-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
AppVeyor CI failures in starting workers #27274
Comments
We also have another failure where the tests are hanging and never complete, e.g. https://ci.appveyor.com/project/JuliaLang/julia/build/1.0.27135/job/707kib8lw7xwkje7 |
While investigating #27274 locally, I saw a hang during the cmdlineargs test. Add a timeout to these tests to hopefully turn any hang into an exception instead.
While investigating #27274 locally, I saw a hang during the cmdlineargs test. Add a timeout to these tests to hopefully turn any hang into an exception instead.
While investigating #27274 locally, I saw a hang during the cmdlineargs test. Add a timeout to these tests to hopefully turn any hang into an exception instead.
Ref. another, somewhat different (?), AV timeout: #27249 (comment). Best! |
That looks like a network error, leading to a hang in the OldPkg testsuite. Ideally we should make sure that all network errors result in reliable failures of the test suite rather than hangs. |
Should we just stop running the OldPkg tests for now since we're deprecating/deleting it in 0.7/1.0? |
Yeah, it would be good to remove the OldPkg tests. That would save non-trivial CI time too. |
Not using AV anymore. |
There's a recurring failure on AppVeyor where it fails to start a worker and then hangs for the rest of the session:
E.g.: https://ci.appveyor.com/project/JuliaLang/julia/build/1.0.27132/job/c7n39lsfix6j2mi3
It would be nice to figure out what's going on here. Maybe some windows-specific race condition?
The text was updated successfully, but these errors were encountered: