Finish bumping stage0

[Mark-Simulacrum]

It looks like the last time had left some remaining cfg's -- which made me think
that the stage0 bump was actually successful. This brings us to a released 1.62
beta though.

This now brings us to cfg-clean, with the exception of check-cfg-features in bootstrap;
I'd prefer to leave that for a separate PR at this time since it's likely to be more tricky.

cc #97147 (comment)

r? @pietroalbini

[rust-highfive]

Hey! It looks like you've submitted a new PR for the library teams!

If this PR contains changes to any rust-lang/rust public library APIs then please comment with r? rust-lang/libs-api @rustbot label +T-libs-api -T-libs to request review from a libs-api team reviewer. If you're unsure where your change falls no worries, just leave it as is and the reviewer will take a look and make a decision to forward on if necessary.

Examples of T-libs-api changes:

• Stabilizing library features
• Introducing insta-stable changes such as new implementations of existing stable traits on existing stable types
• Introducing new or changing existing unstable library APIs (excluding permanently unstable features / features without a tracking issue)
• Changing public documentation in ways that create new stability guarantees
• Changing observable runtime behavior of library APIs

[pietroalbini]

@bors r+

[bors]

📌 Commit 800ecb890ecfbf5075119db76e4f40c3a4dfdebf has been approved by pietroalbini

[bors]

☔ The latest upstream changes (presumably #97239) made this pull request unmergeable. Please resolve the merge conflicts.

[bors]

🔒 Merge conflict

This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again.

How do I rebase?

Assuming self is your fork and upstream is this repository, you can resolve the conflict following these steps:

1. git checkout stage0-bump (switch to your branch)
2. git fetch upstream master (retrieve the latest master)
3. git rebase upstream/master -p (rebase on top of it)
4. Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
5. git push self stage0-bump --force-with-lease (update this PR)

You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial.

Please avoid the "Resolve conflicts" button on GitHub. It uses git merge instead of git rebase which makes the PR commit history more difficult to read.

Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Cargo.lock conflict is handled during merge and rebase. This is normal, and you should still perform step 5 to update this PR.

Error message

Auto-merging src/bootstrap/builder.rs
Auto-merging library/core/src/intrinsics.rs
Auto-merging compiler/rustc_trait_selection/src/lib.rs
CONFLICT (content): Merge conflict in compiler/rustc_trait_selection/src/lib.rs
Auto-merging compiler/rustc_session/src/lib.rs
Auto-merging compiler/rustc_middle/src/mir/visit.rs
Auto-merging compiler/rustc_middle/src/lib.rs
Automatic merge failed; fix conflicts and then commit the result.

[Mark-Simulacrum]

@bors r=pietroalbini

[bors]

📌 Commit b454991 has been approved by pietroalbini

[bors]

⌛ Testing commit b454991 with merge f9ca16b18c56e7e2a4996843a84c29dcdb3d53c1...

[bors]

💥 Test timed out

[ehuss]

@bors retry

The operation was canceled. for dist-aarch64-linux near the beginning of the build, but it was never marked as failed.

[rust-log-analyzer]

A job failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

[bors]

⌛ Testing commit b454991 with merge f22d59ab56de7c533c13e094c8e5786cbfe179d0...

[bors]

💔 Test failed - checks-actions

[rust-log-analyzer]

The job armhf-gnu failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

---- [ui] src/test/ui/generic-associated-types/const-generics-gat-in-trait-return-type-2.rs stdout ----

error: test run failed!
status: exit status: 101
command: "/checkout/obj/build/x86_64-unknown-linux-gnu/stage0-tools-bin/remote-test-client" "run" "0" "/checkout/obj/build/x86_64-unknown-linux-gnu/test/ui/generic-associated-types/const-generics-gat-in-trait-return-type-2/a"
--- stdout -------------------------------
uploaded "/checkout/obj/build/x86_64-unknown-linux-gnu/test/ui/generic-associated-types/const-generics-gat-in-trait-return-type-2/a", waiting for result
--- stderr -------------------------------
--- stderr -------------------------------
thread 'main' panicked at 'client.read_exact(&mut header) failed with Connection reset by peer (os error 104)', src/tools/remote-test-client/src/main.rs:310:9
------------------------------------------

[Mark-Simulacrum]

@bors retry armhf-gnu remote client connection reset

[bors]

⌛ Testing commit b454991 with merge bef2b7c...

[bors]

☀️ Test successful - checks-actions
Approved by: pietroalbini
Pushing bef2b7c to master...

[rust-timer]

Finished benchmarking commit (bef2b7c): comparison url.

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

Results

• Primary benchmarks: no relevant changes found
• Secondary benchmarks: mixed results

	mean1	max	count2
Regressions 😿 (primary)	N/A	N/A	0
Regressions 😿 (secondary)	2.4%	3.0%	2
Improvements 🎉 (primary)	N/A	N/A	0
Improvements 🎉 (secondary)	-2.2%	-2.8%	2
All 😿🎉 (primary)	N/A	N/A	0

Cycles

Results

• Primary benchmarks: 😿 relevant regression found
• Secondary benchmarks: mixed results

	mean1	max	count2
Regressions 😿 (primary)	2.4%	2.4%	1
Regressions 😿 (secondary)	2.0%	2.0%	1
Improvements 🎉 (primary)	N/A	N/A	0
Improvements 🎉 (secondary)	-2.4%	-2.4%	1
All 😿🎉 (primary)	2.4%	2.4%	1

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

@rustbot label: -perf-regression

Footnotes

1. the arithmetic mean of the percent change ↩ ↩²

2. number of relevant changes ↩ ↩²

[ehuss]

Filed #97669 to track the armhf-gnu spurious error.