-
Notifications
You must be signed in to change notification settings - Fork 42
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 accidentally skips over crux-llvm
tests on macOS
#999
Comments
RyanGlScott
added a commit
that referenced
this issue
Jul 21, 2022
Previously, the `clang-withIncl` script that we concocted on CI for calling `clang` with the correct flags neglected to actually pass the _arguments_ to `clang`. As a result, the `crux-llvm` test suite would trivially pass on macOS since it skipped all of the test cases due to `clang-withIncl` being misconfigured. This corrects this mistake by passing the arguments through to `clang-withIncl` using `${1+"$@"}`. Fixes #999. This won't be enough on its own to make the `crux-llvm` test suite pass on macOS—see #885 and #1013. Fixes for those issues will come in subsequent commits.
RyanGlScott
added a commit
that referenced
this issue
Jul 21, 2022
Previously, the `clang-withIncl` script that we concocted on CI for calling `clang` with the correct flags neglected to actually pass the _arguments_ to `clang`. As a result, the `crux-llvm` test suite would trivially pass on macOS since it skipped all of the test cases due to `clang-withIncl` being misconfigured. This corrects this mistake by passing the arguments through to `clang-withIncl` using `${1+"$@"}`. Fixes #999. This won't be enough on its own to make the `crux-llvm` test suite pass on macOS—see #885 and #1013. Fixes for those issues will come in subsequent commits.
RyanGlScott
added a commit
that referenced
this issue
Jul 22, 2022
Previously, the `clang-withIncl` script that we concocted on CI for calling `clang` with the correct flags neglected to actually pass the _arguments_ to `clang`. As a result, the `crux-llvm` test suite would trivially pass on macOS since it skipped all of the test cases due to `clang-withIncl` being misconfigured. This corrects this mistake by passing the arguments through to `clang-withIncl` using `${1+"$@"}`. Fixes #999. This won't be enough on its own to make the `crux-llvm` test suite pass on macOS—see #885 and #1013. Fixes for those issues will come in subsequent commits.
Merged
RyanGlScott
added a commit
that referenced
this issue
Feb 13, 2024
Previous, we concocted a `clang-withIncl` script for running Clang on macOS CI runners, but this neglected to pass any arguments to Clang (among other issues). This patch replaces the `clang-withIncl` machinery with a much simpler, Homebrew-based setup for install Clang/LLVM. With this in place, we can finally run the `crux-llvm` test suite on macOS. Fixes #999.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Recently, I came to wonder why the macOS CI jobs weren't catching #885, which should prevent the
crux-llvm
tests from passing on macOS. It turns out this is because the CI isn't actually running thecrux-llvm
test suite on macOS at all! Take a look at what happens on a typical macOS job like this one:The first suspicious thing here is that the whole test suite takes 12 seconds to run, which is far too short. The second suspicious thing is that
clang-withIncl --version
printsclang-11: error: no input files
instead of the version number. This is a consequence of how the CI is setting upclang
on macOS. It assembles a wrapper script namedclang-withIncl
here:crucible/.github/workflows/crux-llvm-build.yml
Lines 173 to 174 in 4158b6f
There's a mistake here, however: the invocation of
clang
doesn't pass through the arguments (e.g., with${1+"$@"}
), so no matter what arguments you pass to theclang-withIncl
script, it will simply invokeclang
with no input files. We should change this script so that it plumbs through the arguments.The text was updated successfully, but these errors were encountered: