-
-
Notifications
You must be signed in to change notification settings - Fork 429
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
KeyError in qualname_from_frame starting from 5.0a6 #829
Comments
Any chance I can get the project that failed? So that I can run the tests myself? Is numexpr your project? |
Unfortunately both of the projects that failed are internal to my company. Both use numexpr (https://pypi.org/project/numexpr/). I will try to keep digging to see if I can provide more information. |
I see what's going on here: there's a class named "test_numexpr" (unusual name for a class). It's being called, so coverage thinks it's a function. I'll try making a small reproducer. |
Ah, it's easy to make happen:
Thanks for the interesting report! :) |
Wow! That's good news! I honestly didn't know what else to try to figure this one out! So glad :) |
Fixed in 07c3c5d. |
Just to know, no rush, when do you think there will be a new release containing this fix? |
This is in 5.0a7. |
Describe the bug
After upgrading from coveragepy
5.0a5
-ish to to5.0a6
, we started having a few failing builds with something that looks as follows:In case it helps, both failed builds have these lines the log:
and both also mention
KeyError: 'test_numexpr'
I really struggled to understand why this is happening, BUT I went through all commits in coveragepy and, at least, I found that the commit that breaks it is the following:
a9f5f7f
The command that was run to cause this is:
Please let me know if I can provide any other information that might help you
Expected behavior
All tests should be collected and pass, as it happens when using coveragepy from a point in time before the commit mentioned above.
Additional context
3.6.5
and2.7.13
pytest 3.1.0
The text was updated successfully, but these errors were encountered: