Uh oh!
There was an error while loading. Please reload this page.
[experiment] perf-test smallvec optimizations - #90673
Conversation
the8472
commented
Nov 7, 2021
@bors try @rust-timer queue |
rust-timer
commented
Nov 7, 2021
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
bors
commented
Nov 7, 2021
⌛ Trying commit 933ba6a236d051bbb3f002fae024f25c24391959 with merge 2652dd606cb092b25cbb78c7f1fce40f343c1ead... |
This comment has been minimized.
This comment has been minimized.
bors
commented
Nov 7, 2021
💔 Test failed - checks-actions |
the8472
commented
Nov 7, 2021
@bors retry |
matthiaskrgr
commented
Nov 7, 2021
@bors r- |
matthiaskrgr
commented
Nov 7, 2021
@bors try @rust-timer queue |
rust-timer
commented
Nov 7, 2021
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
bors
commented
Nov 7, 2021
🔒 Merge conflict This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again. How do I rebase?Assuming
You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial. Please avoid the "Resolve conflicts" button on GitHub. It uses Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Error message |
matthiaskrgr
commented
Nov 7, 2021
Looks like you added an old version of rust-analyzer to pr or something like that..? |
the8472
commented
Nov 7, 2021
"old" being a few hours old here. I de-submoduled it because cargo couldn't vendor it with the custom overrides that I want to test and the overrides can't be applied to a submodule. But something went wrong somewhere. |
210fa25 to
45af45dCompareredid the commits, locally it cleanly merges into master now. @bors try |
the8472
commented
Nov 7, 2021
@bors try |
bors
commented
Nov 8, 2021
🔒 Merge conflict This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again. How do I rebase?Assuming
You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial. Please avoid the "Resolve conflicts" button on GitHub. It uses Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Error message |
bors
commented
Nov 9, 2021
☔ The latest upstream changes (presumably #90695) made this pull request unmergeable. Please resolve the merge conflicts. |
bors
commented
Nov 13, 2021
⌛ Trying commit 92def8dc40e70ed3c51d5e4d24e78e7197a887cd with merge 7dc2b6bb7610455b60e128dfdc8ccce52002f03f... |
bors
commented
Nov 14, 2021
☀️ Try build successful - checks-actions |
rust-timer
commented
Nov 14, 2021
Queued 7dc2b6bb7610455b60e128dfdc8ccce52002f03f with parent d212d90, future comparison URL. |
rust-timer
commented
Nov 14, 2021
Finished benchmarking commit (7dc2b6bb7610455b60e128dfdc8ccce52002f03f): 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 |
92def8d to
179b167Comparethe8472
commented
Nov 23, 2021
Redoing the 2nd perf run now that #90996 has been merged. if that still skews more negative than the first one then my initial attempt will have been the best one and I'll propose that for inclusion in the small-vec crate. @bors try @rust-timer queue |
rust-timer
commented
Nov 23, 2021
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
bors
commented
Nov 23, 2021
🔒 Merge conflict This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again. How do I rebase?Assuming
You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial. Please avoid the "Resolve conflicts" button on GitHub. It uses Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Error message |
179b167 to
f91df9bComparethe8472
commented
Nov 23, 2021
@bors try |
bors
commented
Nov 23, 2021
⌛ Trying commit f91df9b with merge e7d5196be5d77b51272c96329b5d976f449bcefc... |
bors
commented
Nov 23, 2021
💔 Test failed - checks-actions |
rust-log-analyzer
commented
Nov 23, 2021
The job Click to see the possible cause of the failure (guessed by this bot) |
bors
commented
Dec 8, 2021
☔ The latest upstream changes (presumably #91604) made this pull request unmergeable. Please resolve the merge conflicts. |
Mark-Simulacrum
commented
Jul 24, 2022
Going to close this as a no-longer-relevant (I presume) perf experiment. |
r? @ghost