Rollup of 3 pull requests#156773
Conversation
We specifically call out that the sign is written for negative integers. This would also ideally be called out in `<iN>::format_into`, but the macro infrastructure for the implementation unfortunately doesn't really make this easy as far as I can tell.
Reorg tests 04 | old-name | new-sub-dir | new-name | |-|-|-| | `issue-27997.rs` [issue](rust-lang#27997) | `codegen/` | `correctly-monomorphize-generic-drop-impl.rs` | | `issue-31299.rs` [issue](rust-lang#31299) | `associated-types/` | `sized-recursive-type-via-associated-type.rs` | | `issue-35815.rs` [issue](rust-lang#35815) | `codegen/` | `dont-roundup-dst-prefix-size-to-alignment.rs` | | `issue-46855.rs` [issue](rust-lang#46855) | `mir/` | `dont-use-operand-as-place-for-zst.rs` | | `issue-47486.rs` [issue](rust-lang#47486) | `consts/` | `size_of-requires-type-annotation-in-const.rs` | | `issue-47486.stderr` | `consts/` | `size_of-requires-type-annotation-in-const.stderr` | | `issue-50811.rs` [issue](rust-lang#50811) | `mir/` | `validate-various-comparison-behavior.rs` |
…r=GuillaumeGomez Add an example to the `NumBuffer` documentations We specifically call out that the sign is written for negative integers. This would also ideally be called out in `<iN>::format_into`, but the macro infrastructure for the implementation unfortunately doesn't really make this easy as far as I can tell. Ref rust-lang#138215
…t-rib, r=petrochenkov delegation: visit qself under elided-infer lifetime rib Follow-up for rust-lang#156705, we need to visit delegation's qself under elided-infer lifetime rib too. Fixes rust-lang#156758. Part of rust-lang#118212. r? @petrochenkov
|
@bors r+ rollup=never p=5 |
This comment has been minimized.
This comment has been minimized.
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
💔 Test for 1cf887f failed: CI. Failed job:
|
|
@bors retry |
This comment has been minimized.
This comment has been minimized.
|
📌 Perf builds for each rolled up PR:
previous master: 9128490ab3 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 9128490 (parent) -> b954122 (this PR) Test differencesShow 34 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 b954122bbe6c4a244c511a9a168c6d5438d8f58f --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 (b954122): 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 (secondary -1.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 2.1%, secondary -3.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: 517.203s -> 514.377s (-0.55%) |
Successful merges:
NumBufferdocumentations #156747 (Add an example to theNumBufferdocumentations)r? @ghost
Create a similar rollup