Rollup of 2 pull requests - #161143
Conversation
Signed-off-by: Amirhossein Akhlaghpour <m9.akhlaghpoor@gmail.com>
…=saethlin fix buggy MaybeDangling<&T> validation logic Fixes a critical regression in rust-lang#160749. This is what caused the trouble in rust-lang/miri#5252. r? @oli-obk or @saethlin
…ssumptions, r=jackh726 Add regression test for rust-lang#159890 Adds regression coverage for rust-lang#159890 The ICE no longer reproduces after the canonical response universe assumptions fix landed. this keeps the original reproducer as a UI test and checks that it reports the expected E0195 and E0046 diagnostics instead of panicking Closes rust-lang#159890
|
@bors r+ p=5 |
This comment has been minimized.
This comment has been minimized.
|
📌 Perf builds for each rolled up PR:
previous master: c9b7f17889 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
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 c9b7f17 (parent) -> 67854e5 (this PR) Test differencesShow 9 test diffsStage 1
Stage 2
Additionally, 6 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 67854e511de21d881bb16426996cd4259d44aa2e --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 (67854e5): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 4.2%, secondary 1.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -2.2%)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: 458.034s -> 459.382s (0.29%) |
|
📌 Perf builds for each rolled up PR:
parent commit: c9b7f17889 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Successful merges:
Nonein context.rs #159890)r? @ghost
Create a similar rollup