Skip to content

Conversation

matthiaskrgr
Copy link
Member

Successful merges:

Failed merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

tiif and others added 30 commits February 26, 2025 12:47
before_terminator: add some minor clarifying comments
Add an anchor to directly link to the -Zmiri-tree-borrows docs
It was added to all preludes in Rust 1.80.
Use `size_of` from the prelude instead of imported
Show interpreter backtrace error on Ctrl+C
xizheyin and others added 13 commits March 28, 2025 22:28
Signed-off-by: xizheyin <xizheyin@smail.nju.edu.cn>
Explain one-past-the-end pointer in std library

Closing rust-lang#138969

r? libs
Put pin!() tests in the right file.

In rust-lang#138717, these tests were put in `tests/pin.rs`, but they should go in `tests/pin_macro.rs`.

r? `@jdonszelmann`
Fix formatting nit in process.rs

Minor formatting issue in `process.rs`.
…i-obk

Fix TAIT & ATPIT feature gating in the presence of anon consts

Fixes rust-lang#139055 (rust-lang#119924 (comment)).

r? oli-obk or anybody else
`io::Take`: avoid new `BorrowedBuf` creation in some case

If `self.limit == buf.capacity()`, doing the whole `BorrowedBuf` dance is not necessary.
…compiler-errors

Do not treat lifetimes from parent items as influencing child items

```rust
struct A;
impl Bar<'static> for A {
    const STATIC: &str = "";
    //            ^ no future incompat warning
}
```

has no future incompat warning, because there is no ambiguity. But

```rust
struct C;
impl Bar<'_> for C {
//       ^^ this lifeimte
    const STATIC: &'static str = {
        struct B;
        impl Bar<'static> for B {
            const STATIC: &str = "";
            // causes     ^ to emit a future incompat warning
        }
        ""
    };
}
```

had one before this PR, because the impl for `B` (which is just a copy of `A`) thought it was influenced by a lifetime on the impl for `C`.

I double checked all other `lifetime_ribs` iterations and all of them do check for `Item` boundaries. This feels very fragile tho, and ~~I think we should do not even be able to see ribs from parent items, but that's a different refactoring that I'd rather not do at the same time as a bugfix~~. EDIT: ah nevermind, this is needed for improving diagnostics like "use of undeclared lifetime" being "can't use generic parameters from outer item" instead.

r? `@compiler-errors`
…atrieb

tracking autodiff files via triagebot.toml

r? `@oli-obk`

Tracking:

- rust-lang#124509
@rustbot rustbot added A-meta Area: Issues & PRs about the rust-lang/rust repository itself S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. rollup A PR which is a rollup labels Mar 28, 2025
@matthiaskrgr
Copy link
Member Author

@bors r+ rollup=never p=5

@bors
Copy link
Collaborator

bors commented Mar 28, 2025

📌 Commit 20f2655 has been approved by matthiaskrgr

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 28, 2025
@bors
Copy link
Collaborator

bors commented Mar 28, 2025

⌛ Testing commit 20f2655 with merge 920d95e...

@bors
Copy link
Collaborator

bors commented Mar 29, 2025

☀️ Test successful - checks-actions
Approved by: matthiaskrgr
Pushing 920d95e to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Mar 29, 2025
@bors bors merged commit 920d95e into rust-lang:master Mar 29, 2025
7 checks passed
@rustbot rustbot added this to the 1.87.0 milestone Mar 29, 2025
Copy link
Contributor

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 19f42cb (parent) -> 920d95e (this PR)

Test differences

Show 90 test diffs

Stage 0

  • pin_macro::rust_2024_expr: [missing] -> pass (J2)

Stage 1

  • pin::temp_lifetime: pass -> [missing] (J0)
  • pin_macro::rust_2024_expr: [missing] -> pass (J0)
  • pin_macro::temp_lifetime: [missing] -> pass (J0)
  • [ui] tests/ui/impl-trait/inside-item-nested-in-anon-const.rs: [missing] -> pass (J1)

Stage 2

  • [ui] tests/ui/impl-trait/inside-item-nested-in-anon-const.rs: [missing] -> pass (J3)

Additionally, 84 doctest diffs were found. These are ignored, as they are noisy.

Job group index

  • J0: aarch64-apple, aarch64-gnu, arm-android, armhf-gnu, dist-i586-gnu-i586-i686-musl, i686-gnu-1, i686-gnu-nopt-1, i686-msvc-1, test-various, x86_64-apple-1, x86_64-gnu, x86_64-gnu-aux, x86_64-gnu-llvm-18-1, x86_64-gnu-llvm-18-2, x86_64-gnu-llvm-18-3, x86_64-gnu-llvm-19-1, x86_64-gnu-llvm-19-2, x86_64-gnu-llvm-19-3, x86_64-gnu-nopt, x86_64-gnu-stable, x86_64-mingw-1, x86_64-msvc-1
  • J1: x86_64-gnu-llvm-18-3, x86_64-gnu-llvm-19-3
  • J2: mingw-check
  • J3: aarch64-apple, aarch64-gnu, arm-android, armhf-gnu, dist-i586-gnu-i586-i686-musl, i686-gnu-1, i686-gnu-nopt-1, i686-msvc-1, test-various, x86_64-apple-2, x86_64-gnu, x86_64-gnu-llvm-18-1, x86_64-gnu-llvm-18-2, x86_64-gnu-llvm-19-1, x86_64-gnu-llvm-19-2, x86_64-gnu-nopt, x86_64-gnu-stable, x86_64-mingw-1, x86_64-msvc-1

Job duration changes

  1. aarch64-gnu: 6626.5s -> 10079.5s (52.1%)
  2. dist-i686-mingw: 8142.5s -> 8721.8s (7.1%)
  3. dist-powerpc64le-linux: 9345.8s -> 9978.0s (6.8%)
  4. dist-armhf-linux: 4967.8s -> 5292.1s (6.5%)
  5. aarch64-gnu-debug: 6011.6s -> 6265.6s (4.2%)
  6. aarch64-apple: 3846.6s -> 4007.5s (4.2%)
  7. dist-x86_64-linux: 5350.5s -> 5512.9s (3.0%)
  8. x86_64-msvc-ext2: 5672.6s -> 5833.0s (2.8%)
  9. dist-x86_64-illumos: 5634.7s -> 5776.4s (2.5%)
  10. i686-mingw-1: 7289.0s -> 7453.0s (2.3%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#138976 Explain one-past-the-end pointer in std library bd924e56052a5a6e8518bcb001f054d36eb23cad (link)
#139052 Put pin!() tests in the right file. a1eacbe372c4655f4f9a315b1a871d73f1f68d17 (link)
#139058 Fix formatting nit in process.rs cd893470e289ef17907a853061ee7b01a0b8b8c4 (link)
#139063 Fix TAIT & ATPIT feature gating in the presence of anon con… 5203144204430321894cabbc4f439486a33e8e2e (link)
#139065 Miri subtree update 27f15454a243d5c2a081f88d03398b46cb90763b (link)
#139069 io::Take: avoid new BorrowedBuf creation in some case 54c32509cdee258b8a89053d2115f4f3548a8c1f (link)
#139075 Do not treat lifetimes from parent items as influencing chi… a464c3aa0ccbd68533d11d8a1827220dd5f1471e (link)
#139079 tracking autodiff files via triagebot.toml 98fa4a14e609ddf19e0cd2c9a898eaeac378709e (link)

previous master: 19f42cb9bb

In the case of a perf regression, run the following command for each PR you suspect might be the cause: @rust-timer build $SHA

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (920d95e): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

Results (primary -2.3%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-2.3% [-2.3%, -2.3%] 1
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) -2.3% [-2.3%, -2.3%] 1

Cycles

Results (secondary -3.0%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-3.0% [-4.0%, -2.1%] 12
All ❌✅ (primary) - - 0

Binary size

Results (primary 0.0%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

mean range count
Regressions ❌
(primary)
0.0% [0.0%, 0.0%] 1
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 0.0% [0.0%, 0.0%] 1

Bootstrap: 778.47s -> 777.624s (-0.11%)
Artifact size: 365.96 MiB -> 365.96 MiB (0.00%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-meta Area: Issues & PRs about the rust-lang/rust repository itself merged-by-bors This PR was explicitly merged by bors. rollup A PR which is a rollup S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.