Skip to content

Rollup of 7 pull requests - #162664

Merged
rust-bors[bot] merged 15 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-s1jX04L
Sep 11, 2026
Merged

Rollup of 7 pull requests#162664
rust-bors[bot] merged 15 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-s1jX04L

Conversation

@JonathanBrouwer

Copy link
Copy Markdown
Member

Successful merges:

r? @ghost

Create a similar rollup

cuviper and others added 15 commits August 20, 2026 15:24
* Clarify examples related to `Sync` and `SyncView`

Updated examples to clarify the role of non-`Sync` fields and the functionality of `SyncView`.
* Apply suggestion from @tisonkun
* Update library/core/src/sync/sync_view.rs

Co-authored-by: Laine Taffin Altman <alexanderaltman@me.com>
We have Rust Compiler Development Guide for that.
I've not paid much attention to it in recent times
…r=saethlin

mir-transform: Remove `is_optimization_stage`

Based on rust-lang#160524 until that one is merged

rust-lang#160524 (comment)
Re-export `core::fmt::NumBuffer` in `alloc` (and `std`)

We just stabilized `core::fmt::NumBuffer` in Rust 1.98, but it seems to be a simple oversight that this was not also re-exported in `alloc::fmt` (and `std` just re-exports that whole module). Let's correct that.

I'm marking this stable right away, although I don't think the later `since` version will be properly rendered in docs for a re-export. I'm not sure it's worth trying to clarify that in freeform documentation.
…ail, r=jieyouxu

Prevent `should-fail` to be used in `rustdoc-ui` testsuite

Follow-up of rust-lang#162030 and discussion with @fmease.

There is no reason to use `should-fail` for `rustdoc-ui` (or `rustdoc-html`) testsuite, so let's prevent it.

r? @fmease
Clarify examples related to `Sync` and `SyncView`

Updated examples to clarify the role of non-`Sync` fields and the functionality of `SyncView`.

This refers to rust-lang#98407
… r=jieyouxu

Remove needless test running instructions

We have Rust Compiler Development Guide for that.

r? @jieyouxu
…atrieb

Remove noras target docs mention

I've not paid much attention to it in recent times
@rust-bors rust-bors Bot added the rollup A PR which is a rollup label Sep 11, 2026
@rustbot rustbot added A-CI Area: Our Github Actions CI A-compiletest Area: The compiletest test runner A-meta Area: Issues & PRs about the rust-lang/rust repository itself A-run-make Area: port run-make Makefiles to rmake.rs A-testsuite Area: The testsuite used to check the correctness of rustc 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-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. labels Sep 11, 2026
@JonathanBrouwer

Copy link
Copy Markdown
Member Author

@bors r+ p=5

@rust-bors

rust-bors Bot commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

📌 Commit 220a269 has been approved by JonathanBrouwer

It is now in the queue for this repository.

@rust-bors rust-bors Bot added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Sep 11, 2026
@rust-bors rust-bors Bot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Sep 11, 2026
@rust-bors

This comment has been minimized.

@rust-bors rust-bors Bot added merged-by-bors This PR was explicitly merged by bors. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Sep 11, 2026
@rust-bors

rust-bors Bot commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

☀️ Test successful - CI
Approved by: JonathanBrouwer
Duration: 3h 12m 18s
Pushing 0fc1413 to main...

@rust-bors
rust-bors Bot merged commit 0fc1413 into rust-lang:main Sep 11, 2026
14 checks passed
@rustbot rustbot added this to the 1.100.0 milestone Sep 11, 2026
@github-actions

Copy link
Copy Markdown
Contributor
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 3fbb92e (parent) -> 0fc1413 (this PR)

Test differences

Show 16 test diffs

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

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 0fc141305da7a8a222f65aef1f1acc739c46282b --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-gnu-llvm-21-3: 1h 12m -> 1h 49m (+51.4%)
  2. dist-x86_64-solaris: 1h 13m -> 1h 46m (+44.4%)
  3. test-x86_64-gnu-debug: 2h 6m -> 1h 12m (-42.7%)
  4. test-x86_64-gnu-llvm-22-3: 1h 48m -> 1h 6m (-38.6%)
  5. test-i686-gnu-1: 1h 41m -> 2h 15m (+34.0%)
  6. test-various: 2h 9m -> 1h 25m (-33.9%)
  7. dist-x86_64-msvc: 2h 23m -> 3h 9m (+32.8%)
  8. dist-x86_64-llvm-mingw: 1h 41m -> 2h 13m (+32.1%)
  9. test-x86_64-gnu-llvm-21: 50m 55s -> 36m 9s (-29.0%)
  10. test-x86_64-mingw-1: 2h 23m -> 3h 4m (+28.4%)
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

Copy link
Copy Markdown
Collaborator

Finished benchmarking commit (0fc1413): comparison URL.

Overall result: ✅ improvements - no action needed

@rustbot label: -perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-0.2% [-0.2%, -0.2%] 2
All ❌✅ (primary) - - 0

Max RSS (memory usage)

Results (primary 1.3%, secondary 1.0%)

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

mean range count
Regressions ❌
(primary)
1.9% [0.4%, 3.0%] 3
Regressions ❌
(secondary)
2.6% [1.9%, 3.2%] 3
Improvements ✅
(primary)
-0.5% [-0.5%, -0.5%] 1
Improvements ✅
(secondary)
-4.0% [-4.0%, -4.0%] 1
All ❌✅ (primary) 1.3% [-0.5%, 3.0%] 4

Cycles

Results (primary 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.9% [0.4%, 2.3%] 9
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-0.9% [-2.4%, -0.5%] 8
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 0.1% [-2.4%, 2.3%] 17

Binary size

Results (primary 0.1%, 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.1% [0.0%, 0.2%] 85
Regressions ❌
(secondary)
0.1% [0.0%, 0.2%] 59
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 0.1% [0.0%, 0.2%] 85

Bootstrap: 492.981s -> 492.706s (-0.06%)
Artifact size: 406.85 MiB -> 406.91 MiB (0.01%)

@rust-bors

rust-bors Bot commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#161413 mir-transform: Remove is_optimization_stage 2fd3a959386fa950d9f9a8eacb9026bac9138097
(link)
#161430 Re-export core::fmt::NumBuffer in alloc (and std) 26d5c618d3af505a2e5d68774b61d84e4cd3d8a6
(link)
#162446 Prevent should-fail to be used in rustdoc-ui testsuite 30fa8b118e54f5e870c7a9911f91e78fcebd3b86
(link)
#162621 Clarify examples related to Sync and SyncView 7c7786f05c5f3b300020685c78fd2c73678b64a4
(link)
#162650 Initialize mingw for all mingw targets 8e8cfdb3ed2cd5515b2a33d27b7b153ef3901c42
(link)
#162651 Remove needless test running instructions e091a49434f79cd7a85786cac7d0f2f3b417f146
(link)
#162658 Remove noras target docs mention b4ba5560b71fa34e2460bb353ebedd6650fbe0da
(link)

parent commit: 3fbb92e141

In the case of a perf regression, run the following command for each PR you suspect might be the cause: @rust-timer build $SHA

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-CI Area: Our Github Actions CI A-compiletest Area: The compiletest test runner A-meta Area: Issues & PRs about the rust-lang/rust repository itself 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. rollup A PR which is a rollup 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-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants