Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TRIP - one last shutdown hang #96

Closed
goodboy opened this issue Jan 28, 2020 · 1 comment
Closed

TRIP - one last shutdown hang #96

goodboy opened this issue Jan 28, 2020 · 1 comment
Labels
bug Something isn't working testing
Milestone

Comments

@goodboy
Copy link
Owner

goodboy commented Jan 28, 2020

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.

@goodboy
Copy link
Owner Author

goodboy commented Jul 27, 2020

Closed by #128.

@goodboy goodboy closed this as completed Jul 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working testing
Projects
None yet
Development

No branches or pull requests

1 participant