Rollup of 11 pull requests - #162434
Conversation
This updates the rust-version file to 71238e2.
Pull recent changes from https://github.com/rust-lang/rust via Josh. Upstream ref: rust-lang/rust@71238e2 Filtered ref: rust-lang/rustc-dev-guide@1cf0a36 Upstream diff: rust-lang/rust@da51146...71238e2 This merge was created using https://github.com/rust-lang/josh-sync.
Rustc pull update
…O is enabled The parallel frontend makes the cookies nondeterministic in their current form, resulting in nondeterministic outputs when bitcode is emitted or LTO is used. Causes minor diagnostic regression for inline asm in release builds.
…const_check function
This updates the rust-version file to 32d94cc.
Pull recent changes from https://github.com/rust-lang/rust via Josh. Upstream ref: rust-lang/rust@32d94cc Filtered ref: rust-lang/rustc-dev-guide@7cbd4c9 Upstream diff: rust-lang/rust@71238e2...32d94cc This merge was created using https://github.com/rust-lang/josh-sync.
…c-pull Rustc pull update
…e-test-link Update links for test-x86_64-gnu-debug and test-aarch64-gnu-debug
This test demonstrates the existing crash, and will be migrated to a successful coverage test in a subsequent commit. Co-Authored-By: Rachel Barker <rachel.barker@ferrous-systems.com>
Compile-time-only functions don't generate code, so instrumenting them for coverage is useless. This also avoids an ICE when trying to get the function's symbol name for an unused-function record, which can occur when instrumenting `core`. Co-Authored-By: Rachel Barker <rachel.barker@ferrous-systems.com>
In all cases, the caller was passing `&self.thir[scrutinee_id].span`, which can just as easily be done by the callee. There's no need to add confusion by passing a separate span.
Rollup of 11 pull requests try-job: dist-various-1 try-job: test-various try-job: test-x86_64-gnu-aux try-job: test-x86_64-gnu-llvm-21-3 try-job: test-x86_64-msvc-1 try-job: test-aarch64-apple-1 try-job: test-aarch64-apple-2 try-job: test-x86_64-mingw-1 try-job: test-i686-msvc-1 try-job: test-i686-msvc-2 try-job: test-armhf-gnu
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
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 752b9bf (parent) -> f0bbd8d (this PR) Test differencesShow 168 test diffsStage 1
Stage 2
Additionally, 148 doctest diffs were found. These are ignored, as they are noisy. Job group index
Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard f0bbd8dfa962017309286c7feeea8b2ef9a881b0 --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
Finished benchmarking commit (f0bbd8d): 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 (primary 0.7%, secondary 3.3%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 0.3%)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: 481.658s -> 479.3s (-0.49%) |
|
📌 Perf builds for each rolled up PR:
parent commit: 752b9bf879 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Successful merges:
threads::spawnning loop not reproducible #150451)scrutinee_spanto some MIR-build methods #162420 (mir_build: Don't pass a redundantscrutinee_spanto some MIR-build methods)r? @ghost
Create a similar rollup