-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Only obey optimize-tests flag on UI tests that are run-pass #98817
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
``` optimize-tests = false, master 25.98s optimize-tests = true, master 34.69s optimize-tests = true, patched 28.79s ``` Effects: - faster UI tests - llvm asserts get exercised less on build-pass tests - the difference between opt and nopt builds shrinks a bit - aux libs don't get optimized since they don't have a pass mode and almost never have explicit compile flags
(rust-highfive has picked a reviewer for you, use r? to override) |
I think this makes sense - we can probably adjust nopt (or opt) builders to have different behavior here, but ultimately I suspect impact is pretty minimal. @bors r+ rollup=iffy |
📌 Commit 125f33a has been approved by |
@bors r- |
a9972ca
to
f719239
Compare
@rustbot ready |
@bors r=Mark-Simulacrum |
📌 Commit f719239 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (d2074cb): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
stage1 UI tests walltime on my machine:
Effects: