-
Notifications
You must be signed in to change notification settings - Fork 112
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
test_checkBigStorage randomly fails with an AssertionError #85
Comments
I just noticed that some files |
This leftover temporary file is the one produced by |
In the meantime, I've also seen cases where no The failures happen especially when the machine is under high load, so it really looks timing-based. My theory is that the serialisation and/or deserialisation doesn't finish before the Also, I think it might be a good idea to let a test fail entirely if |
Correction: I meant the |
test_checkBigStorage
sometimes fails with anAssertionError
in line 595 or 596. The failures happen only sometimes, suggesting that it's a timing issue and one of thestopFunc
s might need another condition (e.g. the one after the log compaction, to ensure that the data was indeed dumped to disk?).I've seen failures on both lines mentioned above, i.e. there are cases where
o1
has the correct value buto2
doesn't and vice-versa. In all cases I've seen,getValue('test')
returnsNone
, i.e. the value is missing entirely, not corrupted.My platform is a Debian machine with Python 3.6.
Bash command to run this test repeatedly:
The text was updated successfully, but these errors were encountered: