Rollup of 13 pull requests - #161014
Conversation
This comment has been minimized.
This comment has been minimized.
Rollup of 13 pull requests Successful merges: - #160976 (Ensure TLS accesses don't call the global allocator through panic (part 2)) - #160438 ([rustdoc] Change table odd table rows background color to not make it the same as inline code) - #160985 (self-profile more of borrowck) - #137858 (Add new `unused_footnote_definition` rustdoc lint) - #159566 (Add support for generics in `offload`and remove `no_mangle` attribute) - #160676 (rustc_public: split `def`s out of `ty`) - #160861 (rustc_parse: suggest removing semicolon before `if` block) - #160958 (Remove unused `#[non_exhaustive]` in library) - #160978 (move resolve_path to Session inherent method) - #160990 (Remove old cfg parser which is now dead code) - #160991 (Add offload component on nightly) - #160999 (doc changes to expect messages in process.rs) - #161003 (Also warn if an invalid `doc` attribute is used on a macro invocation)
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
💔 Test for d479045 failed: CI. Failed job:
|
This comment has been minimized.
This comment has been minimized.
Rollup of 13 pull requests try-job: dist-x86_64-msvc
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 79ef636 (parent) -> 1e5ee35 (this PR) Test differencesShow 93 test diffsStage 1
Stage 2
Additionally, 72 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 1e5ee356374211706221b71b6106d297a646ee57 --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 |
|
📌 Perf builds for each rolled up PR:
previous master: 79ef636a60 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
|
Finished benchmarking commit (1e5ee35): comparison URL. Overall result: ❌✅ regressions and improvements - please read:Our benchmarks found a performance regression caused by this PR. Next Steps:
@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 7.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -0.4%, secondary -7.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary 0.2%, secondary -7.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 455.642s -> 457.516s (0.41%) |
Successful merges:
unused_footnote_definitionrustdoc lint #137858 (Add newunused_footnote_definitionrustdoc lint)offloadand removeno_mangleattribute #159566 (Add support for generics inoffloadand removeno_mangleattribute)defs out ofty#160676 (rustc_public: splitdefs out ofty)ifblock #160861 (rustc_parse: suggest removing semicolon beforeifblock)#[non_exhaustive]in library #160958 (Remove unused#[non_exhaustive]in library)docattribute is used on a macro invocation #161003 (Also warn if an invaliddocattribute is used on a macro invocation)r? @ghost
Create a similar rollup