You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[OrcJIT] distinguish normal and abrupt TaskDispatcher shutdown
Add a `run_to_complete` complement to `shutdown`, which does nearly the
same operations, but does not cancel future / pending work. The
distinction is often mainly academic, but split for clarity of intent of
each caller.
Annotate each and every tests that assumes that any previously scheduled
tasks have finished running with a call of `run_to_completion` before
reading the variables written by those tasks. This more clearly
emphasizes the expectations of each of these tests and makes them robust
against data-races or changes to the default scheduler.
These should have no impact currently, but have been tested and shown to
pass with a scheduler which defers all work (as if being run on a
thread) until an explicit synchronization point "acquires" that state,
demonstrating that this is each and every test that would be affected by
changes to the default scheduler.
0 commit comments