-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Bump Fuchsia integration commit #135675
Bump Fuchsia integration commit #135675
Conversation
@bors try |
Bump Fuchsia integration commit This advances Fuchsia to a checkout from 2025-01-13, which corresponds to a recent Rust roll, and hopefully avoids rust-lang#135667, where a repository used by the older version of Rust was accidentally archived and broke checking out the prior version. try-job: x86_64-fuchsia cc `@ehuss`
This advances Fuchsia to a checkout from 2025-01-13, which corresponds to a recent Rust roll, and hopefully avoids rust-lang#135667, where a repository used by the older version of Rust was accidentally archived and broke checking out the prior version. try-job: x86_64-fuchsia
21d5aed
to
37a88ba
Compare
@bors try |
Bump Fuchsia integration commit This advances Fuchsia to a checkout from 2025-01-13, which corresponds to a recent Rust roll, and hopefully avoids rust-lang#135667, where a repository used by the older version of Rust was accidentally archived and broke checking out the prior version. try-job: x86_64-fuchsia cc `@ehuss`
⌛ Trying commit 37a88ba with merge ce3de076dbb498069b8dad34c6edb84dba879452... |
This comment was marked as outdated.
This comment was marked as outdated.
☀️ Try build successful - checks-actions |
Looks good, this will fix bors. r? lqd @bors r+ p=100 |
🌲 The tree is currently closed for pull requests below priority 100. This pull request will be tested once the tree is reopened. |
@bors p=1000 |
Bump Fuchsia integration commit This advances Fuchsia to a checkout from 2025-01-13, which corresponds to a recent Rust roll, and hopefully avoids rust-lang#135667, where a repository used by the older version of Rust was accidentally archived and broke checking out the prior version. try-job: x86_64-fuchsia cc `@ehuss`
⌛ Testing commit 37a88ba with merge e46ac6b710cfa1a647a41e57c9e30ccc29d2775a... |
I went through the queue, ehuss had already retried the ones that had failed due to this issue, and the other PRs were r+ed later without any failures, so when this lands (or if the repo is restored) the tree can be reopened. (I may not be at a computer when that happens, but anyone with r+ can reopen) |
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
@bors retry fucking hell msvc |
⌛ Testing commit 37a88ba with merge bd62a452f45c2386275c5469f9ae390e7de2dc6f... |
If this PR fails again: fuchsia people have said they fixed the repo causing issues for the builder, so we can also try to land the next PR in queue instead of this one. |
☀️ Test successful - checks-actions |
Finished benchmarking commit (bd62a45): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (primary -0.8%, secondary -2.1%)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.
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: 765.445s -> 764.994s (-0.06%) |
This advances Fuchsia to a checkout from 2025-01-13, which corresponds to a recent Rust roll, and hopefully avoids #135667, where a repository used by the older version of Rust was accidentally archived and broke checking out the prior version.
try-job: x86_64-fuchsia
cc @ehuss