Skip to content

Rollup of 16 pull requests #142483

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 46 commits into from
Jun 14, 2025
Merged

Rollup of 16 pull requests #142483

merged 46 commits into from
Jun 14, 2025

Conversation

workingjubilee
Copy link
Member

@workingjubilee workingjubilee commented Jun 14, 2025

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

lcnr and others added 30 commits June 3, 2025 18:08
Explicitly cross-build it for GPU targets and check it errors on hosts.
The previous method, where a layer would be passed directly,
required to pass a "no-op" layer when no custom layer was needed.
This should have in theory worked, however having a no-op layer
seems to change the way the tracing lib applies filters internally,
leading to some debug!() being printed despite them being out of
the minimum level for the filters. Note however that this behavior
was very inconsistent, and e.g. some debug!() would get printed
and some others wouldn't, for no apparent reason.
Intrinsic functions declared in `std::intrinsics` are an implementation
detail and should not be called directly by the user. The compiler
explicitly warns against their use in user code:

```
warning: the feature `core_intrinsics` is internal to the compiler or standard library
 --> src/lib.rs:1:12
  |
1 | #![feature(core_intrinsics)]
  |            ^^^^^^^^^^^^^^^
  |
  = note: using it is strongly discouraged
  = note: `#[warn(internal_features)]` on by default
```

[**Playground link**]

This PR documents what the compiler warning says: these intrinsics should
not be called outside the standard library.

[**Playground link**]: https://play.rust-lang.org/?version=nightly&mode=debug&edition=2024&gist=1c893b0698291f550bbdde0151fd221b
Confusingly, this does not make compile test print what command is used
to run a ui test:

    ./x test tests/ui/panics/abort-on-panic.rs --verbose

It is also necessary to pass `--no-capture`, like this:

    ./x test tests/ui/panics/abort-on-panic.rs --verbose --no-capture

Now you will see prints like this:

    executing cd "/rust/build/x86_64-unknown-linux-gnu/test/ui/panics/abort-on-panic.next" && \
        RUSTC="/rust/build/x86_64-unknown-linux-gnu/stage1/bin/rustc" \
        RUST_TEST_THREADS="32" \
        "/rust/build/x86_64-unknown-linux-gnu/test/ui/panics/abort-on-panic.next/a"

Add a hint in the code for this that would have helped me figure this out.
Signed-off-by: Jonathan Brouwer <jonathantbrouwer@gmail.com>
…rs, r=ChrisDenton

Add platform support docs & maintainers for *-windows-msvc

Thanks to `@ChrisDenton,` `@dpaoliello,` `@lambdageek` and `@sivadeilra` for agreeing to be target maintainers!

cc rust-lang#113739
…e, r=tgross35

tests: Convert two handwritten minicores to add-core-stubs
@rustbot rustbot added A-compiletest Area: The compiletest test runner 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. WG-trait-system-refactor The Rustc Trait System Refactor Initiative (-Znext-solver) rollup A PR which is a rollup labels Jun 14, 2025
@workingjubilee
Copy link
Member Author

@bors rollup=never p=5 r+

@bors
Copy link
Collaborator

bors commented Jun 14, 2025

📌 Commit 572b452 has been approved by workingjubilee

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

bors commented Jun 14, 2025

⌛ Testing commit 572b452 with merge 64033a4...

@bors
Copy link
Collaborator

bors commented Jun 14, 2025

☀️ Test successful - checks-actions
Approved by: workingjubilee
Pushing 64033a4 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Jun 14, 2025
@bors bors merged commit 64033a4 into rust-lang:master Jun 14, 2025
1 check passed
@rustbot rustbot added this to the 1.89.0 milestone Jun 14, 2025
Copy link
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 64c81fd (parent) -> 64033a4 (this PR)

Test differences

Show 404 test diffs

Stage 1

  • [crashes] tests/crashes/137188.rs: pass -> [missing] (J1)
  • [crashes] tests/crashes/138166.rs: pass -> [missing] (J1)
  • [crashes] tests/crashes/138240.rs: pass -> [missing] (J1)
  • [crashes] tests/crashes/138266.rs: pass -> [missing] (J1)
  • [crashes] tests/crashes/138359.rs: pass -> [missing] (J1)
  • [ui] tests/ui/const-generics/mgca/missing_generic_params.rs: [missing] -> pass (J1)
  • [ui] tests/ui/feature-gates/feature-gate-abi_gpu_kernel.rs: pass -> [missing] (J1)
  • [ui] tests/ui/feature-gates/feature-gate-abi_gpu_kernel.rs#AMDGPU: [missing] -> pass (J1)
  • [ui] tests/ui/feature-gates/feature-gate-abi_gpu_kernel.rs#HOST: [missing] -> pass (J1)
  • [ui] tests/ui/feature-gates/feature-gate-abi_gpu_kernel.rs#NVPTX: [missing] -> pass (J1)
  • [ui] tests/ui/traits/object/no-incomplete-inference.rs#current: [missing] -> pass (J1)
  • [ui] tests/ui/traits/object/no-incomplete-inference.rs#next: [missing] -> pass (J1)
  • vec::test_peek_mut: [missing] -> pass (J3)

Stage 2

  • [crashes] tests/crashes/137188.rs: pass -> [missing] (J0)
  • [crashes] tests/crashes/138166.rs: pass -> [missing] (J0)
  • [crashes] tests/crashes/138240.rs: pass -> [missing] (J0)
  • [crashes] tests/crashes/138266.rs: pass -> [missing] (J0)
  • [crashes] tests/crashes/138359.rs: pass -> [missing] (J0)
  • [ui] tests/ui/const-generics/mgca/missing_generic_params.rs: [missing] -> pass (J2)
  • [ui] tests/ui/feature-gates/feature-gate-abi_gpu_kernel.rs: pass -> [missing] (J2)
  • [ui] tests/ui/feature-gates/feature-gate-abi_gpu_kernel.rs#AMDGPU: [missing] -> pass (J2)
  • [ui] tests/ui/feature-gates/feature-gate-abi_gpu_kernel.rs#HOST: [missing] -> pass (J2)
  • [ui] tests/ui/feature-gates/feature-gate-abi_gpu_kernel.rs#NVPTX: [missing] -> pass (J2)
  • [ui] tests/ui/traits/object/no-incomplete-inference.rs#current: [missing] -> pass (J2)
  • [ui] tests/ui/traits/object/no-incomplete-inference.rs#next: [missing] -> pass (J2)

Additionally, 379 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 64033a4ee541c3e9c178fd593e979c74bb798cdc --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. x86_64-apple-2: 5893.1s -> 4150.9s (-29.6%)
  2. dist-x86_64-apple: 9773.4s -> 7840.8s (-19.8%)
  3. dist-ohos-aarch64: 4043.3s -> 4544.1s (12.4%)
  4. aarch64-apple: 5259.7s -> 4634.0s (-11.9%)
  5. dist-ohos-armv7: 3922.9s -> 4355.5s (11.0%)
  6. dist-arm-linux-gnueabi: 5160.7s -> 4684.8s (-9.2%)
  7. dist-ohos-x86_64: 4102.8s -> 4437.0s (8.1%)
  8. x86_64-mingw-2: 6921.6s -> 7267.2s (5.0%)
  9. dist-powerpc64le-linux-musl: 4776.0s -> 5001.0s (4.7%)
  10. x86_64-gnu-debug: 5884.3s -> 5641.3s (-4.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

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#140969 Allow initializing logger with additional tracing Layer 972be9913871c61f65b5fa516376a067d667f890 (link)
#141352 builtin dyn impl no guide inference 4789e7d00c2c404d9da30e4ea22ed23a5dd7cf74 (link)
#142046 add Vec::peek_mut 623d28fcf72d2ed9cc38b84f6d51607eff1c4959 (link)
#142273 tests: Minicore extern "gpu-kernel" feature test b632b211621844ec62a6c0499a9be6679b22b8c4 (link)
#142302 Rework how the disallowed qualifier in function type diagno… 7e5cd03dd92eed1fd85d0005fba34936e3dbb13c (link)
#142405 Don't hardcode the intrinsic return types twice in the comp… dcbde7578b66b1273342894b847eb095391dd417 (link)
#142434 Pre-install JS dependencies in tidy Dockerfile 575d23236e7f8874c149745e0f68f99ccd72a655 (link)
#142439 doc: mention that intrinsics should not be called in user c… a679bf0cc219d547de17a86727fd6ba6ea995c57 (link)
#142441 Delay replacing escaping bound vars in FindParamInClause 8d6f120c0f6e0f4515f629cb538378700ba6f290 (link)
#142449 Require generic params for const generic params b6df966217ce96ca20d83c049d3f91e311488e74 (link)
#142452 Remove "intermittent" wording from ReadDir 52da83d5ed455cd2cb3ad55461c9f4a02877cda2 (link)
#142459 Remove output helper bootstrap cf86af5f6f42f281dda5cdec168518cf2d439b11 (link)
#142460 cleanup search graph impl f3ff416c4c4e6a7f0bcadaaeb48210339cea3aab (link)
#142461 compiletest: Clarify that --no-capture is needed with `--… d906a0a527f9e73b7e5d974a3a29de13a641e397 (link)
#142475 Add platform support docs & maintainers for *-windows-msvc 6db81305120553e7a90dde7c7214e87dfd7a9960 (link)
#142480 tests: Convert two handwritten minicores to add-core-stubs afb891b226bd132661a8e40f4b0f9c86efeb96d9 (link)

previous master: 64c81fd105

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

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (64033a4): 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%] 3
All ❌✅ (primary) - - 0

Max RSS (memory usage)

Results (secondary 5.9%)

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)
5.9% [3.3%, 8.5%] 2
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) - - 0

Cycles

Results (secondary -1.9%)

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)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-1.9% [-1.9%, -1.9%] 1
All ❌✅ (primary) - - 0

Binary size

Results (secondary -0.0%)

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)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-0.0% [-0.0%, -0.0%] 1
All ❌✅ (primary) - - 0

Bootstrap: 757.551s -> 757.347s (-0.03%)
Artifact size: 372.30 MiB -> 372.22 MiB (-0.02%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-compiletest Area: The compiletest test runner 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 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-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. WG-trait-system-refactor The Rustc Trait System Refactor Initiative (-Znext-solver)
Projects
None yet
Development

Successfully merging this pull request may close these issues.