Skip to content
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

Revert "Rollup merge of #80458 - RalfJung:promotion-refactor, r=oli-obk" #80727

Closed
wants to merge 1 commit into from

Conversation

rylev
Copy link
Member

@rylev rylev commented Jan 5, 2021

Reverts #80458 to test for possible performance regressions.

In the latest perf triage, the rollup that the reverted PR was a part of featured a performance regression. We are testing whether the reverted PR was indeed (at least partially) responsible.

This reverts commit 46111c1, reversing
changes made to 1975142.

cc @RalfJung @oli-obk

…, r=oli-obk"

This reverts commit 46111c1, reversing
changes made to 1975142.
@rust-highfive
Copy link
Collaborator

r? @matthewjasper

(rust-highfive has picked a reviewer for you, use r? to override)

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Jan 5, 2021
@matthewjasper matthewjasper removed their assignment Jan 5, 2021
@rylev
Copy link
Member Author

rylev commented Jan 5, 2021

r? @ghost

@rylev
Copy link
Member Author

rylev commented Jan 5, 2021

@bors try @rust-timer queue

@rust-timer
Copy link
Collaborator

Awaiting bors try build completion.

@bors
Copy link
Contributor

bors commented Jan 5, 2021

⌛ Trying commit 39bbc1e with merge aaff735c88fc1381b649ee416dd34a8338c49f67...

@oli-obk
Copy link
Contributor

oli-obk commented Jan 5, 2021

I am fairly certain it can't be due to this PR, since the regression is solely in LLVM optimizations, but let's wait for perf, maybe we promote fewer things now and that makes LLVM take longer (there was a change in that PR that could be breaking, but we have no examples that could even trigger that code)?

@bors
Copy link
Contributor

bors commented Jan 5, 2021

☀️ Try build successful - checks-actions
Build commit: aaff735c88fc1381b649ee416dd34a8338c49f67 (aaff735c88fc1381b649ee416dd34a8338c49f67)

@rust-timer
Copy link
Collaborator

Queued aaff735c88fc1381b649ee416dd34a8338c49f67 with parent 68ec332, future comparison URL.

@rustbot label: +S-waiting-on-perf

@bors
Copy link
Contributor

bors commented Jan 5, 2021

☀️ Try build successful - checks-actions
Build commit: aaff735c88fc1381b649ee416dd34a8338c49f67 (aaff735c88fc1381b649ee416dd34a8338c49f67)

@rustbot rustbot added the S-waiting-on-perf Status: Waiting on a perf run to be completed. label Jan 5, 2021
@rust-timer
Copy link
Collaborator

Finished benchmarking try commit (aaff735c88fc1381b649ee416dd34a8338c49f67): comparison url.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying rollup- to bors.

Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf

@rustbot rustbot removed the S-waiting-on-perf Status: Waiting on a perf run to be completed. label Jan 5, 2021
@rylev
Copy link
Member Author

rylev commented Jan 5, 2021

@oli-obk is correct. It’s not this PR. The search continues.

@rylev rylev closed this Jan 5, 2021
@rylev rylev deleted the revert-80458 branch January 5, 2021 20:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants