-
Notifications
You must be signed in to change notification settings - Fork 234
Unexpectedly no active workers available #1196
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
Comments
at frist glance it seems like a error in traceback handling breaks things (that lineno in the tb shouldnt be None)
theres need for extra detail to figure if this is a bug in a c library or if ptest needs to get more defensive |
Ok, I will throw in |
I think if anything, it's primarily a pytest bug rather than pytest-xdist bug, where the main issue is the Maybe xdist doesn't need to die in the case, but seemingly primary issue is in pytest itself. I saw it locally when I aborted a testrun with Control+C. Should I raise this as a bug in Also a side note, I tried with The critical parts of the exception - it says line is
Full
|
As per the exception a frame has a line number of none My current understanding is that only a broken c extension can trigger that My understand is that every valid frame object returns a number there The note about a type not having a module hardens that suspicion |
I just looked up the details and Indeed cpython maps line numbers 0 and -1 in c to None in python This needs a pytest bugs We also need to create a warning when this case triggers |
Hello!
I've started seeing a weird error on some of my test runs, where I get a
RuntimeError: Unexpectedly no active workers available
raised inpytest-xdist
, after a inTypeError: unsupported operand type(s) for -: 'NoneType' and 'int'
frompytest
.What is strangest is that this is on a successful run (from the looks of it), judging by the summary
I've not really managed to figure out why it happens, and why it only happens sometimes. What is especially puzzling to me is that it only happens sometimes, and that it does happen on succesful runs as well.
Any tips for debugging this? Any specific functions or hooks I should look at, to see if me overriding sometime causes issues?
Here's the full exception:
Full run including plugin and python versions and the full command
The text was updated successfully, but these errors were encountered: