Skip to content

Rollup of 5 pull requests - #162640

Merged
rust-bors[bot] merged 15 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-IxgJVAv
Sep 11, 2026
Merged

Rollup of 5 pull requests#162640
rust-bors[bot] merged 15 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-IxgJVAv

Conversation

@JonathanBrouwer

Copy link
Copy Markdown
Member

Successful merges:

r? @ghost

Create a similar rollup

Kobzol and others added 15 commits September 7, 2026 10:26
…ialization to make DefId creation in it deterministic
Instead of Tier 2 without host tools table.
…cnr,BoxyUwU

Rename various resolving functions for consistency, and document them

r? @lcnr or anyone in @rust-lang/initiative-trait-system-refactor

This is all changes from https://github.com/rust-lang/rust/pull/160913/changes that are *just* renames. Updating that PR to be *just* the logic changes

All interesting changes happened in `rustc_infer/src/infer/mod.rs` across all commits. Everything else is renames propagating through other files.

The functions are now called:

| before    |   after  | note |
|---|---|---|
| `shallow_resolve_*` | (unchanged) `shallow_resolve_*` | Now with newly added docs. |
| `resolve_vars_if_possible_*` | `deeply_resolve_ignoring_regions_*` | |
| `eager_resolve_vars` | `deeply_resolve_via_unification_table` | moved onto the `InferCtxtLike` as an inherent method with default body. |
| `fully_resolve` |`deeply_resolve_via_region_graph` | Resolves *with* regions and asserts that all variables are resolved at the end. Note, we only use this function 3x so the long name is ok, it shouldn't be your go-to anyway. |
| `opportunistic_resolve_var` | | gone, same as `shalllow_resolve` now that we resolve to roots |

> [!NOTE]
> I've not used an LLM for any part of this PR, or any other PR I make. This includes any related work like research.
…, r=jieyouxu

Respect `--all-targets` flag when checking the compiler

Chris was trying to get `x check library --all-targets` working in https://rust-lang.zulipchat.com/#narrow/channel/326414-t-infra.2Fbootstrap/topic/Checking.20std.20tests.20without.20building/with/613735399.

I took a look into this and realized that the `x check --all-targets` flag is literally unused - nothing in bootstrap was reading it. So the compiler and library were never checked with `--all-targets`, but on the other hands all tools are checked with `--all-targets` (or equivalent) by default, even without the flag.

The library seems to be broken with `x check --all-targets`, but compiler works. This PR thus enables `--all-targets` for the compiler. Tools are still checked with all targets unconditionally.
…body, r=petrochenkov

Parallel frontend: reproducible coroutine_by_move_body_def_id

Adds test for and fixes `DefId` creation reproducibility issue in `coroutine_by_move_body_def_id` that came up in rust-lang#162202

r? @petrochenkov
…regression, r=petrochenkov

add regression test for RPITIT fulfillment error

Closes rust-lang#159680
…f-target-tier-docs, r=JohnTitor

Move `riscv64im-unknown-none-elf` to Tier 3 table

Instead of Tier 2 without host tools table.

Noticed when looking at `i686-pc-windows-msvc` target docs and rust-lang#113739.
@rust-bors rust-bors Bot added the rollup A PR which is a rollup label Sep 11, 2026
@rustbot rustbot added A-run-make Area: port run-make Makefiles to rmake.rs 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-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. WG-trait-system-refactor The Rustc Trait System Refactor Initiative (-Znext-solver) labels Sep 11, 2026
@JonathanBrouwer

Copy link
Copy Markdown
Member Author

@bors r+ p=5

@rust-bors

rust-bors Bot commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

📌 Commit c6fc90a has been approved by JonathanBrouwer

It is now in the queue for this repository.

@rust-bors rust-bors Bot 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 Sep 11, 2026
@rust-bors

This comment has been minimized.

rust-bors Bot pushed a commit that referenced this pull request Sep 11, 2026
…uwer

Rollup of 5 pull requests

Successful merges:

 - #162126 (Rename various resolving functions for consistency, and document them)
 - #160681 (Respect `--all-targets` flag when checking the compiler)
 - #162580 (Parallel frontend: reproducible coroutine_by_move_body_def_id )
 - #162614 (add regression test for RPITIT fulfillment error)
 - #162626 (Move `riscv64im-unknown-none-elf` to Tier 3 table)
@rust-bors rust-bors Bot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Sep 11, 2026
@rust-bors rust-bors Bot removed the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Sep 11, 2026
@rust-bors

rust-bors Bot commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

💔 Test for 3c4d262 failed: CI. Failed job:

@JonathanBrouwer

Copy link
Copy Markdown
Member Author

@bors retry

@rust-bors rust-bors Bot 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 Sep 11, 2026
@rust-bors

This comment has been minimized.

@rust-bors rust-bors Bot added the merged-by-bors This PR was explicitly merged by bors. label Sep 11, 2026
@rust-bors

rust-bors Bot commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

☀️ Test successful - CI
Approved by: JonathanBrouwer
Duration: 3h 6m 4s
Pushing 3fbb92e to main...

@github-actions

Copy link
Copy Markdown
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 ada41e1 (parent) -> 3fbb92e (this PR)

Test differences

Show 51 test diffs

Stage 1

  • [ui] tests/ui/traits/next-solver/diagnostics/rpitit-fulfillment-error.rs: [missing] -> pass (J2)
  • [ui (polonius)] tests/ui/traits/next-solver/diagnostics/rpitit-fulfillment-error.rs: [missing] -> pass (J4)
  • [run-make] tests/run-make/parallel-reproducible-by-move-body: [missing] -> pass (J6)

Stage 2

  • [run-make] tests/run-make/parallel-reproducible-by-move-body: [missing] -> ignore (ignored when the operating system and target environment are windows-gnu) (J0)
  • [ui] tests/ui/traits/next-solver/diagnostics/rpitit-fulfillment-error.rs: [missing] -> pass (J1)
  • [run-make] tests/run-make/parallel-reproducible-by-move-body: [missing] -> ignore (ignored when cross-compiling) (J3)
  • [run-make] tests/run-make/parallel-reproducible-by-move-body: [missing] -> pass (J5)

Additionally, 44 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 3fbb92e14159dd8b9bdb81e065883d1132e5abb7 --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-x86_64-freebsd: 1h 3m -> 1h 35m (+50.6%)
  2. test-x86_64-gnu-stdlib-semver-check: 16m 25s -> 9m 28s (-42.3%)
  3. test-x86_64-gnu: 1h 49m -> 2h 33m (+39.9%)
  4. test-i686-msvc: 2h 24m -> 1h 31m (-36.6%)
  5. test-x86_64-gnu-gcc-core-tests: 17m 33s -> 11m 51s (-32.5%)
  6. test-x86_64-mingw-2: 1h 42m -> 2h 15m (+31.9%)
  7. dist-x86_64-illumos: 1h 25m -> 1h 52m (+30.6%)
  8. dist-s390x-linux: 1h 11m -> 1h 33m (+30.6%)
  9. test-i686-gnu-1: 2h 22m -> 1h 41m (-29.1%)
  10. test-x86_64-rust-for-linux: 1h 1m -> 44m 8s (-27.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-bors

rust-bors Bot commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#162126 Rename various resolving functions for consistency, and doc… c8c5b351beefa8fcacd7a744e171dd94dc2bc03f
(link)
#160681 Respect --all-targets flag when checking the compiler 4715664bf928f54e52fbbc287eaec408a8bbbe41
(link)
#162580 Parallel frontend: reproducible coroutine_by_move_body_def_… 27ae82c2a9a270eeec520bece3cd110190b52984
(link)
#162614 add regression test for RPITIT fulfillment error 937573842a229fbd36510f93e58853df8b136f6a
(link)
#162626 Move riscv64im-unknown-none-elf to Tier 3 table 8db7ab60d550bcab6e9d9a705a2f21e432e3c999
(link)

parent commit: ada41e1ce8

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
Copy Markdown
Collaborator

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

Max RSS (memory usage)

Results (primary -1.1%, secondary -2.0%)

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

mean range count
Regressions ❌
(primary)
0.4% [0.4%, 0.4%] 1
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-1.6% [-2.2%, -1.2%] 3
Improvements ✅
(secondary)
-2.0% [-2.0%, -2.0%] 1
All ❌✅ (primary) -1.1% [-2.2%, 0.4%] 4

Cycles

Results (primary -0.3%, secondary -2.2%)

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.4%, 2.2%] 8
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-1.3% [-2.6%, -0.6%] 9
Improvements ✅
(secondary)
-2.2% [-2.2%, -2.2%] 1
All ❌✅ (primary) -0.3% [-2.6%, 2.2%] 17

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
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-0.1% [-0.2%, -0.0%] 85
Improvements ✅
(secondary)
-0.1% [-0.2%, -0.0%] 59
All ❌✅ (primary) -0.1% [-0.2%, -0.0%] 85

Bootstrap: 497.659s -> 492.981s (-0.94%)
Artifact size: 406.94 MiB -> 406.85 MiB (-0.02%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-run-make Area: port run-make Makefiles to rmake.rs merged-by-bors This PR was explicitly merged by bors. rollup A PR which is a rollup 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-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. 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.

8 participants