Skip to content

Commit 5d832f1

Browse files
committed
Don't run ui-fulldeps tests twice in stage 1
This removes a separate call in the x86_64-gnu-llvm-21-3 job which runs the ui-fulldeps a second time. ui-fulldeps is already running in the first call (`../x.py --stage 1 test`) as it is a default test suite. This was added in #116009, but I think that was a misunderstanding of the problem. The actual problem was fixed in #116932 where the actual problem was the use of `&&`. This doesn't really have much of an impact on CI time (only a couple seconds) because all the tests are skipped with `ignored, up-to-date`. I'm mainly doing this to clean up the script itself for clarity.
1 parent 4feb722 commit 5d832f1

1 file changed

Lines changed: 0 additions & 4 deletions

File tree

src/ci/docker/scripts/x86_64-gnu-llvm3.sh

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,10 +14,6 @@ set -ex
1414
# despite having different output on 32-bit vs 64-bit targets.
1515
../x.py --stage 1 test tests/mir-opt --host='' --target=i686-unknown-linux-gnu
1616

17-
# Run `ui-fulldeps` in `--stage=1`, which actually uses the stage0
18-
# compiler, and is sensitive to the addition of new flags.
19-
../x.py --stage 1 test tests/ui-fulldeps
20-
2117
# Rebuild the stdlib with the size optimizations enabled and run tests again.
2218
RUSTFLAGS_NOT_BOOTSTRAP="--cfg feature=\"optimize_for_size\"" ../x.py --stage 1 test \
2319
library/std library/alloc library/core

0 commit comments

Comments
 (0)