-
-
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
OSX Travis fails spawn test with InterruptException #17626
Comments
@yuyichao Could this be a SIGSEGV happening, but getting picked up by the |
Unless there's actually a |
This is happening fairly often. Will need to fix this to get reliable CI. |
slightly different backtrace on this one, but probably same underlying cause
|
not Travis specific: buildbot log https://build.julialang.org/builders/build_osx10.9-x64/builds/1751/steps/shell_2/logs/stdio
@vtjnash ideas? |
Yep, just wanted to pop in and say this is still happening on the |
shucks, on the merge commit too: https://travis-ci.org/JuliaLang/julia/jobs/194054914 |
still failing https://travis-ci.org/JuliaLang/julia/jobs/194719508
|
Seems to be a new / different failure, in that it consistently occurs in a different test. |
Here are two more that look possibly related: https://travis-ci.org/JuliaLang/julia/jobs/200076193 |
I got similar failure on FreeBSD (4GB ram + 4GB swap on it).
|
I suspected it was something like this. I guess the solution would be to get Travis to raise some limit. |
Once there's a fix, it should be backported to 0.6. Luckily the failure is only spurious, so in the meantime we can keep running the macOS builds on the buildbot repeatedly until one of them goes through... |
@vtjnash said the fix may be only for 1.0. Anyways shouldn't hold 0.6.1 on it. |
"things you wanted fixed soon" ≠ "release blocker"; throw the "priority" label on it for that. |
If Jameson knows how to fix it already, is there anything to triage? |
Can I assume that this is no longer relevant? |
It still happens occasionally though less often than it used to. |
fixed by #22041 |
I am observing this value get set to EINTR sometimes on Linux. It is not generally supposed to do that (though not prohibited either). That is causing us to sometimes drop signals (usually SIGINT). Since we just need this code for Darwin (ref #17626, #22041, #20174), we can remove this from everywhere else.
I am observing this value get set to EINTR sometimes on Linux. It is not generally supposed to do that (though not prohibited either). That is causing us to sometimes drop signals (usually SIGINT). Since we just need this code for Darwin (ref #17626, #22041, #20174), we can remove this from everywhere else.
I am observing this value get set to EINTR sometimes on Linux. It is not generally supposed to do that (though not prohibited either). That is causing us to sometimes drop signals (usually SIGINT). Since we just need this code for Darwin (ref #17626, #22041, #20174), we can remove this from everywhere else.
e.g. https://travis-ci.org/JuliaLang/julia/jobs/147328890
or https://travis-ci.org/JuliaLang/julia/jobs/146808733
The text was updated successfully, but these errors were encountered: