-
Notifications
You must be signed in to change notification settings - Fork 30
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
Tests: Flakyness with "active servers" logic within test suite #404
Comments
Maybe this happens because the retry interval is set to a very low value when running the tests. crate-python/src/crate/client/test_http.py Lines 311 to 313 in afb3b0b
So, the I actually recognized that this specific job was executing very slow, so it probably has been scheduled on a CI machine currently experiencing more load than others. |
The same thing happened again at https://github.com/crate/crate-python/runs/2297326550#step:6:184.
|
Now also, slightly different but the same issue, at https://github.com/crate/crate-python/runs/2297736340#step:6:166.
|
Footnotes |
I did not observe this flaw recently, so I am closing this issue. |
It still happens when runners seem to be slow.
-- https://github.com/crate/crate-python/actions/runs/3198965176/jobs/5224159502#step:4:338 |
This one still happens from time to time. -- https://github.com/crate/crate-python/actions/runs/3700515171/jobs/6269005827#step:4:565 |
Still happening occasionally. One re-run usually fixes the fluke. -- https://github.com/crate/crate-python/actions/runs/9545350897/job/26305926214#step:4:651 |
This issue has not been observed recently, so I am closing this. |
Hi,
on [1] and [2], I just observed a flakyness on a single job when running the tests on #397 and #402.
With kind regards,
Andreas.
[1] https://github.com/crate/crate-python/actions/runs/687059879
[2] https://github.com/crate/crate-python/runs/2195227267#step:5:199
The text was updated successfully, but these errors were encountered: