Rollup of 6 pull requests - #161226
Conversation
…ions-on-binders, r=adwinwhite Fix: WF ICE assumptions on binders Fixes rust-lang#160293 `-Zassumptions-on-binders` ICEs because the solver's `well_formed_goals` passes terms with resolvable inference variables to `unnormalized_obligations`, which asserts they're already resolved (unlike other callers). Resolve inference variables before computing WF obligations.
…-set-docs, r=nnethercote Better comments on small copy lists, explaining the limitations better r? @nnethercote > [!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.
…ark-Simulacrum Add nightly-only support for Cargo unremap trim-paths files in `rust-lldb` Same as rust-lang#160560 but for `rust-lldb`. This PR adds support in `rust-lldb` for the un-remapping file produced by Cargo with `-Ztrim-paths` (rust-lang/cargo#17303). This support is nightly-only, and only activated when `RUST_LLDB_TRIM_PATHS=unstable` is set. The processing is identical to the GDB script, the differences are regarding the interaction with LLDB and the need to setup a background thread.
bootstrap: Make various things non-pub - Previously: rust-lang#161157 --- During my quest to move things out of bootstrap's `lib.rs`, I have found several clusters of code that start to emit dead-code warnings when `lib.rs` is cleared out. This PR aims to pre-emptively resolve some of those clusters, by making various things non-pub and dealing with the resulting warnings. There should be no change to bootstrap behaviour.
This comment has been minimized.
This comment has been minimized.
Rollup of 6 pull requests try-job: dist-various-1 try-job: test-various try-job: x86_64-gnu-aux try-job: x86_64-gnu-llvm-21-3 try-job: x86_64-msvc-1 try-job: aarch64-apple-1 try-job: aarch64-apple-2 try-job: x86_64-mingw-1 try-job: i686-msvc-1 try-job: i686-msvc-2
This comment has been minimized.
This comment has been minimized.
|
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)And then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance HTTP 503: No server is currently available to service your request. Sorry about that. Please try resubmitting your request and contact us if the problem persists. (https://api.github.com/graphql) |
|
Finished benchmarking commit (6d656b1): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis perf run didn't have relevant results for this metric. Max RSS (memory usage)Results (secondary 3.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 6.7%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 457.931s -> 468.493s (2.31%) |
|
📌 Perf builds for each rolled up PR:
parent commit: cfadd10310 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Successful merges:
rust-lldb#160869 (Add nightly-only support for Cargo unremap trim-paths files inrust-lldb)lldb-reprtests #161214 (Reduce minimum LLDB to 21.1.0 forlldb-reprtests)lldb_batchmodelints #161216 (Clean up somelldb_batchmodelints)r? @ghost
Create a similar rollup