-
Notifications
You must be signed in to change notification settings - Fork 31
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 BindException: Address already in use
/ SystemError: Failed to start Crate instance in time
#630
Comments
I have not been able to observe this error recently, so I am closing this. |
The error is not gone yet, those are two more data points. |
doctests/layer.txt
Another different one from
-- https://github.com/crate/crate-python/actions/runs/3218694497/jobs/5263181322#step:4:363 |
doctests/layer.txt
SystemError: Failed to start Crate instance in time
This one still occasionally happens.
-- https://github.com/crate/crate-python/actions/runs/3700515171/jobs/6269005519#step:4:429 |
Didn't see this for a while already. Even if, it's just a fluke. Closing this. |
Still happening occasionally.
-- https://github.com/crate/crate-python/actions/runs/9562806841/job/26359960751?pr=625#step:4:354 References |
SystemError: Failed to start Crate instance in time
BindException: Address already in use
/ SystemError: Failed to start Crate instance in time
This issue has not been observed recently, so I am closing this. |
The root cause for
SystemError: Failed to start Crate instance in time.
(see #629) is that a previous instance of CrateDB might not have been terminated correctly.In that case, a subsequent attempt to start it will croak like [1,2]
[1] https://github.com/crate/crate-python/runs/6210165871#step:6:192
[2] https://github.com/crate/crate-python/runs/6540915990#step:5:233
_Originally posted by @amotl in #629
References
The text was updated successfully, but these errors were encountered: