-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Linker SEGV on MacOS, as of today #6350
Comments
Sometimes when we 're-run failed jobs' we get the same linker-assertion-failure message; other times we do not. I can't find a pattern other than to say there appears to be some randomness involved ... |
As a workaround we've downgraded our CI runner from macos-12 to macos-11 |
Ah, more info: successful build log
and unsuccessful build log
|
@johnkerl hello! We will take a look! First idea is a bug in xcode, have you tried to choose a different xcode version in your pipeline? |
I observe the same assertion in |
@mikhailkoliada as a workaround we've downgraded our CI runner from macos-12 to macos-11 |
@johnkerl could you please try to get back to macos-12 and try different xcode version(s)? |
@mikhailkoliada hmm I tried
so I'll need to check my understand of how to configure XCode versioning within GHA. |
We had a similar issue with our tests. Running |
Hello everyone. It looks like an issue with Xcode, that is why for now I'm going to close the issue. |
Our recommendation is to use this actions - https://github.com/marketplace/actions/setup-xcode-version |
Apparently, xcode 14 has a reported linker bug which prevents a successful build. The recommended workaround is to revert toolchain to last known good version (v13.4.1). More information can be found here - actions/runner-images#6350
Apparently, xcode 14 has a reported linker bug which prevents a successful build. The recommended workaround is to revert toolchain to last known good version (v13.4.1). More information can be found here - actions/runner-images#6350 Also, when macos-latest is used, CI can use either macos11 or macos12 and the build fails if it selects the former. Enforce macos-12 strictly for now.
Apparently, xcode 14 has a reported linker bug which prevents a successful build. The recommended workaround is to revert toolchain to last known good version (v13.4.1). More information can be found here - actions/runner-images#6350 Also, when macos-latest is used, CI can use either macos11 or macos12 and the build fails if it selects the former. Enforce macos-12 strictly for now.
Description
Linker stack trace from https://github.com/single-cell-data/TileDB-SOMA/actions/runs/3177996393/jobs/5179048104:
This appears to be an assertion failure inside the linker itself.
Platforms affected
Runner images affected
Image version and build link
https://github.com/single-cell-data/TileDB-SOMA/actions/runs/3177996393/jobs/5179048104
Is it regression?
https://github.com/single-cell-data/TileDB-SOMA/actions/runs/3174959251/jobs/5172405039
Expected behavior
The linker shouldn't fail an assertion while compiling C++ code
Actual behavior
Assertion-fail in the linker
Repro steps
The text was updated successfully, but these errors were encountered: