Skip to content

Conversation

@Zalathar
Copy link
Member

@Zalathar Zalathar commented Nov 4, 2025

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

fneddy and others added 30 commits October 21, 2025 08:30
The tests fail on s390x and presumably other big-endian systems, due
to check of raw alloc values in the MIR output.

To fix the tests remove the raw bytes from the MIR output
(via: compile-flags: -Zdump-mir-exclude-alloc-bytes) and update the
matching diffs.
add tool to "enforce" semantic line breaks
…me-tests-chapters

fix another corner case for sembr tool
Also, tidy does a lot more than follow Rust Style Guide
The first was a warning:
```
Testing stage2 {rustc_parse_format} (aarch64-apple-darwin)
   Compiling rustc_index v0.0.0 (/Users/ci/project/compiler/rustc_index)
error: extern crate `smallvec` is unused in crate `rustc_index`
 --> compiler/rustc_index/src/lib.rs:2:1
  |
2 | #![cfg_attr(all(feature = "nightly", test), feature(stmt_expr_attributes))]
  | ^
  |
  = help: remove the dependency or add `use smallvec as _;` to the crate root
  = note: `-D unused-crate-dependencies` implied by `-D warnings`
  = help: to override `-D warnings` add `#[allow(unused_crate_dependencies)]`

error: could not compile `rustc_index` (lib) due to 1 previous error
```

The second was that `type_ir_macros` didn't fully specify its
dependencies:
```
Testing stage1 {rustc_type_ir_macros} (aarch64-apple-darwin)
   Compiling rustc_type_ir_macros v0.0.0 (/Users/jyn/src/ferrocene3/compiler/rustc_type_ir_macros)
error[E0432]: unresolved import `syn::visit_mut`
   --> compiler/rustc_type_ir_macros/src/lib.rs:2:10
    |
  2 | use syn::visit_mut::VisitMut;
    |          ^^^^^^^^^ could not find `visit_mut` in `syn`
    |
note: found an item that was configured out
   --> /Users/jyn/.local/lib/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/syn-2.0.106/src/lib.rs:880:21
    |
878 | #[cfg(feature = "visit-mut")]
    |       --------------------- the item is gated behind the `visit-mut` feature
879 | #[cfg_attr(docsrs, doc(cfg(feature = "visit-mut")))]
880 | pub use crate::gen::visit_mut;
    |                     ^^^^^^^^^

error[E0433]: failed to resolve: could not find `visit_mut` in `syn`
   --> compiler/rustc_type_ir_macros/src/lib.rs:206:18
    |
206 |             syn::visit_mut::visit_type_path_mut(self, i);
    |                  ^^^^^^^^^ could not find `visit_mut` in `syn`
    |
note: found an item that was configured out
   --> /Users/jyn/.local/lib/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/syn-2.0.106/src/lib.rs:880:21
    |
878 | #[cfg(feature = "visit-mut")]
    |       --------------------- the item is gated behind the `visit-mut` feature
879 | #[cfg_attr(docsrs, doc(cfg(feature = "visit-mut")))]
880 | pub use crate::gen::visit_mut;
    |                     ^^^^^^^^^
```
This updates the rust-version file to c5dabe8.
Pull recent changes from https://github.com/rust-lang/rust via Josh.

Upstream ref: c5dabe8
Filtered ref: d867ed05e46e3ba4d231efe9df26fcc9310b5d09
Upstream diff: rust-lang/rust@b1b464d...c5dabe8

This merge was created using https://github.com/rust-lang/josh-sync.
This was updated recently.

Also, the annotation was broken, so would not appear in date-check issue.
@bors bors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Nov 4, 2025
@bors
Copy link
Collaborator

bors commented Nov 5, 2025

⌛ Testing commit 41382a4 with merge dbaea8b...

bors added a commit that referenced this pull request Nov 5, 2025
Rollup of 6 pull requests

Successful merges:

 - #147355 (Add alignment parameter to `simd_masked_{load,store}`)
 - #147925 (Fix tests for big-endian)
 - #148341 (compiler: Fix a couple issues around cargo feature unification)
 - #148371 (Dogfood `trim_{suffix|prefix}` in compiler)
 - #148495 (Implement Path::is_empty)
 - #148502 (rustc-dev-guide subtree update)

r? `@ghost`
`@rustbot` modify labels: rollup
@bors
Copy link
Collaborator

bors commented Nov 5, 2025

💔 Test failed - checks-actions

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Nov 5, 2025
@Zalathar
Copy link
Member Author

Zalathar commented Nov 5, 2025

GitHub Actions isn't showing full logs for the failed job, so treating it as runner flakiness. 😿

@bors retry

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

bors commented Nov 5, 2025

⌛ Testing commit 41382a4 with merge 8e0b68e...

@bors
Copy link
Collaborator

bors commented Nov 5, 2025

☀️ Test successful - checks-actions
Approved by: Zalathar
Pushing 8e0b68e to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Nov 5, 2025
@bors bors merged commit 8e0b68e into rust-lang:master Nov 5, 2025
12 checks passed
@rustbot rustbot added this to the 1.93.0 milestone Nov 5, 2025
@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#147355 Add alignment parameter to simd_masked_{load,store} 388aa009604c168f417e75cae4b230f2847fa29b (link)
#147925 Fix tests for big-endian 022be78f8d1b2e2e26ab35e583445b6566b83387 (link)
#148341 compiler: Fix a couple issues around cargo feature unificat… 7afe48e69451ae9eb68b0403acb31d3ce5ee632c (link)
#148371 Dogfood trim_{suffix|prefix} in compiler d302e5c94ab0b680260b5b01bc6c58da71c003c4 (link)
#148495 Implement Path::is_empty 96698bd49ebd63a7c71e286c2b52bfa9cb5d34d4 (link)
#148502 rustc-dev-guide subtree update aa2405f06714f8d71749f6aaa238a8e8d723a71a (link)

previous master: c0ff72ffc4

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

@github-actions
Copy link
Contributor

github-actions bot commented Nov 5, 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 c0ff72f (parent) -> 8e0b68e (this PR)

Test differences

Show 194 test diffs

194 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 8e0b68e63cd2b7b6d18474fe6f49df6fb1570c25 --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-i586-gnu-i586-i686-musl: 5489.2s -> 4844.3s (-11.7%)
  2. x86_64-msvc-2: 6863.9s -> 7623.5s (+11.1%)
  3. dist-aarch64-msvc: 5852.1s -> 5306.9s (-9.3%)
  4. aarch64-msvc-1: 7350.2s -> 6802.7s (-7.4%)
  5. dist-x86_64-solaris: 5145.2s -> 5523.5s (+7.4%)
  6. pr-check-1: 1964.4s -> 1821.6s (-7.3%)
  7. dist-aarch64-apple: 6090.1s -> 6532.1s (+7.3%)
  8. dist-apple-various: 3776.0s -> 4049.3s (+7.2%)
  9. x86_64-rust-for-linux: 2849.7s -> 2646.7s (-7.1%)
  10. dist-i686-mingw: 9784.1s -> 9164.0s (-6.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
Collaborator

Finished benchmarking commit (8e0b68e): comparison URL.

Overall result: ❌✅ regressions and improvements - please read the text below

Our benchmarks found a performance regression caused by this PR.
This might be an actual regression, but it can also be just noise.

Next Steps:

  • If the regression was expected or you think it can be justified,
    please write a comment with sufficient written justification, and add
    @rustbot label: +perf-regression-triaged to it, to mark the regression as triaged.
  • If you think that you know of a way to resolve the regression, try to create
    a new PR with a fix for the regression.
  • If you do not understand the regression or you think that it is just noise,
    you can ask the @rust-lang/wg-compiler-performance working group for help (members of this group
    were already notified of this PR).

@rustbot label: +perf-regression
cc @rust-lang/wg-compiler-performance

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.2% [0.2%, 0.2%] 1
Regressions ❌
(secondary)
0.1% [0.1%, 0.1%] 2
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-0.5% [-0.9%, -0.1%] 8
All ❌✅ (primary) 0.2% [0.2%, 0.2%] 1

Max RSS (memory usage)

Results (primary -0.2%, secondary 3.5%)

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.8%, 0.8%] 1
Regressions ❌
(secondary)
4.1% [1.7%, 6.0%] 10
Improvements ✅
(primary)
-1.2% [-1.2%, -1.2%] 1
Improvements ✅
(secondary)
-3.0% [-3.0%, -3.0%] 1
All ❌✅ (primary) -0.2% [-1.2%, 0.8%] 2

Cycles

Results (primary 3.5%, secondary 2.7%)

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

mean range count
Regressions ❌
(primary)
3.5% [3.5%, 3.5%] 1
Regressions ❌
(secondary)
5.0% [1.3%, 9.7%] 7
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-5.4% [-6.6%, -4.3%] 2
All ❌✅ (primary) 3.5% [3.5%, 3.5%] 1

Binary size

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

Bootstrap: 474.063s -> 475.57s (0.32%)
Artifact size: 390.97 MiB -> 390.76 MiB (-0.05%)

@rustbot rustbot added the perf-regression Performance regression. label Nov 5, 2025
bjorn3 pushed a commit to bjorn3/rust that referenced this pull request Nov 8, 2025
Rollup of 6 pull requests

Successful merges:

 - rust-lang#147355 (Add alignment parameter to `simd_masked_{load,store}`)
 - rust-lang#147925 (Fix tests for big-endian)
 - rust-lang#148341 (compiler: Fix a couple issues around cargo feature unification)
 - rust-lang#148371 (Dogfood `trim_{suffix|prefix}` in compiler)
 - rust-lang#148495 (Implement Path::is_empty)
 - rust-lang#148502 (rustc-dev-guide subtree update)

r? `@ghost`
`@rustbot` modify labels: rollup
@Mark-Simulacrum Mark-Simulacrum added the perf-regression-triaged The performance regression has been triaged. label Nov 11, 2025
@Mark-Simulacrum
Copy link
Member

Regressions look likely to be bimodality to me. Marking as triaged.

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-rustc-dev-guide Area: rustc-dev-guide A-test-infra-minicore Area: `minicore` test auxiliary and `//@ add-core-stubs` merged-by-bors This PR was explicitly merged by bors. perf-regression Performance regression. perf-regression-triaged The performance regression has been triaged. 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-compiler Relevant to the compiler 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. T-rustdoc-frontend Relevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output.

Projects

None yet

Development

Successfully merging this pull request may close these issues.