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
testmon_data.fail_reports might contain both failed and skipped #103
Comments
Also 39ee38a is next iteration. |
Just hit the assert now:
Before this I was interrupting
Note that it goes through testmon's It looks like |
It was before the latest data-format bump though, i.e. might have missed some fixes, but I could just reproduce it by Ctrl-C'ing with a removed .testmondata now. To reproduce this it needs a failed test before Ctrl-Cing. |
So it was 2 separate runs?
|
Yes. I could reproducible trigger the internal error (the assert) by removing Just tried to reproduce it with something simpler, but could not: def test_pass1():
pass
def test_fail():
assert 0
def test_sleep():
import time
time.sleep(2)
def test_pass2():
pass But I've copied |
it shouldn't happen in v0.9.12 any more. Can you confirm? |
Yes, I assume so - at least I've seen something in this regard when re-testing for #101. |
testmon_data.fail_reports might contain both failed and skipped:
I might have messed up some internals while debugging #101 / #102, but I think it should be ensured that this would never happen, e.g. on the DB level.
The text was updated successfully, but these errors were encountered: