When a Miri "pass" test fails with MIRI_SKIP_UI_CHECKS set, the only output we get is
FAILED TEST: tests/pass/box.rs
command: MIRI_ENV_VAR_TEST="0" MIRI_TEMP="/tmp/miri-uitest-40LqIv" RUST_BACKTRACE="1" "/home/r/src/rust/rustc/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/release/miri" "--error-format=json" "--sysroot=/home/r/src/rust/rustc/build/x86_64-unknown-linux-gnu/miri-sysroot" "-Dwarnings" "-Dunused" "-Ainternal_features" "-O" "-Zmir-opt-level=4" "-Cdebug-assertions=yes" "-Zui-testing" "--out-dir" "/home/r/src/rust/rustc/build/x86_64-unknown-linux-gnu/stage1-tools/x86_64-unknown-linux-gnu/tmp/miri_ui/0/tests/pass" "tests/pass/box.rs" "-Zmiri-permissive-provenance" "--edition" "2021"
error: test got exit status: 1, but expected 0
= note: compilation failed, but was expected to succeed
The expected behavior is that it prints stderr, as it would usually when output conflict handling is enabled. The error has nothing to do with an output conflict so it shouldn't be affected by output conflict handling.
When a Miri "pass" test fails with
MIRI_SKIP_UI_CHECKSset, the only output we get isThe expected behavior is that it prints stderr, as it would usually when output conflict handling is enabled. The error has nothing to do with an output conflict so it shouldn't be affected by output conflict handling.