ci: split x86_64-gnu-tools job #142245
ci: split x86_64-gnu-tools job #142245
Conversation
rustbot
added
A-testsuite
|
trying to write in the cache. @bors2 try |
ci: split x86_64-gnu-tools job
<!-- homu-ignore:start -->
<!--
If this PR is related to an unstable feature or an otherwise tracked effort,
please link to the relevant tracking issue here. If you don't know of a related
tracking issue or there are none, feel free to ignore this.
This PR will get automatically assigned to a reviewer. In case you would like
a specific user to review your work, you can assign it to them by using
r? <reviewer name>
-->
r? `@ghost`
<!-- homu-ignore:end -->
try-job: x86_64-gnu-tools
try-job: x86_64-gnu-miri
|
💔 Test failed
|
This comment has been minimized.
This comment has been minimized.
marcoieni
force-pushed
the
split-gnu-tools
branch
from
f983d2f to
269bff1
Compare
|
@bors2 try |
ci: split x86_64-gnu-tools job
<!-- homu-ignore:start -->
<!--
If this PR is related to an unstable feature or an otherwise tracked effort,
please link to the relevant tracking issue here. If you don't know of a related
tracking issue or there are none, feel free to ignore this.
This PR will get automatically assigned to a reviewer. In case you would like
a specific user to review your work, you can assign it to them by using
r? <reviewer name>
-->
r? `@ghost`
<!-- homu-ignore:end -->
try-job: x86_64-gnu-tools
try-job: x86_64-gnu-miri
|
Timing looks aligned with the rest of the PR jobs r? @Kobzol |
rustbot
added
the
S-waiting-on-review
There was a problem hiding this comment.
Here (https://github.com/rust-lang/rust/actions/runs/15537420813/job/43739929375) the miri job took almost hour and a half :(
|
@bors2 try |
ci: split x86_64-gnu-tools job
<!-- homu-ignore:start -->
<!--
If this PR is related to an unstable feature or an otherwise tracked effort,
please link to the relevant tracking issue here. If you don't know of a related
tracking issue or there are none, feel free to ignore this.
This PR will get automatically assigned to a reviewer. In case you would like
a specific user to review your work, you can assign it to them by using
r? <reviewer name>
-->
Split the job to remove one large runner.
<!-- homu-ignore:end -->
try-job: x86_64-gnu-tools
try-job: x86_64-gnu-miri
marcoieni
force-pushed
the
split-gnu-tools
branch
from
269bff1 to
f30e9c9
Compare
|
@bors try |
ci: split x86_64-gnu-tools job try-job: x86_64-gnu-tools try-job: x86_64-gnu-miri
|
☀️ Try build successful - checks-actions |
|
The PR took 77 minutes. I don't know why the try build takes longer. Should I split the miri job in |
|
Ah, because of this: https://github.com/rust-lang/rust/pull/142245/files#diff-d4ae5ae3c50d051afd7eb52e758cf5de0e2d57d1328a9f620af6c7c9af0a9274R13 It's special-cased to be faster on PRs. Ok, I guess that 77 minutes isn't that terrible. Let's try it. @bors r+ rollup=never Marking as rollup=never because I want to see the test diff on this. |
bors
added
the
S-waiting-on-review
|
Probably this was a flaky error because this PR should be independent from that job, but let's see. @bors2 try |
ci: split x86_64-gnu-tools job
<!-- homu-ignore:start -->
<!--
If this PR is related to an unstable feature or an otherwise tracked effort,
please link to the relevant tracking issue here. If you don't know of a related
tracking issue or there are none, feel free to ignore this.
This PR will get automatically assigned to a reviewer. In case you would like
a specific user to review your work, you can assign it to them by using
r? <reviewer name>
-->
Split the job to remove one large runner.
<!-- homu-ignore:end -->
try-job: x86_64-gnu-tools
try-job: x86_64-gnu-miri
try-job: aarch64-gnu
|
@bors r+ |
|
💡 This pull request was already approved, no need to approve it again.
|
bors
added
S-waiting-on-bors
ci: split x86_64-gnu-tools job try-job: x86_64-gnu-tools try-job: x86_64-gnu-miri try-job: aarch64-gnu
|
wow, this PR must be cursed or something. For some reason, building citool on mac took 1h and 40 minutes. 
|
|
Also other jobs took too much. |
|
💔 Test failed - checks-actions |
bors
added
S-waiting-on-review
|
@bors r=Kobzol |
|
💡 This pull request was already approved, no need to approve it again.
|
bors
added
S-waiting-on-bors
|
the PR failed to be merged for an unrelated error again. |
|
☀️ Test successful - checks-actions |
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing 70e2b4a (parent) -> 2fcf177 (this PR) Test differencesNo test diffs found Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 2fcf1776b9ccef89993dfe40e9f5c4908e2d2d48 --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
Finished benchmarking commit (2fcf177): comparison URL. Overall result: ❌ regressions - no action needed@rustbot label: -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary -0.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -4.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 691.846s -> 692.244s (0.06%) |
Split the job to remove one large runner.
try-job: x86_64-gnu-tools
try-job: x86_64-gnu-miri
try-job: aarch64-gnu