-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
handle forced compiler and revert #137476 #138039
handle forced compiler and revert #137476 #138039
Conversation
rustbot has assigned @Mark-Simulacrum. Use |
@onur-ozkan you could try-job the slowest job for a rough measurement (the dist ppcle64 or whatever it's called) that we know regressed in build time |
We don't build tools on try-jobs, but I can add a small patch to force that for testing. |
Yeah, it was the powerpc64 le one, I think (not on PC right now). |
Ah right, I forgot about the try-job tool build distinction again... |
ae78953
to
cd0f743
Compare
Some changes occurred in src/tools/opt-dist cc @Kobzol |
@bors try |
…-tools, r=<try> handle forced compiler and revert rust-lang#137476 Fixes rust-lang#138004 I would appreciate it if we could measure CI pipelines with the current changes to see if this reduces recent CI overhead. cc `@rust-lang/infra` try-job: powerpc64le-unknown-linux-gnu
This comment has been minimized.
This comment has been minimized.
Messed up with the job name on the previous call. @bors try |
…-tools, r=<try> handle forced compiler and revert rust-lang#137476 Fixes rust-lang#138004 I would appreciate it if we could measure CI pipelines with the current changes to see if this reduces recent CI overhead. cc `@rust-lang/infra` try-job: dist-powerpc64le-linux
This comment was marked as outdated.
This comment was marked as outdated.
Try builds are different only for jobs that use the PGO/BOLT optimization pipeline. For the PowerPC job, try job is exactly the same as an auto job. |
|
Yeah, we might want to host the GCC dependencies on our mirrors, I'll open an infra topic. |
For reference, the job duration was ~2h45m before #137476, and ~3h15m after it. |
I have a script that compares the executed bootstrap stages (later I want to add this functionality to #138013), I'll run it on the output once it finishes. So far it seems to be on the slower side though :/ |
☀️ Try build successful - checks-actions |
Signed-off-by: onur-ozkan <work@onurozkan.dev>
Signed-off-by: onur-ozkan <work@onurozkan.dev>
🌲 The tree is currently closed for pull requests below priority 100. This pull request will be tested once the tree is reopened. |
…-tools, r=jieyouxu handle forced compiler and revert rust-lang#137476 Fixes rust-lang#138004 I would appreciate it if we could measure CI pipelines with the current changes to see if this reduces recent CI overhead. cc `@rust-lang/infra` try-job: dist-powerpc64le-linux
(Not a blocker) With this PR, it still seems like it is building the compiler an extra unnecessary time:
I would not expect that second build to the host architecture. I would expect that "stage1" compiler to not be used at all (it is not used for compiling anything, and it is not included in the dist artifacts). Do we know why that is happening? |
(Just noting that this might explain the "missing" 15 minutes). |
@ehuss can you share what |
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
|
Yeah, we can avoid that too, but are you sure that this wasn't happening before #137476? |
☀️ Test successful - checks-actions |
Finished benchmarking commit (e6af292): 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)This benchmark run did not return any relevant results for this metric. CyclesResults (secondary -2.4%)This 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: 773.363s -> 774.453s (0.14%) |
Fixes #138004
I would appreciate it if we could measure CI pipelines with the current changes to see if this reduces recent CI overhead. cc @rust-lang/infra
try-job: dist-powerpc64le-linux