-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Unset MIRI_BLESS for mir-opt-level 4 miri tests #111809
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
Conversation
r? @ozkanonur (rustbot has picked a reviewer for you, use r? to override) |
r? miri i think this means it's not possible to bless mir-opt-level=4 tests, is that right? or is the idea that all the tests should be the same regardless of the opt level? |
Its the same tests, just with opts enabled to catch miscompilations. It wouldn't make sense to bless them twice. |
@bors r+ rollup (CI never passes --bless, which is why we never caught this in the first place) |
Unset MIRI_BLESS for mir-opt-level 4 miri tests When running `x.py test src/tools/miri --bless`, the 2nd test run (with mir-opt-level 4) crashes because it disables ui checking, which is incompatible with blessing. This PR fixes that by not trying to bless that run.
…iaskrgr Rollup of 5 pull requests Successful merges: - rust-lang#111745 (Fix overflow in error emitter) - rust-lang#111770 (Read beta version from the version file if building from a source tarball) - rust-lang#111797 (Migrate GUI colors test to original CSS color format) - rust-lang#111809 (Unset MIRI_BLESS for mir-opt-level 4 miri tests) - rust-lang#111817 (Migrate GUI colors test to original CSS color format) r? `@ghost` `@rustbot` modify labels: rollup
When running
x.py test src/tools/miri --bless
, the 2nd test run (with mir-opt-level 4) crashes because it disables ui checking, which is incompatible with blessing. This PR fixes that by not trying to bless that run.