-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Remove fragile equal-pointers-unequal tests. #140576
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
These randomly break when i change the implementation of format_args!().
@bors r+ rollup |
…iaskrgr Rollup of 7 pull requests Successful merges: - rust-lang#138712 (resolve: Support imports of associated types and glob imports from traits) - rust-lang#140395 (organize and extend forbidden target feature tests) - rust-lang#140576 (Remove fragile equal-pointers-unequal tests.) - rust-lang#140582 (Update sysinfo to `0.35.0` in bootstrap and `tools/opt-dist`) - rust-lang#140595 (doc(std): fix typo lchown -> lchmod) - rust-lang#140597 (zkvm: remove schmerik as target maintainer) - rust-lang#140604 (yet another small borrowck cleanup ) r? `@ghost` `@rustbot` modify labels: rollup
The tests are for a known miscompilation caused by LLVM. The intent is that the |
Rollup merge of rust-lang#140576 - m-ou-se:fragile-tests, r=compiler-errors Remove fragile equal-pointers-unequal tests. Same as rust-lang#139176 --- These tests were added in rust-lang#127003 These tests stop working when I change implementation details of format_args!(). These tests shouldn't rely on such implementation details. Do these tests test anything that isn't already covered by other tests? If so, they should be expressed in a less fragile way that doesn't rely on internal details of format_args!(). cc `@GrigorenkoPV,` author of these tests.
Sure, but if I chanage anything about the format_args!() implementation details, the bugs are no longer triggered. So if we want these tests, they should be rewritten to not rely on the exact expansion/lowering of format_args!(). |
Same as #139176
These tests were added in #127003
These tests stop working when I change implementation details of format_args!(). These tests shouldn't rely on such implementation details.
Do these tests test anything that isn't already covered by other tests? If so, they should be expressed in a less fragile way that doesn't rely on internal details of format_args!().
cc @GrigorenkoPV, author of these tests.