-
-
Notifications
You must be signed in to change notification settings - Fork 720
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
Error when running single test using gen_cluster
with check_new_threads=True
#2487
Comments
I believe that this has been resolved |
Hmmm, I am still getting the error on master (0a5b8da). |
I've run the lines that you ran above from master and am unable to reproduce this. I'm also decently confident that this was resolved in #2510 |
OK this is weird I am still having a very similar issue with my original reproducer snippet. I get the problem on two different computers but I can not reproduce on Travis. Maybe @jcrist you can have a go since you bumped into the same issue in #2511? Something I noticed is that the problematic thread is named differently: Would it make sense to ignore "Profile" threads, as we do for "ThreadExecutor" and "watch message" threads? Relevant part of the stack-trace (using the snippet from the top post):
|
Hrm, so the relevant thread is started here: distributed/distributed/core.py Lines 122 to 136 in 78a1a34
And the stopping condition is checked here: distributed/distributed/profile.py Line 240 in 78a1a34
That logic looks ok to me. One possibility is that you have a very long profiling interval in a config file somewhere? (though I don't know why this would be).
No, I think that we genuinely need to test for these. We start them every time we create a Server around a new event loop. We need to make sure that we clean them up. |
Thanks a lot for your help! Debugging a bit further I noticed I had a old-style config in This does not make immediate sense since the values seem to match in the old config.
I have to admit I am happy I got back to a sane state, even without understanding fully why ... |
I bumped into this when working on #2485. The only similar thing I found when googling is xpdAcq/rapidz#22.
To reproduce:
Note I am using the
test_close
(indistributed/tests/test_client.py
) but this happens for any test usinggen_cluster
withcheck_new_threads=True
. Not sure why this is not happening in Travis ...The relevant part of the error:
Full output:
The text was updated successfully, but these errors were encountered: