Bump to 1.101.0

[Mark-Simulacrum]

https://forge.rust-lang.org/release/process.html#bump-the-stable-version-number-friday-the-week-before

r? Mark-Simulacrum

[Mark-Simulacrum]

@bors r+ rollup=never p=1

(Needs to land by ~Monday but not otherwise super urgent).

[rust-bors]

📌 Commit a2c55f8 has been approved by Mark-Simulacrum

It is now in the queue for this repository.

[rust-bors]

💔 Test for bc9ce38 failed: CI. Failed job:

• auto - test-armhf-gnu (web logs, enhanced plaintext logs)

[JonathanBrouwer]

@bors retry

[rust-bors]

💔 Test for f5f88b3 failed: CI. Failed job:

• auto - test-i686-gnu-nopt-2 (web logs, enhanced plaintext logs)

[rust-log-analyzer]

The job test-i686-gnu-nopt-2 failed! Check out the build log: (web) (plain enhanced) (plain)

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

[JonathanBrouwer]

@bors retry

[rust-bors]

☀️ Test successful - CI
Approved by: Mark-Simulacrum
Duration: 3h 36s
Pushing a22b02e to main...

[github-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 fd98695 (parent) -> a22b02e (this PR)

Test differences

Show 4 test diffs

Stage 2

• [run-make] tests/run-make/compressed-debuginfo-zstd: pass -> ignore (ignored if LLVM wasn't build with zstd for ELF section compression or LLVM is not the default codegen backend) (J0)

Additionally, 3 doctest diffs were found. These are ignored, as they are noisy.

Job group index

• J0: test-x86_64-gnu-nopt

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard a22b02eaecd6ac937d752139c79d0159c725932d --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

1. test-x86_64-msvc-2: 1h 29m -> 2h 38m (+77.5%)
2. test-arm-android: 1h 18m -> 2h 16m (+73.1%)
3. test-x86_64-gnu-gcc-core-tests: 17m 39s -> 30m 6s (+70.5%)
4. dist-i686-mingw: 33m 33s -> 54m 40s (+62.9%)
5. dist-x86_64-musl: 1h 29m -> 2h 24m (+60.8%)
6. test-x86_64-gnu-next-trait-solver-polonius: 53m 29s -> 1h 21m (+53.1%)
7. test-x86_64-gnu-aux: 1h 34m -> 2h 20m (+49.1%)
8. dist-powerpc64le-linux-musl: 1h 10m -> 1h 43m (+45.9%)
9. dist-x86_64-llvm-mingw: 1h 26m -> 2h 5m (+44.9%)
10. test-i686-gnu-nopt-2: 2h 23m -> 1h 21m (-43.1%)

How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

[rust-timer]

Finished benchmarking commit (a22b02e): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This perf run didn't have relevant results for this metric.

Max RSS (memory usage)

Results (secondary 0.1%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	2.6%	[0.9%, 5.9%]	3
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-3.7%	[-4.3%, -3.1%]	2
All ❌✅ (primary)	-	-	0

Cycles

Results (primary 2.5%, secondary 3.9%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	2.5%	[2.5%, 2.5%]	1
Regressions ❌ (secondary)	7.2%	[0.5%, 10.9%]	8
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-4.9%	[-5.6%, -3.4%]	3
All ❌✅ (primary)	2.5%	[2.5%, 2.5%]	1

Binary size

This perf run didn't have relevant results for this metric.

Bootstrap: 490.11s -> 489.175s (-0.19%)
Artifact size: 406.28 MiB -> 407.02 MiB (0.18%)