-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Various tests break if optimize-tests = false
in config.toml
#55757
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
…rom `rustc -O`. (The fact that output differs under `opt-level=0` is an instance of rust-lang#55757.)
Hmm, @oli-obk points out (#55532 (comment)) that one can add And that's true: One can pass I had thought you couldn't, because what you cannot do is pass |
The main symptom of this problem on OS X will be resolved if #54153 is closed by PR #56772 I'll go look if Linux has any similar issues. If it doesn't... then I may close this. I'm tempted to still leave it open because tests should have some way to override the setting in |
Linux didn't have any analogous issues here. And I think PR #56772 will (eventually) go through. So I'm closing this. |
Some number of tests in the test suite will break if you turn off optimization. (The breakage is usually not terrible; e.g. sometimes its mild difference in diagnostic output.)
This is nonetheless a real problem because there is no good way to work around it. For example, there is no way for a test to specify that it requires a certain opt-level.
The text was updated successfully, but these errors were encountered: