Skip to content

[beta] backports and stage0 bump #141412

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

Merged
merged 12 commits into from
May 25, 2025
Merged

[beta] backports and stage0 bump #141412

merged 12 commits into from
May 25, 2025

Conversation

cuviper
Copy link
Member

@cuviper cuviper commented May 22, 2025

r? cuviper

cuviper and others added 6 commits May 22, 2025 15:38
Unfortunately, multiple people are reporting linker warnings related to
`__rust_no_alloc_shim_is_unstable` after this change. The solution isn't
quite clear yet, let's revert to green for now, and try a reland with a
determined solution for `__rust_no_alloc_shim_is_unstable`.

This reverts commit c8b7f32, reversing
changes made to 667247d.

(cherry picked from commit 734a5b1)
…ad disable problematic test

(cherry picked from commit 6128fca)
@rustbot rustbot added A-run-make Area: port run-make Makefiles to rmake.rs S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-release Relevant to the release subteam, which will review and decide on the PR/issue. labels May 22, 2025
@rustbot

This comment has been minimized.

@cuviper
Copy link
Member Author

cuviper commented May 22, 2025

@bors r+ p=1 rollup=never

@bors
Copy link
Collaborator

bors commented May 22, 2025

📌 Commit 14acce0 has been approved by cuviper

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels May 22, 2025
@bors
Copy link
Collaborator

bors commented May 23, 2025

⌛ Testing commit 14acce0 with merge 343190f...

bors added a commit to rust-lang-ci/rust that referenced this pull request May 23, 2025
[beta] backports and stage0 bump

- bump stage0
- Update the edition guide for let chains rust-lang#140852
- Fix download of GCC from CI on non-nightly channels rust-lang#140901
- Revert "Fix linking statics on Arm64EC rust-lang#140176" rust-lang#141024
- [win][arm64] Remove 'Arm64 Hazard' undocumented MSVC option and instead disable problematic test rust-lang#141045
- Do not call name() on rpitit assoc_item rust-lang#141308

r? cuviper
@rust-log-analyzer

This comment has been minimized.

@bors
Copy link
Collaborator

bors commented May 23, 2025

💔 Test failed - checks-actions

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels May 23, 2025
@jieyouxu
Copy link
Member

jieyouxu commented May 23, 2025

2025-05-23T05:28:45.5158211Z [2025-05-23T05:28:45Z WARN  mdbook::preprocess::cmd] The command wasn't found, is the "gettext" preprocessor installed?
2025-05-23T05:28:45.5159328Z [2025-05-23T05:28:45Z WARN  mdbook::preprocess::cmd] 	Command: mdbook-gettext
2025-05-23T05:28:46.0246711Z Error: Rendering failed
2025-05-23T05:28:46.0247105Z 	Caused By: Unable to copy across static files
2025-05-23T05:28:46.0249027Z 	Caused By: There is not enough space on the disk. (os error 112)

Oh it's this problem...

disk usage:
Filesystem            Size  Used Avail Use% Mounted on
C:/Program Files/Git  150G  120G   31G  80% /

@jieyouxu
Copy link
Member

jieyouxu commented May 23, 2025

You may need to cherry-pick #141023 to beta as well, or pray that you get lucky and roll a Windows Server 2025 image that is not the broken one that doesn't have the D: drive.

Tracking issue for that broken image: #141022

…ages

At the moment, it seems like Windows Server 2025 20250504.1.0 is
misconfigured causing insufficient disk space failures. Temporarily go
back to Windows Server 2022 in the hope that those are not also
misconfigured.

(cherry picked from commit f4ce73e)
@rustbot rustbot added A-testsuite Area: The testsuite used to check the correctness of rustc T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels May 23, 2025
@cuviper
Copy link
Member Author

cuviper commented May 23, 2025

Thanks! I've added that CI change.

@bors r+

@bors
Copy link
Collaborator

bors commented May 23, 2025

📌 Commit 1272ff8 has been approved by cuviper

It is now in the queue for this repository.

@bors bors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label May 24, 2025
@bors
Copy link
Collaborator

bors commented May 24, 2025

⌛ Testing commit 53458c8 with merge ae02e44...

bors added a commit that referenced this pull request May 24, 2025
[beta] backports and stage0 bump

- bump stage0 to 1.87.0
- Update the edition guide for let chains #140852
- Fix download of GCC from CI on non-nightly channels #140901
- Revert "Fix linking statics on Arm64EC #140176" #141024
- [win][arm64] Remove 'Arm64 Hazard' undocumented MSVC option and instead disable problematic test #141045
- Do not call name() on rpitit assoc_item #141308
- Temporarily use Windows Server 2022 instead of Windows Server 2025 images #141023
- Use Docker cache from the current repository #141280
- Move dist-x86_64-linux CI job to GitHub temporarily #141388
- ci: prepare aws access keys for migration #141389

r? cuviper
@rust-log-analyzer

This comment has been minimized.

@bors
Copy link
Collaborator

bors commented May 24, 2025

💔 Test failed - checks-actions

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels May 24, 2025
@Mark-Simulacrum
Copy link
Member

@bors retry

Just in case it's somehow spurious.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels May 24, 2025
This will be used to access secrets once we move off rust-lang-ci.
@rustbot
Copy link
Collaborator

rustbot commented May 25, 2025

⚠️ Warning ⚠️

  • Some commits in this PR modify submodules.
  • There are issue links (such as #123) in the commit messages of the following commits.
    Please remove them as they will spam the issue with references to the commit.

@Mark-Simulacrum
Copy link
Member

@bors r+ rollup=never

Included #141323 -- I think that should fix the remaining gap.

@bors
Copy link
Collaborator

bors commented May 25, 2025

📌 Commit 1718bb2 has been approved by Mark-Simulacrum

It is now in the queue for this repository.

@bors
Copy link
Collaborator

bors commented May 25, 2025

⌛ Testing commit 1718bb2 with merge 4330d60...

bors added a commit that referenced this pull request May 25, 2025
[beta] backports and stage0 bump

- bump stage0 to 1.87.0
- Update the edition guide for let chains #140852
- Fix download of GCC from CI on non-nightly channels #140901
- Revert "Fix linking statics on Arm64EC #140176" #141024
- [win][arm64] Remove 'Arm64 Hazard' undocumented MSVC option and instead disable problematic test #141045
- Do not call name() on rpitit assoc_item #141308
- Temporarily use Windows Server 2022 instead of Windows Server 2025 images #141023
- Use Docker cache from the current repository #141280
- Move dist-x86_64-linux CI job to GitHub temporarily #141388
- ci: prepare aws access keys for migration #141389
- Add bors environment to CI #141323

r? cuviper
@bors
Copy link
Collaborator

bors commented May 25, 2025

💥 Test timed out

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels May 25, 2025
@Mark-Simulacrum
Copy link
Member

@bors r+ rollup=never

Per #t-infra > Commits that have to be backported for CI to work @ 💬 backporting #141078 too.

@bors
Copy link
Collaborator

bors commented May 25, 2025

📌 Commit 5257f89 has been approved by Mark-Simulacrum

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels May 25, 2025
@bors
Copy link
Collaborator

bors commented May 25, 2025

⌛ Testing commit 5257f89 with merge 95597e8...

@bors
Copy link
Collaborator

bors commented May 25, 2025

☀️ Test successful - checks-actions
Approved by: Mark-Simulacrum
Pushing 95597e8 to beta...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label May 25, 2025
@bors bors merged commit 95597e8 into rust-lang:beta May 25, 2025
7 checks passed
@rustbot rustbot added this to the 1.88.0 milestone May 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-run-make Area: port run-make Makefiles to rmake.rs A-testsuite Area: The testsuite used to check the correctness of rustc merged-by-bors This PR was explicitly merged by bors. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. T-release Relevant to the release subteam, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.