-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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 #113588 to fix bootstrap timings #114345
Conversation
Let's see if timings would be fixed |
This comment has been minimized.
This comment has been minimized.
⌛ Trying commit 7c12b2e with merge 75df98292f8a14c854080a4c2bc5de9a8bed029f... |
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (75df98292f8a14c854080a4c2bc5de9a8bed029f): comparison URL. Overall result: no relevant changes - no action neededBenchmarking 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 may lead to changes in compiler perf. @bors rollup=never Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: missing data |
@@ -78,22 +78,13 @@ pub fn rev_exists(rev: &str, git_dir: Option<&Path>) -> Result<bool, String> { | |||
/// We will then fall back to origin/master in the hope that at least this exists. | |||
pub fn updated_master_branch(git_dir: Option<&Path>) -> Result<String, String> { | |||
let upstream_remote = get_rust_lang_rust_remote(git_dir)?; | |||
for upstream_master in [format!("{upstream_remote}/master"), format!("origin/master")] { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it worth checking a revert of just the changes in updated_master_branch? Those are unrelated to the Miri changes, it just seemed reasonable to ensure the remove branch returned here actually exists.
This PR changes how LLVM is built. Consider updating src/bootstrap/download-ci-llvm-stamp. |
there is bootstrap data on the server, so let's land this for now, and figure out how to land the initial PR after that r? @RalfJung |
If it's just some transient .git state, we should be able to fix it on the server, fix the rustc-perf collector, and reland the PR to fix the issue. |
☀️ Test successful - checks-actions |
Finished benchmarking commit (6e6d39a): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 650.695s -> 648.281s (-0.37%) |
This reverts #113588 which seems to have broken perf's bootstrap timings via some git issue
#114318 (comment) show a newly broken benchmark, the error at the time was
If this lands, it will reopen #101907 and annoy miri, but it could actually be an issue that would appear during the next bootstrap bump, not just rustc-perf today.
r? @ghost