-
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
Make more tests robust and independent #546
Comments
|
The same error at test_connect_message::AssertionError-2> assert msg in captured.out
E assert "connected to database 'jdbc:hsqldb:mem://test_connect_message_1' (user: ixmp)..." in ''
E + where '' = CaptureResult(out='', err='').out
ixmp\tests\backend\test_jdbc.py:277: AssertionError
---------------------------- Captured stdout call -----------------------------
2024-09-30 05:17:54,257 INFO at.ac.iiasa.ixmp.Platform:182 - closed the connection to database 'jdbc:hsqldb:mem://test_connect_message_0'
2024-09-30 05:17:54,445 INFO at.ac.iiasa.ixmp.Platform:165 - Welcome to the IX modeling platform!
2024-09-30 05:17:54,445 INFO at.ac.iiasa.ixmp.Platform:166 - connected to database 'jdbc:hsqldb:mem://test_connect_message_1' (user: ixmp)...
------------------------------ Captured log call ------------------------------
INFO ixmp.backend.jdbc:jdbc.py:288 launching ixmp.Platform connected to jdbc:hsqldb:mem://test_connect_message_1 |
Thanks for continuing to track these. I'll remove the If particular users report failures of the code in real-world usage that correspond to the flaky tests on GHA, then those are definitely |
|
|
|
|
|
|
|
Unfortunately, despite our recent improvements in #543, we still see some apparent flakiness. Its main source seems to be the setup-graphviz action on the windows runners, which sometimes fails like this:
In addition, there was a new flaky test today:
test_connect_message::AssertionError
Which almost seems like
out
anderr
got mixed up in theCaptureResult
. If this originates from one test changing the logging level without changing it back again, we should figure out a way to change the level just for this one test, without affecting the whole environment.The text was updated successfully, but these errors were encountered: