Uh oh!
There was an error while loading. Please reload this page.
Lint elided lifetimes in path during lifetime resolution -- variant - #91271
Lint elided lifetimes in path during lifetime resolution -- variant#91271cjgillot wants to merge 7 commits into
Conversation
cjgillot
commented
Nov 26, 2021
@bors try @rust-timer queue |
rust-timer
commented
Nov 26, 2021
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
bors
commented
Nov 26, 2021
⌛ Trying commit e6f5068 with merge 3a16e8d1317082cc536140a5e6f2b312a196a417... |
rust-log-analyzer
commented
Nov 26, 2021
The job Click to see the possible cause of the failure (guessed by this bot) |
bors
commented
Nov 26, 2021
☀️ Try build successful - checks-actions |
rust-timer
commented
Nov 26, 2021
Queued 3a16e8d1317082cc536140a5e6f2b312a196a417 with parent 6d246f0, future comparison URL. |
rust-timer
commented
Nov 27, 2021
Finished benchmarking commit (3a16e8d1317082cc536140a5e6f2b312a196a417): comparison url. Summary: This change led to large relevant mixed results 🤷 in compiler performance.
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR led to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never |
jackh726
commented
Nov 30, 2021
r? @jackh726 see #90446 (comment) |
Variant for #90446
r? @ghost