Rollup of 5 pull requests#155339
Conversation
Reformat `top_level_options!` and `options!` macro declarations These macros are already tricky, and having weird formatting doesn't help. Using a more regular style makes it easier to see where nesting begins and ends. Extracted from rust-lang#154501 after the changes in rust-lang#149357 made rebasing very difficult. There should be no change to compiler behaviour.
…r=tgross35 bump std libc to `0.2.185` https://github.com/rust-lang/libc/releases/tag/0.2.185 r? tgross35
attribute cleanup: rustc_confusables r? @jdonszelmann
…, r=JohnTitor `CValue::zst()` - add missing "ZST" in docs
…trochenkov various small `rustc_expand` cleanups Each commit should be reviewable on its own.
|
@bors r+ rollup=never p=5 |
This comment has been minimized.
This comment has been minimized.
…uwer Rollup of 5 pull requests Successful merges: - #155331 (Reformat `top_level_options!` and `options!` macro declarations) - #155332 (bump std libc to `0.2.185`) - #155286 (attribute cleanup: rustc_confusables) - #155306 (`CValue::zst()` - add missing "ZST" in docs) - #155311 (various small `rustc_expand` cleanups)
|
💔 Test for 71f4f54 failed: CI. Failed job:
|
|
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) |
|
@bors retry |
This comment has been minimized.
This comment has been minimized.
|
📌 Perf builds for each rolled up PR:
previous master: 32e4c0ecbd 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 32e4c0e (parent) -> 9620eae (this PR) Test differencesShow 2 test diffs2 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 9620eae30ab7614dcb72d44c4ce1dac497f6ae18 --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 (9620eae): 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 -1.8%, secondary 2.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -2.8%)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: 490.627s -> 489.918s (-0.14%) |
Successful merges:
top_level_options!andoptions!macro declarations #155331 (Reformattop_level_options!andoptions!macro declarations)0.2.185#155332 (bump std libc to0.2.185)CValue::zst()- add missing "ZST" in docs #155306 (CValue::zst()- add missing "ZST" in docs)rustc_expandcleanups #155311 (various smallrustc_expandcleanups)r? @ghost
Create a similar rollup