Skip to content

Conversation

Zalathar
Copy link
Contributor

@Zalathar Zalathar commented Aug 26, 2025

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

epage and others added 30 commits August 20, 2025 15:54
This is to prove that the frontmatter is preserved.

The choices in tests is intended for showing the different parts of the
proposed Style Guide for frontmatters.
previously, this lint did not distinguish between `<img` and `<img>`,
and since the latter should be accepted under html5,
the former was also accepted.

the parser now also handles multi-line tags and multi-line attributes.
Pointers with different residues modulo their least common allocation alignment are never equal.
Pointers to the same static allocation are equal if and only if they have the same offset.
Strictly in-bounds (in-bounds and not one-past-the-end) pointers to different static allocations are always unequal.
A pointer cannot be equal to an integer if `ptr-int` cannot be null.

Also adds more tests for `ptr_guaranteed_cmp`.

Co-authored-by: Ralf Jung <[email protected]>
All function pointers are currently treated as unaligned anyway;
any change implementing function pointer alignment during consteval should add
tests that it works properly on arm::t32 functions.
As opposed to passing it around through Result.
These kinds of warnings can make our test suites fail, so if we want
them, we'll need a different flag.
Keeping it up-to-date with the latest changes/features.
Extend the <target>.optimized-compiler-builtins bootstrap option to accept a
path to a prebuilt compiler-rt builtins library, and update compiler-builtins
to enable optimized builtins without building compiler-rt builtins.
Create a dedicated enum to abstract the different ways compiler-builtins
can be configured.

This also relaxes build.optimized-compiler-builtins to accept the path
of a library to match the behavior of <target>.optimized-compiler-builtins
override.
…mpiler-builtins, r=Kobzol,tgross35

Allow linking a prebuilt optimized compiler-rt builtins library

Extend the <target>.optimized-compiler-builtins bootstrap option to accept a path to a prebuilt compiler-rt builtins library, and update compiler-builtins to enable optimized builtins without building compiler-rt builtins.
…=RalfJung

Implement some more checks in `ptr_guaranteed_cmp`.

* Pointers with different residues modulo their allocations' least common alignment are never equal.
* Pointers to the same static allocation are equal if and only if they have the same offset.
* Pointers to different non-zero-sized static allocations are unequal if both point within their allocation, and not on opposite ends.

Tracking issue for `const_raw_ptr_comparison`: <rust-lang#53020>

This should not affect `is_null`, the only usage of this intrinsic on stable.

Closes rust-lang#144584
…tags-svg-145529, r=GuillaumeGomez

make rustdoc::invalid_html_tags more robust

best reviewed a commit at a time.

I kept finding more edge case so I ended up having to make quite significant changes to the parser in order to make it preserve state across events and handle multiline attributes correctly.

fixes rust-lang#145529
test(rustfmt): Verify frontmatter is preserved

This is to prove that the frontmatter is preserved.

The choices in tests is intended for showing the different parts of the proposed Style Guide for frontmatters (rust-lang#145617).

While rustfmt is developed in a different repo, work involving upstream integration is blocked on some work that is being finished up in that repo.  I was told that it would be ok to post against this repo in the mean time.

Tracking issue: rust-lang#136889
Fix some minor issues in comments

Fix some minor issues in comments
… r=petrochenkov

Handle unwinding fatal errors in codegen workers

Also directly unwind on fatal errors at the point they are emitted inside the codegen backends.

Fixes the coordinator ICE of rust-lang#132240, rust-lang#135075 and rust-lang#145800.
…ieni

Wait for DPkg frontend lock when trying to remove packages

Hopefully this helps with [#t-infra > pr-check-1 fails on "free up disk space"](https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/pr-check-1.20fails.20on.20.22free.20up.20disk.20space.22/with/535794424).

As suggested by riking in [#t-infra > pr-check-1 fails on "free up disk space" @ 💬](https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/pr-check-1.20fails.20on.20.22free.20up.20disk.20space.22/near/535791579), thanks!

r? infra-ci
…w, r=clubby789

compiletest: if a compiler fails, show its output

Before, when working on something like a `rustdoc-js` test, if you made a syntax error in a rust file, you would not get that error output unless you ran with `--verbose`, which would also cause an enormous amount of other output to be printed as well.  This can also lead to frustration in new contributors who don't think to run with `--verbose`.

Now, if rustc or rustdoc is run by compiletest and produces an non-zero exit code, its output will be printed.
Make `x test distcheck` self-contained

Before, the checked components were extracted under the checked out source root, which caused us to test some weird combination of tarball + checkout sources/aritfacts/configuration.

Now `x test distcheck` works with an external temporary directory instead, which should make it self-contained. I also moved some config from the Dockerfile to the test itself, and fixed an issue in tidy that caused `x test tidy` to fail on tarball sources.

I also removed `.args(&builder.config.configure_args)`, because it was passing all kinds of crap from the CI config to the distcheck step, which was making it less reproducible.

Fixes: rust-lang#145183

r? ```@jieyouxu```

try-job: x86_64-gnu-distcheck
Don't show warnings from xcrun with -Zverbose-internals

These kinds of warnings can make our test suite fail spuriously, so if we want them, we'll need a different flag.

This was introduced in rust-lang#131477. Fixes rust-lang#145543.

r? apiraino
```@bors``` rollup
@rustbot rustbot added 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-rustfmt Relevant to the rustfmt team, which will review and decide on the PR/issue. rollup A PR which is a rollup labels Aug 26, 2025
@Zalathar
Copy link
Contributor Author

Subset of #145865.

@bors r+ rollup=never p=5

@bors
Copy link
Collaborator

bors commented Aug 26, 2025

📌 Commit a21c2a6 has been approved by Zalathar

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

bors commented Aug 26, 2025

⌛ Testing commit a21c2a6 with merge d2ec14c...

bors added a commit that referenced this pull request Aug 26, 2025
Rollup of 12 pull requests

Successful merges:

 - #143689 (Allow linking a prebuilt optimized compiler-rt builtins library)
 - #144885 (Implement some more checks in `ptr_guaranteed_cmp`. )
 - #145535 (make rustdoc::invalid_html_tags more robust)
 - #145766 (test(rustfmt): Verify frontmatter is preserved)
 - #145811 (Fix some minor issues in comments)
 - #145814 (Handle unwinding fatal errors in codegen workers)
 - #145815 (Wait for DPkg frontend lock when trying to remove packages)
 - #145821 (compiletest: if a compiler fails, show its output)
 - #145845 (Make `x test distcheck` self-contained)
 - #145847 (Don't show warnings from xcrun with -Zverbose-internals)
 - #145856 (Update books)
 - #145858 (Update wasm-component-ld dependency)

r? `@ghost`
`@rustbot` modify labels: rollup
@rust-log-analyzer
Copy link
Collaborator

A job failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)

@bors
Copy link
Collaborator

bors commented Aug 26, 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 Aug 26, 2025
@Zalathar
Copy link
Contributor Author

@bors retry (502 Bad Gateway)

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

bors commented Aug 26, 2025

⌛ Testing commit a21c2a6 with merge 4356e83...

@bors
Copy link
Collaborator

bors commented Aug 26, 2025

☀️ Test successful - checks-actions
Approved by: Zalathar
Pushing 4356e83 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Aug 26, 2025
@bors bors merged commit 4356e83 into rust-lang:master Aug 26, 2025
11 checks passed
@rustbot rustbot added this to the 1.91.0 milestone Aug 26, 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 ace9a74 (parent) -> 4356e83 (this PR)

Test differences

Show 7 test diffs

Stage 1

  • passes::lint::html_tags::tests::test_extract_tags_nested_unclosed: [missing] -> pass (J0)
  • passes::lint::html_tags::tests::test_extract_tags_taglike_in_attr: [missing] -> pass (J0)
  • passes::lint::html_tags::tests::test_extract_tags_taglike_in_multievent_attr: [missing] -> pass (J0)
  • passes::lint::html_tags::tests::test_extract_tags_taglike_in_multiline_attr: [missing] -> pass (J0)
  • passes::lint::html_tags::tests::test_extract_tags_taglike_in_multiline_multievent_attr: [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 4356e83c77cb28113411fb8e2219127f708095b5 --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: 9481.2s -> 6308.9s (-33.5%)
  2. x86_64-gnu-distcheck: 8246.7s -> 5572.3s (-32.4%)
  3. pr-check-1: 1733.1s -> 1338.3s (-22.8%)
  4. dist-x86_64-apple: 6950.2s -> 8427.4s (21.3%)
  5. x86_64-gnu-nopt: 8765.9s -> 7264.5s (-17.1%)
  6. x86_64-gnu-llvm-19: 2909.4s -> 2493.7s (-14.3%)
  7. aarch64-apple: 5841.5s -> 5109.4s (-12.5%)
  8. i686-gnu-nopt-1: 8397.1s -> 7355.0s (-12.4%)
  9. aarch64-gnu-llvm-19-2: 2586.0s -> 2281.2s (-11.8%)
  10. i686-gnu-1: 8599.4s -> 7590.8s (-11.7%)
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
#143689 Allow linking a prebuilt optimized compiler-rt builtins lib… ddd869d3ce0822b7314f4922673d198b933fa5cb (link)
#144885 Implement some more checks in ptr_guaranteed_cmp. 6f3fe285af3240c13064c7289a3315b5cc3b9fe1 (link)
#145535 make rustdoc::invalid_html_tags more robust 9dd964ab27c9417e65f82f50a9c08553bfd8b1fc (link)
#145766 test(rustfmt): Verify frontmatter is preserved 76e67e7503227da3c2ee4c16071e2f8359304cf0 (link)
#145811 Fix some minor issues in comments 8a9ef094c080f9cfd06398846d3b6fa002c3318e (link)
#145814 Handle unwinding fatal errors in codegen workers a01599355df2f897f1f43bcac6442a075f09e38d (link)
#145815 Wait for DPkg frontend lock when trying to remove packages 6bd0d68c76cbb80639346c86574c49b8adf53a18 (link)
#145821 compiletest: if a compiler fails, show its output 32f0137a9933b01af751f35cf1dde42ee03738bc (link)
#145845 Make x test distcheck self-contained e696f3475d6921350c089a25536a1ff15097eb57 (link)
#145847 Don't show warnings from xcrun with -Zverbose-internals 6e03217655a5d5234aefb197c8b760ae1f1b47eb (link)
#145856 Update books 70cc5b730e8ae011cb125fd348a3fc23f5c0429c (link)
#145858 Update wasm-component-ld dependency ff22287b48de8f259cfba4e698af131310c33a83 (link)

previous master: ace9a74442

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

@Zalathar Zalathar deleted the rollup-lag9tlg branch August 26, 2025 11:41
@rust-timer
Copy link
Collaborator

Finished benchmarking commit (4356e83): 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 (primary -1.2%, secondary -3.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)
2.0% [1.9%, 2.1%] 2
Improvements ✅
(primary)
-1.2% [-2.2%, -0.5%] 4
Improvements ✅
(secondary)
-4.9% [-9.2%, -1.7%] 5
All ❌✅ (primary) -1.2% [-2.2%, -0.5%] 4

Cycles

Results (secondary 2.3%)

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

Binary size

Results (primary 0.1%, secondary 0.1%)

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

mean range count
Regressions ❌
(primary)
0.1% [0.0%, 0.8%] 54
Regressions ❌
(secondary)
0.1% [0.0%, 0.1%] 26
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 0.1% [0.0%, 0.8%] 54

Bootstrap: 468.198s -> 468.126s (-0.02%)
Artifact size: 378.40 MiB -> 391.18 MiB (3.38%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-CI Area: Our Github Actions CI A-compiler-builtins Area: compiler-builtins (https://github.com/rust-lang/compiler-builtins) A-compiletest Area: The compiletest test runner A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-testsuite Area: The testsuite used to check the correctness of rustc 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-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. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. T-rustfmt Relevant to the rustfmt team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.