Skip to content

Rollup of 5 pull requests #142901

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 11 commits into from
Jun 23, 2025
Merged

Rollup of 5 pull requests #142901

merged 11 commits into from
Jun 23, 2025

Conversation

matthiaskrgr
Copy link
Member

@matthiaskrgr matthiaskrgr commented Jun 23, 2025

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

Mark-Simulacrum and others added 11 commits June 21, 2025 11:17
Co-authored-by: 许杰友 Jieyou Xu (Joe) <39484203+jieyouxu@users.noreply.github.com>
Co-authored-by: Jieyou Xu <jieyouxu@outlook.com>
Signed-off-by: Jonathan Brouwer <jonathantbrouwer@gmail.com>
…on, r=jieyouxu

Document subdirectories of UI tests with README files

Part of rust-lang#133895 and the [2025 Google Summer of Code](https://blog.rust-lang.org/2025/05/08/gsoc-2025-selected-projects/) associated project.

When adding a new UI test, one is faced with hundreds of subdirectories in `tests/ui` reflecting various categories. Knowing where to put the new test is not trivial, as many of the categories have slightly misleading names. For example, `moves` does not only refer to the `move` keyword but to functions taking ownership in general, whereas `allocator` does not refer to allocation in general but rather to the very specific `allocator_api` and `global_allocator` features.

Many contributors will therefore place their test at the top level of ̀`tests/ui` where it will be mixed with hundreds of unrelated tests.

This PR is a tentative move towards more clearly defined tag/categories, with a SUMMARY.md file documenting the true purpose of each subdirectory, placed inside `tests/ui`.

r? ``@jieyouxu``
…r=jdonszelmann

Port `#[no_mangle]` to new attribute parsing infrastructure

Ports `no_mangle` to the new attribute parsing infrastructure for rust-lang#131229 (comment)

r? ``@jdonszelmann``
…imulacrum

1.88.0 release notes

r? cuviper
…-alignment, r=workingjubilee

centralize `-Zmin-function-alignment` logic

tracking issue: rust-lang#82232
discussed in: rust-lang#142824 (comment)

Apply the `-Zmin-function-alignment` value to the alignment field of the function attributes when those are created, so that individual backends don't need to consider it.

The one exception right now is cranelift, because it can't yet set the alignment for individual functions, but it can (and does) set the global minimum function alignment.

cc ``@RalfJung`` I think this is an improvement regardless, is there anything else that should be done for miri?
…version-update, r=Kobzol

Check rustdoc-json-types FORMAT_VERSION is correctly updated

Follow-up of rust-lang#142677.

``@nnethercote`` suggested that we should also ensure that the `FORMAT_VERSION` was only increased by 1 and we should check for it, this PR does it.

cc ``@aDotInTheVoid``
r? ghost
@rustbot rustbot added A-attributes Area: Attributes (`#[…]`, `#![…]`) 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-rustdoc-json Area: Rustdoc JSON backend 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-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-release Relevant to the release subteam, 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. rollup A PR which is a rollup labels Jun 23, 2025
@matthiaskrgr
Copy link
Member Author

@bors r+ rollup=never p=5

@bors
Copy link
Collaborator

bors commented Jun 23, 2025

📌 Commit 1104920 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 Jun 23, 2025
@bors
Copy link
Collaborator

bors commented Jun 23, 2025

⌛ Testing commit 1104920 with merge 22be76b...

@bors
Copy link
Collaborator

bors commented Jun 23, 2025

☀️ Test successful - checks-actions
Approved by: matthiaskrgr
Pushing 22be76b to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Jun 23, 2025
@bors bors merged commit 22be76b into rust-lang:master Jun 23, 2025
11 checks passed
@rustbot rustbot added this to the 1.89.0 milestone Jun 23, 2025
@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#141597 Document subdirectories of UI tests with README files dd63e1a0c4a652792ad704feb448dc2b4362a5a9 (link)
#142823 Port #[no_mangle] to new attribute parsing infrastructure 7e24ad94206aa185ada3b86abcfbd8d776bac1e5 (link)
#142828 1.88.0 release notes 21ff5bd629200bf99c7e5ddabbfff53534220564 (link)
#142854 centralize -Zmin-function-alignment logic 73f280afd942a0a9f128c84932c4f47db8cea9da (link)
#142875 Check rustdoc-json-types FORMAT_VERSION is correctly updated 853f452401a0fcea65f83c4f983f56e688df152d (link)

previous master: 58d5e11690

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

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 58d5e11 (parent) -> 22be76b (this PR)

Test differences

Show 61 test diffs

Stage 1

  • errors::verify_codegen_ssa_no_mangle_nameless_137: [missing] -> pass (J0)

Additionally, 60 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 22be76b7e259f27bf3e55eb931f354cd8b69d55f --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-aarch64-linux: 7897.6s -> 5692.1s (-27.9%)
  2. x86_64-apple-2: 4405.1s -> 5632.2s (27.9%)
  3. x86_64-rust-for-linux: 2910.8s -> 2495.9s (-14.3%)
  4. dist-x86_64-apple: 8213.4s -> 9239.3s (12.5%)
  5. i686-gnu-2: 6092.5s -> 5334.6s (-12.4%)
  6. aarch64-gnu-debug: 4080.9s -> 3652.1s (-10.5%)
  7. dist-aarch64-windows-gnullvm: 5018.5s -> 4498.8s (-10.4%)
  8. i686-gnu-nopt-1: 7803.5s -> 7055.5s (-9.6%)
  9. i686-gnu-1: 7965.4s -> 7215.8s (-9.4%)
  10. x86_64-gnu-llvm-20-1: 3651.5s -> 3322.6s (-9.0%)
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 (22be76b): 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)

Results (secondary 5.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)
5.0% [2.6%, 7.5%] 2
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) - - 0

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: 688.673s -> 689.686s (0.15%)
Artifact size: 371.94 MiB -> 371.95 MiB (0.00%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-attributes Area: Attributes (`#[…]`, `#![…]`) 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-rustdoc-json Area: Rustdoc JSON backend 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-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-release Relevant to the release subteam, 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.

9 participants