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
I can consistently reproduce a teardown failure (hangs instead) when running the test_cancellation.py::test_nested_multierrors() test with trip but only when trace level logging is enabled via the --ll trace to pytest.
At face value this seems to be a race condition where somehow a couple subactors aren't getting their cancel messages. Monitoring logging and the process list shows this is likely the case. It needs more investigation but I don't think is a show stopper especially given the test is reproducing a case unlikely to be used in practice.
The text was updated successfully, but these errors were encountered:
I can consistently reproduce a teardown failure (hangs instead) when running the
test_cancellation.py::test_nested_multierrors()
test with trip but only when trace level logging is enabled via the--ll trace
topytest
.At face value this seems to be a race condition where somehow a couple subactors aren't getting their cancel messages. Monitoring logging and the process list shows this is likely the case. It needs more investigation but I don't think is a show stopper especially given the test is reproducing a case unlikely to be used in practice.
The text was updated successfully, but these errors were encountered: