-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Don't cancel try-perf branch if 'outdated' #100033
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
@bors r+ rollup p=1 To clarify, the builds aren't queued, they run in parallel, but we are able to just dump a set onto the branch rather than queuing elsewhere. I guess you can pop from a queue in parallel too :) |
📌 Commit 5a3cc95492c7412f48e1bf5aa211a1dd556ed76e has been approved by It is now in the queue for this repository. |
⌛ Testing commit 5a3cc95492c7412f48e1bf5aa211a1dd556ed76e with merge dfadf2593af5848e11b063a83a6518ec3737ddbd... |
💔 Test failed - checks-actions |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
5a3cc95
to
debb75a
Compare
@bors r+ rollup p=1 |
☀️ Test successful - checks-actions |
Finished benchmarking commit (9d5cd21): comparison url. Instruction countThis benchmark run did not return any relevant results for this metric. 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 |
try-perf
just like thetry
branch should always run all jobs to completion. This allows us to use the branch like a queue.r? @Mark-Simulacrum