diff options
Diffstat (limited to 'src/ci/docker/host-x86_64/x86_64-gnu-llvm-15/script.sh')
-rwxr-xr-x | src/ci/docker/host-x86_64/x86_64-gnu-llvm-15/script.sh | 49 |
1 files changed, 0 insertions, 49 deletions
diff --git a/src/ci/docker/host-x86_64/x86_64-gnu-llvm-15/script.sh b/src/ci/docker/host-x86_64/x86_64-gnu-llvm-15/script.sh deleted file mode 100755 index 2eb751ca3..000000000 --- a/src/ci/docker/host-x86_64/x86_64-gnu-llvm-15/script.sh +++ /dev/null @@ -1,49 +0,0 @@ -#!/bin/bash - -set -ex - -# Only run the stage 1 tests on merges, not on PR CI jobs. -if [[ -z "${PR_CI_JOB}" ]]; then - # When running gcc backend tests, we need to install `libgccjit` and to not run llvm codegen - # tests as it will fail them. - if [[ "${ENABLE_GCC_CODEGEN}" == "1" ]]; then - ../x.py --stage 1 test --skip src/tools/tidy --skip tests/codegen - else - ../x.py --stage 1 test --skip src/tools/tidy - fi - - # Run the `mir-opt` tests again but this time for a 32-bit target. - # This enforces that tests using `// EMIT_MIR_FOR_EACH_BIT_WIDTH` have - # both 32-bit and 64-bit outputs updated by the PR author, before - # the PR is approved and tested for merging. - # It will also detect tests lacking `// EMIT_MIR_FOR_EACH_BIT_WIDTH`, - # despite having different output on 32-bit vs 64-bit targets. - ../x.py --stage 1 test tests/mir-opt --host='' --target=i686-unknown-linux-gnu - - # Run `ui-fulldeps` in `--stage=1`, which actually uses the stage0 - # compiler, and is sensitive to the addition of new flags. - ../x.py --stage 1 test tests/ui-fulldeps -fi - -# When running gcc backend tests, we need to install `libgccjit` and to not run llvm codegen -# tests as it will fail them. -# NOTE: intentionally uses all of `x.py`, `x`, and `x.ps1` to make sure they all work on Linux. -if [[ "${ENABLE_GCC_CODEGEN}" == "1" ]]; then - ../x.py --stage 2 test --skip src/tools/tidy --skip tests/codegen -else - ../x.py --stage 2 test --skip src/tools/tidy -fi - -# Run the `mir-opt` tests again but this time for a 32-bit target. -# This enforces that tests using `// EMIT_MIR_FOR_EACH_BIT_WIDTH` have -# both 32-bit and 64-bit outputs updated by the PR author, before -# the PR is approved and tested for merging. -# It will also detect tests lacking `// EMIT_MIR_FOR_EACH_BIT_WIDTH`, -# despite having different output on 32-bit vs 64-bit targets. -../x --stage 2 test tests/mir-opt --host='' --target=i686-unknown-linux-gnu - -# Run the UI test suite again, but in `--pass=check` mode -# -# This is intended to make sure that both `--pass=check` continues to -# work. -../x.ps1 --stage 2 test tests/ui --pass=check --host='' --target=i686-unknown-linux-gnu |