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
While tests run fine if running in just a single worker of with -n 4, it seems that when boosting this further to 8 cores, the scheduler emitted an extra event of EMPTY.
Looking at the async task the monitors for empty, it is possible there's a race condition causing this to trigger twice. This should be handled properly although it's hard to create a reproducing example. In general, how can we deterministically create race conditions for testing?
While tests run fine if running in just a single worker of with
-n 4
, it seems that when boosting this further to8
cores, the scheduler emitted an extra event ofEMPTY
.Looking at the async task the monitors for empty, it is possible there's a race condition causing this to trigger twice. This should be handled properly although it's hard to create a reproducing example. In general, how can we deterministically create race conditions for testing?
amltk/src/amltk/scheduling/scheduler.py
Lines 1148 to 1165 in 0f4e1af
Error, traceback of test
The text was updated successfully, but these errors were encountered: