-
Notifications
You must be signed in to change notification settings - Fork 252
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 run-tests
script now attempts to detect Apple Clang 15 and other unsupported regression-tests compiler versions
#972
Merged
hsutter
merged 2 commits into
hsutter:main
from
bluetarpmedia:ci-detect-invalid-compiler
Feb 9, 2024
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Question] Are you sure Apple Clang 15 was selected? The GitHub runner states that Clang 15 s installed from Homebrew. I checked and the output of
$(brew --prefix llvm@15)/bin/clang --version
is:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I'm not 100% sure, this is very much some investigative work!
All I can say for certain right now is that on some macOS job runs (e.g. the one linked above, and I've seen it other times too),
clang++
does not resolve to Apple Clang 14. That's why the script produces thenot found for compiler: 'clang++'
error message.One of the updates in this PR is to provide more info about why the job fails. If this PR is merged then in the future we'll get more info due to this:
That may show
Apple clang 15.0 etc
or something else.Yeah, the
macos-13
runner confusingly has both LLVM Clang installed as well as multiple versions of Xcode (with Apple Clang).Xcode 14.3 is meant to be the default so
clang++
would resolve to Apple Clang 14, but I suspect there's a problem which is causing Xcode 15 to be active. But, it could also somehow be invoking LLVM Clang 15. To me that seemed less likely because, like you noted, it's installed via Homebrew and needs thebrew --prefix llvm@15
to get the correct path.