-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Fix spurious CI failures #94779
Fix spurious CI failures #94779
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
@bors r+ p=50 rollup=never |
📌 Commit 1c0bd57d4f36f3a5bea74d7ac48c1596153688ed has been approved by |
🌲 The tree is currently closed for pull requests below priority 50. This pull request will be tested once the tree is reopened. |
⌛ Testing commit 1c0bd57d4f36f3a5bea74d7ac48c1596153688ed with merge 0ee66f91371c124eeaccf189524f591235d84c26... |
💔 Test failed - checks-actions |
1c0bd57
to
18006a6
Compare
I commented the test and will look into it later. @bors r=Dylan-DPC p=50 rollup=never |
📌 Commit 18006a6 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (458262b): comparison url. Summary: This benchmark run did not return any relevant results. 4 results were found to be statistically significant but too small to be relevant. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
This should fix the CI error encountered in #94774 (and multiple others).
cc @nikic