Skip to content

Conversation

matthiaskrgr
Copy link
Member

@matthiaskrgr matthiaskrgr commented Oct 7, 2025

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

Muscraft and others added 17 commits October 2, 2025 05:45
…x, r=Zalathar

Use declarative macro for `#[derive(TryFromU32)]`

cc ``@Zalathar``
…avidtwco

test: Subtract code_offset from width for ui_testing

`annotate-snippets` does not have a "UI test" mode like `rustc`, [where the code offset is not subtracted from the column width](https://github.com/rust-lang/rust/blob/f34ba774c78ea32b7c40598b8ad23e75cdac42a6/compiler/rustc_errors/src/emitter.rs#L1985-L1987). This makes it so `annotate-snippets` will shift the output for some very long tests 5 - 7 columns to the left. As part of my work to have `rustc` use `annotate-snippets`, and to reduce the test differences between the two, I figured it would be best if `rustc` started subtracting the code offset from the width as well.

The first commit exists to keep the test output changes of adding a new line to a test separate from adding the `--diagnostic-width` flag in the second commit. This makes it easier to verify that adding the flag does not affect the test's output.

[Zulip discussion](https://rust-lang.zulipchat.com/#narrow/channel/147480-t-compiler.2Fdiagnostics/topic/annotate-snippets.20hurdles)
…-highlight-span, r=estebank

Fix wrong span for hightlight for duplicated diff lines

Fixes rust-lang#147070

From comments: rust-lang#147070 (comment)
The lightlight row for diff must at least 2.

r? `@estebank`
…Kivooeo,jackh726

Improve diagnostics: update note and add help message

I moved the content from the note to a help message, as it seemed more appropriate there, and then added new information to the note(`Modules are usually placed outside of blocks, at the top level of the file`)!

resolve: rust-lang#147314
…ments, r=kobzol

Fluent tidy improvements

Follow-up of rust-lang#147345 and of rust-lang#147191.

It uses `fluent_syntax` to parse `fluent` files (but not for blessing, not even sure how the current one works).

I also added an `assert` to ensure we never go to previous situation where the `fluent` files were actually not checked at all.

cc ``@Kivooeo``
r? kobzol
Update books

## rust-lang/reference

4 commits in e11adf6016a362766eea5a3f9832e193994dd0c8..8efb9805686722dba511b7b27281bb6b77d32130
2025-10-06 15:04:20 UTC to 2025-10-01 17:30:01 UTC

- Clarify that "or it is dropped" is meant restrictively (rust-lang/reference#2035)
- add lifetime extension tests for tuple struct temporaries (rust-lang/reference#2033)
- Add `target_env = "macabi"` and `target_env = "sim"` (rust-lang/reference#1781)
- Typo fixes for the Tokens page (additions -> editions) (rust-lang/reference#2031)
…, r=fmease

don't panic on extern with just multiple quotes in the name

Continues rust-lang#147377.
That PR fixed ICE when the extern name was a single quote `"'"`, but multiple quotes like `"''"` cause the same problem.
I had a random revelation that the trimming can remove more than one quote.
r? ``@nnethercote``
@rustbot rustbot added A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-tidy Area: The tidy tool 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-clippy Relevant to the Clippy team. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. rollup A PR which is a rollup labels Oct 7, 2025
@matthiaskrgr
Copy link
Member Author

@bors r+ rollup=never p=5

@bors
Copy link
Collaborator

bors commented Oct 7, 2025

📌 Commit 21bf6db has been approved by matthiaskrgr

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 Oct 7, 2025
@bors
Copy link
Collaborator

bors commented Oct 7, 2025

⌛ Testing commit 21bf6db with merge 4a54b26...

@bors
Copy link
Collaborator

bors commented Oct 7, 2025

☀️ Test successful - checks-actions
Approved by: matthiaskrgr
Pushing 4a54b26 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Oct 7, 2025
@bors bors merged commit 4a54b26 into rust-lang:master Oct 7, 2025
11 checks passed
@rustbot rustbot added this to the 1.92.0 milestone Oct 7, 2025
@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#145495 Use declarative macro for #[derive(TryFromU32)] 160a5ffcfbb52bf739aa58c53195f64ac90f6791 (link)
#147165 test: Subtract code_offset from width for ui_testing 79e4b1c3285b41cdde7d0968b9eaaa3ce95e4f2a (link)
#147354 Fix wrong span for hightlight for duplicated diff lines dc4f2b98cbb0acf568dd742626a2cfe21b5db0f0 (link)
#147395 Improve diagnostics: update note and add help message ad05e8916e2e3fcff18425c49765798410cb357c (link)
#147396 Fluent tidy improvements 22a3ce1c27f68c9282788305593980b7e5a4d6bb (link)
#147407 Update books 6db353cebcf22a0803bca37d0222667afd3c063a (link)
#147413 don't panic on extern with just multiple quotes in the name 7c90685f5e65a4dd27955c4def37843ee6b5b06e (link)

previous master: d773bd07d6

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

Copy link
Contributor

github-actions bot commented Oct 7, 2025

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 d773bd0 (parent) -> 4a54b26 (this PR)

Test differences

Show 29 test diffs

Stage 1

  • [ui] tests/ui-fulldeps/try-from-u32/errors.rs: ignore (up-to-date) -> [missing] (J1)
  • [ui] tests/ui-fulldeps/try-from-u32/hygiene.rs: ignore (up-to-date) -> [missing] (J1)
  • [ui] tests/ui-fulldeps/try-from-u32/values.rs: ignore (up-to-date) -> [missing] (J1)
  • [ui] tests/ui/argument-suggestions/wrong-highlight-span-extra-arguments-147070.rs: [missing] -> pass (J1)
  • [ui] tests/ui/directory_ownership/file-mod-restriction.rs: [missing] -> pass (J1)
  • [ui] tests/ui/directory_ownership/non-inline-mod-restriction.rs: pass -> [missing] (J1)
  • [ui] tests/ui/extern/extern-only-quotes-issue-147365.rs: [missing] -> pass (J1)
  • [ui] tests/ui/extern/extern-single-quote-issue-147365.rs: pass -> [missing] (J1)

Stage 2

  • [ui] tests/ui/directory_ownership/file-mod-restriction.rs: [missing] -> pass (J0)
  • [ui] tests/ui/directory_ownership/non-inline-mod-restriction.rs: pass -> [missing] (J0)
  • [ui] tests/ui-fulldeps/try-from-u32/errors.rs: pass -> [missing] (J2)
  • [ui] tests/ui-fulldeps/try-from-u32/hygiene.rs: pass -> [missing] (J2)
  • [ui] tests/ui-fulldeps/try-from-u32/values.rs: pass -> [missing] (J2)
  • [ui] tests/ui/argument-suggestions/wrong-highlight-span-extra-arguments-147070.rs: [missing] -> ignore (only executed when the operating system is linux) (J3)
  • [ui] tests/ui/extern/extern-only-quotes-issue-147365.rs: [missing] -> pass (J4)
  • [ui] tests/ui/extern/extern-single-quote-issue-147365.rs: pass -> [missing] (J4)
  • [ui] tests/ui/extern/extern-only-quotes-issue-147365.rs: [missing] -> ignore (ignored if rustc wasn't built with debug assertions) (J5)
  • [ui] tests/ui/extern/extern-single-quote-issue-147365.rs: ignore (ignored if rustc wasn't built with debug assertions) -> [missing] (J5)
  • [ui] tests/ui/argument-suggestions/wrong-highlight-span-extra-arguments-147070.rs: [missing] -> pass (J6)

Additionally, 10 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 4a54b26d30dac43778afb0e503524b763fce0eee --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. aarch64-apple: 6935.4s -> 9389.9s (35.4%)
  2. dist-x86_64-apple: 6142.2s -> 7843.4s (27.7%)
  3. pr-check-1: 1364.4s -> 1598.6s (17.2%)
  4. x86_64-gnu-llvm-20: 2360.8s -> 2752.6s (16.6%)
  5. dist-x86_64-msvc-alt: 10835.9s -> 9219.8s (-14.9%)
  6. aarch64-gnu-llvm-20-2: 2217.6s -> 2494.8s (12.5%)
  7. i686-gnu-nopt-1: 7179.9s -> 8058.0s (12.2%)
  8. dist-x86_64-musl: 7663.8s -> 8524.6s (11.2%)
  9. aarch64-gnu-llvm-20-1: 3381.2s -> 3732.1s (10.4%)
  10. armhf-gnu: 4791.4s -> 5275.1s (10.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
Copy link
Collaborator

Finished benchmarking commit (4a54b26): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

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

Max RSS (memory usage)

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

Cycles

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

Binary size

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

Bootstrap: 473.455s -> 473.216s (-0.05%)
Artifact size: 388.39 MiB -> 388.39 MiB (-0.00%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-tidy Area: The tidy tool merged-by-bors This PR was explicitly merged by bors. rollup A PR which is a rollup 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-clippy Relevant to the Clippy team. 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.

10 participants