Skip to content

Rollup of 2 pull requests - #162456

Merged
rust-bors[bot] merged 4 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-bpMVYlc
Sep 8, 2026
Merged

Rollup of 2 pull requests#162456
rust-bors[bot] merged 4 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-bpMVYlc

Conversation

@JonathanBrouwer

Copy link
Copy Markdown
Member

Successful merges:

r? @ghost

Create a similar rollup

sleepycatcoding and others added 4 commits September 8, 2026 00:36
…mejrs

Forward CfgTrace attributes on EII items

Forwards compiler's synthetic CfgTrace and CfgAttrTrace to EII foreign item and macro. This enables the usage of `#[cfg(..)]`, `#[cfg_attr(..)]` and `cfg_select!` on EII.

Fixes rust-lang#162378.

No LLM was used in the creation of this PR.
…ll, r=jieyouxu

Fix myself on .mailmap once and for all

After a few failed attempts, I finally have it. I learned the git mailmap syntax. This is to celebrate my 500th contrib in thanks.rust-lang.org

Fixes the issue where I'm listed both as "Alejandra González" (currently with 477 points) and "Alejandra Gonzalez" (26 points)
@rust-bors rust-bors Bot added the rollup A PR which is a rollup label Sep 8, 2026
@rustbot rustbot added A-meta Area: Issues & PRs about the rust-lang/rust repository itself S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Sep 8, 2026
@JonathanBrouwer

Copy link
Copy Markdown
Member Author

@bors r+ p=5

@rust-bors

rust-bors Bot commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

📌 Commit 46f0fdd has been approved by JonathanBrouwer

It is now in the queue for this repository.

@rust-bors rust-bors Bot 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 Sep 8, 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 8, 2026
@rust-bors

rust-bors Bot commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

☀️ Test successful - CI
Approved by: JonathanBrouwer
Duration: 3h 4m 47s
Pushing 745de6e to main...

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

github-actions Bot commented Sep 8, 2026

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 a3e94c2 (parent) -> 745de6e (this PR)

Test differences

Show 5 test diffs

Stage 1

  • [ui (polonius)] tests/ui/eii/cfg_on_eii.rs: [missing] -> pass (J1)
  • [ui] tests/ui/eii/cfg_on_eii.rs: [missing] -> pass (J2)

Stage 2

  • [ui] tests/ui/eii/cfg_on_eii.rs: [missing] -> pass (J0)

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

Job group index

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 745de6eca673de5329ec68f2689629a5ca45ab35 --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. dist-x86_64-llvm-mingw: 1h 28m -> 2h 14m (+51.2%)
  2. test-x86_64-gnu-llvm-21: 35m 11s -> 52m 13s (+48.4%)
  3. test-x86_64-gnu-gcc: 1h 25m -> 51m 41s (-39.6%)
  4. dist-aarch64-apple: 1h 43m -> 2h 23m (+38.1%)
  5. dist-powerpc64-linux-gnu: 1h 12m -> 1h 39m (+36.2%)
  6. dist-ohos-x86_64: 1h -> 1h 19m (+33.1%)
  7. test-x86_64-msvc-ext1: 2h 21m -> 1h 35m (-32.6%)
  8. test-armhf-gnu: 1h 8m -> 1h 31m (+32.4%)
  9. test-i686-gnu-1: 2h 10m -> 1h 28m (-32.3%)
  10. dist-various-1: 39m 19s -> 51m 38s (+31.3%)
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 (745de6e): 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 (primary 1.2%)

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

mean range count
Regressions ❌
(primary)
2.2% [0.7%, 3.6%] 2
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-0.7% [-0.7%, -0.7%] 1
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 1.2% [-0.7%, 3.6%] 3

Cycles

Results (primary 0.1%, secondary 0.6%)

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

mean range count
Regressions ❌
(primary)
0.8% [0.6%, 1.0%] 3
Regressions ❌
(secondary)
3.2% [3.2%, 3.2%] 1
Improvements ✅
(primary)
-0.6% [-0.8%, -0.6%] 3
Improvements ✅
(secondary)
-2.0% [-2.0%, -2.0%] 1
All ❌✅ (primary) 0.1% [-0.8%, 1.0%] 6

Binary size

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

Bootstrap: 479.129s -> 478.441s (-0.14%)
Artifact size: 403.56 MiB -> 403.53 MiB (-0.01%)

@rust-bors

rust-bors Bot commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#162433 Forward CfgTrace attributes on EII items c8d3d61ffa429ae3c6b45cf88ea40f4bc0c7521a
(link)
#162447 Fix myself on .mailmap once and for all 257b7f35e1414c08cdd1a9195f9543a6eaa39927
(link)

parent commit: a3e94c2ff5

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-meta Area: Issues & PRs about the rust-lang/rust repository itself merged-by-bors This PR was explicitly merged by bors. rollup A PR which is a rollup T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants