-
-
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
CI: New Intermittent segfault #46152
Comments
Is that the |
That'd match the the fact the first failing job was found on June 30th: the PR was merged the day before. |
The test that's failing is not the one that was added in that PR though. It's usually either the |
This changes the mach exception server to ignore fatal SIGSEGVs, letting regular kernel processing handle it (by performing POSIX signal delivery and then subsequently coredumping), rather than quitting the process directly. There's probably some way to induce the kernel to perform core dumping directly from the exception server, but I think it'll be less confusing all around to just have segfaults take the standard path. Hoping this will help debug #46152.
Both would be very likely to fail if the PR was incompletely fixing the issue, and if people keep configuring CI to run with threads (which is not supported yet) |
|
This changes the mach exception server to ignore fatal SIGSEGVs, letting regular kernel processing handle it (by performing POSIX signal delivery and then subsequently coredumping), rather than quitting the process directly. There's probably some way to induce the kernel to perform core dumping directly from the exception server, but I think it'll be less confusing all around to just have segfaults take the standard path. Hoping this will help debug #46152.
Appears to have been resolved by turning off threading. |
This changes the mach exception server to ignore fatal SIGSEGVs, letting regular kernel processing handle it (by performing POSIX signal delivery and then subsequently coredumping), rather than quitting the process directly. There's probably some way to induce the kernel to perform core dumping directly from the exception server, but I think it'll be less confusing all around to just have segfaults take the standard path. Hoping this will help debug JuliaLang#46152.
This changes the mach exception server to ignore fatal SIGSEGVs, letting regular kernel processing handle it (by performing POSIX signal delivery and then subsequently coredumping), rather than quitting the process directly. There's probably some way to induce the kernel to perform core dumping directly from the exception server, but I think it'll be less confusing all around to just have segfaults take the standard path. Hoping this will help debug JuliaLang#46152.
We appear to have a new intermittent segfault on CI. I regularly see
ProcessExited(139)
on macos builders, but it's possible that failures on various other systems are also related. See below for a table of recent macos logs that failed with this error. Looks like this might have started around Jul 4 or so.Table of recent ProcessExited(139) failures
12 rows × 9 columns
The text was updated successfully, but these errors were encountered: