You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In both cases, the processes are compiling a crate when they receive an abort signal. It's possible that we're hitting some resource limits in the runners themselves. But re-running the CI jobs a few times does the trick.
The text was updated successfully, but these errors were encountered:
Resolving with the assumption that #2987 has fixed the problem, which is in line with the claims made in rust-lang/rust#92173 (comment) (that the problem is an XCode issue). We may have to re-open this issue if the problem isn't actually fixed by the OS upgrade.
Proposed change: Investigate the spurious failures in macOS CI jobs and attempt to fix if possible.
Motivation: This week some CI jobs running on macOS runners have been failing without a clear reason to do so. Some examples:
should_panic
andfail_uncoverable
options as global conditions #2967 (no code changes)main
after we merged Rethinkshould_panic
andfail_uncoverable
options as global conditions #2967 (again, no code changes)In both cases, the processes are compiling a crate when they receive an abort signal. It's possible that we're hitting some resource limits in the runners themselves. But re-running the CI jobs a few times does the trick.
The text was updated successfully, but these errors were encountered: