@@ -6,14 +6,14 @@ set -x # so one can see where we are in the script
66
77X_PY=" $1 "
88
9- python3 " $X_PY " --stage 2 test src/tools/cargo -- --no-run
10- python3 " $X_PY " --stage 2 build src/tools/cargo
9+ # python3 "$X_PY" --stage 2 test src/tools/cargo -- --no-run
10+ # python3 "$X_PY" --stage 2 build src/tools/cargo
1111
1212# Try to test the toolstate-tracked tools and store the build/test success in the TOOLSTATE_FILE.
1313
1414# Pre-build the compiler and the library first to output a better error message when the build
1515# itself fails (see https://github.com/rust-lang/rust/issues/127869 for context).
16- python3 " $X_PY " build --stage 2 compiler rustdoc
16+ # python3 "$X_PY" build --stage 2 compiler rustdoc
1717
1818# set +e
1919# python3 "$X_PY" test --stage 2 --no-fail-fast \
@@ -34,43 +34,12 @@ python3 "$X_PY" build --stage 2 compiler rustdoc
3434# python3 "$X_PY" test --stage 2 src/tools/clippy
3535# python3 "$X_PY" test --stage 2 src/tools/rustfmt
3636
37- # Testing Miri is a bit more complicated.
38- # We set the GC interval to the shortest possible value (0 would be off) to increase the chance
39- # that bugs which only surface when the GC runs at a specific time are more likely to cause CI to fail.
40- # This significantly increases the runtime of our test suite, or we'd do this in PR CI too.
41- if [ -z " ${PR_CI_JOB:- } " ]; then
42- MIRIFLAGS=-Zmiri-provenance-gc=1 python3 " $X_PY " test --stage 2 src/tools/miri src/tools/miri/cargo-miri
43- else
44- python3 " $X_PY " test --stage 2 src/tools/miri src/tools/miri/cargo-miri
45- fi
46- # We natively run this script on x86_64-unknown-linux-gnu and x86_64-pc-windows-msvc.
47- # Also cover some other targets via cross-testing, in particular all tier 1 targets.
48- case $HOST_TARGET in
49- x86_64-unknown-linux-gnu)
50- # Only this branch runs in PR CI.
51- # Fully test all main OSes, including a 32bit target.
52- python3 " $X_PY " test --stage 2 src/tools/miri src/tools/miri/cargo-miri --target x86_64-apple-darwin
53- python3 " $X_PY " test --stage 2 src/tools/miri src/tools/miri/cargo-miri --target i686-pc-windows-msvc
54- # Only run "pass" tests for the remaining targets, which is quite a bit faster.
55- python3 " $X_PY " test --stage 2 src/tools/miri --target x86_64-pc-windows-gnu --test-args pass
56- python3 " $X_PY " test --stage 2 src/tools/miri --target i686-unknown-linux-gnu --test-args pass
57- python3 " $X_PY " test --stage 2 src/tools/miri --target aarch64-unknown-linux-gnu --test-args pass
58- python3 " $X_PY " test --stage 2 src/tools/miri --target s390x-unknown-linux-gnu --test-args pass
59- ;;
60- x86_64-pc-windows-msvc)
61- # Strangely, Linux targets do not work here. cargo always says
62- # "error: cannot produce cdylib for ... as the target ... does not support these crate types".
63- # Only run "pass" tests, which is quite a bit faster.
64- python3 " $X_PY " test --stage 2 src/tools/miri --target aarch64-apple-darwin --test-args pass
65- python3 " $X_PY " test --stage 2 src/tools/miri --target i686-pc-windows-gnu --test-args pass
66- ;;
67- * )
68- echo " FATAL: unexpected host $HOST_TARGET "
69- exit 1
70- ;;
71- esac
37+ python3 " $X_PY " test --stage 2 src/tools/miri src/tools/miri/cargo-miri
38+ python3 " $X_PY " test --stage 2 src/tools/miri --target aarch64-apple-darwin --test-args pass
39+ python3 " $X_PY " test --stage 2 src/tools/miri --target i686-pc-windows-gnu --test-args pass
40+
7241# Also smoke-test `x.py miri`. This doesn't run any actual tests (that would take too long),
7342# but it ensures that the crates build properly when tested with Miri.
74- python3 " $X_PY " miri --stage 2 library/core --test-args notest
75- python3 " $X_PY " miri --stage 2 library/alloc --test-args notest
76- python3 " $X_PY " miri --stage 2 library/std --test-args notest
43+ # python3 "$X_PY" miri --stage 2 library/core --test-args notest
44+ # python3 "$X_PY" miri --stage 2 library/alloc --test-args notest
45+ # python3 "$X_PY" miri --stage 2 library/std --test-args notest
0 commit comments