Skip to content

Rollup of 9 pull requests - #165698

Merged
rust-bors[bot] merged 39 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-SGvTy8O
Nov 9, 2026
Merged

rust-bors[bot] merged 39 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-SGvTy8O

Conversation

@JonathanBrouwer

Copy link
Copy Markdown
Member

Successful merges:

r? @ghost

Create a similar rollup

GuillaumeGomez and others added 30 commits October 16, 2026 14:29
`addr_of` sounds too much like the `addr_of!` macro or any other operation using raw pointers. It's also consistent with `ty_ref` and `expr_array_ref`.
This matches the order in which it is actually written in code.
This allows removing some clones and simplifies the code since it only needs to work with up to two selflike arguments, which is all we need.
This removes several clones and works since each method def only gets expanded once. It also requires inlining `create_derived_impl` to avoid borrow checking errors.
Some platforms like UEFI do not support real sub-processes. Hoever, it
is possible to launch a program from another. Thus, while
Command::spawn is not possible on UEFI, APIs which wait for the
result, (such as Command::output) are fine.

Similar to what was done for Command::output in past, make
Command::status impl platform specific, i.e. move it into
sys/process/mod.rs.

Signed-off-by: Ayush Singh <ayush@beagleboard.org>
Use a custom implementation for Command::status for UEFI, that does
not rely on Command::spawn. While I am only writing one for UEFI,
judging by the implementation of output just above this, other
platforms might also add their own in the future.

Signed-off-by: Ayush Singh <ayush@beagleboard.org>
```
error: the constant `N` is not of type `usize`
  --> $DIR/bad-subst-const-kind.rs:8:31
   |
LL | impl<const N: u64> Q for [u8; N] {
   |      ------------             ^ array length expected `usize`, found `u64`
   |      |
   |      `N` defined here
   |
   = note: the length of array `[u8; N]` must be type `usize`
```

When evaluating an array type's length we don't have accurate spans for that hir node, because evaluation happens on types. Keep the Span for the whole array type that we can use later to try and find the hir node and extract the right span to use in the diagnostic.
…e-in-helper-thread, r=petrochenkov

Make `Proxy` weak reference as it seems that it is not dropped at all

Split from rust-lang#165506 which makes `Proxy` droppable, which locally fixes the issue:
```rust
thread 'jobserver::jobserver_and_j' (126990) panicked at src/tools/cargo/tests/testsuite/jobserver.rs:411:10:

---- expected: tests/testsuite/jobserver.rs:405:27
++++ actual:   stderr
   1    1 | [WARNING] a `-j` argument was passed to Cargo but Cargo is also configured with an external jobserver in its environment, ignoring the `-j` parameter
   2    2 | [COMPILING] foo v0.0.1 ([ROOT]/foo)
   3    3 | [FINISHED] `dev` profile [unoptimized + debuginfo] target(s) in [ELAPSED]s
        4 + make[1]: INTERNAL: Exiting with 1 jobserver tokens available; should be 2!
```

(see rust-lang#162848 (comment)).

r? @petrochenkov
Add regression test for unsafe diagnostic attributes

Adds a regression test for this issue: rust-lang#165692
I'm refactoring some things and would like to make sure I don't accidentally change the behaviour here

cc @mejrs
@rust-bors rust-bors Bot added the rollup A PR which is a rollup label Nov 9, 2026
@rustbot rustbot added A-attributes Area: Attributes (`#[…]`, `#![…]`) A-process Area: `std::process` (note: `std::env` is A-env) 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. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. T-rustdoc-frontend Relevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output. labels Nov 9, 2026
@JonathanBrouwer

Copy link
Copy Markdown
Member Author

@bors r+ p=5 force

Trying commonly failed jobs
@bors try jobs=dist-various-1,test-various,test-x86_64-gnu-aux,test-x86_64-msvc-1,test-aarch64-apple-1,test-aarch64-apple-2,test-x86_64-mingw-1,test-i686-msvc,test-armhf-gnu,test-x86_64-gnu-llvm-22-3,test-aarch64-msvc-2

@rust-bors

rust-bors Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

📌 Commit 26453bc has been approved by JonathanBrouwer

It is now in the queue for this repository.

@rust-bors rust-bors Bot 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 Nov 9, 2026
@rust-bors

This comment has been minimized.

rust-bors Bot pushed a commit that referenced this pull request Nov 9, 2026
Rollup of 9 pull requests


try-job: dist-various-1
try-job: test-various
try-job: test-x86_64-gnu-aux
try-job: test-x86_64-msvc-1
try-job: test-aarch64-apple-1
try-job: test-aarch64-apple-2
try-job: test-x86_64-mingw-1
try-job: test-i686-msvc
try-job: test-armhf-gnu
try-job: test-x86_64-gnu-llvm-22-3
try-job: test-aarch64-msvc-2
@rust-bors

This comment has been minimized.

@rust-bors

rust-bors Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

☀️ Try build successful (CI)
Build commit: fae3790 (fae37905f4b5622ad956ef7c2840dcedce69cffc)
Base parent: 495625e (495625e3cba369dad96c4d1e8030e8fe1816ab2c)

@rust-bors rust-bors Bot added merged-by-bors This PR was explicitly merged by bors. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Nov 9, 2026
@rust-bors

rust-bors Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

☀️ Test successful - CI
Approved by: JonathanBrouwer
Duration: 3h 10m 22s
Pushing 7f56606 to main...

@rust-bors
rust-bors Bot merged commit 7f56606 into rust-lang:main Nov 9, 2026
16 checks passed
@rustbot rustbot added this to the 1.102.0 milestone Nov 9, 2026
@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
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 fefe61b (parent) -> 7f56606 (this PR)

Test differences

Show 195 test diffs

Stage 1

  • [rustdoc-html] tests/rustdoc-html/deref-to-alias.rs: [missing] -> pass (J1)
  • [rustdoc-html] tests/rustdoc-html/deref/deref-methods-aliased-type.rs: [missing] -> pass (J1)
  • [rustdoc-html] tests/rustdoc-html/deref/deref-on-aliased.rs: [missing] -> pass (J1)
  • [rustdoc-html] tests/rustdoc-html/deref/not-mut-deref.rs: [missing] -> pass (J1)
  • [rustdoc-html] tests/rustdoc-html/notable-trait/type-alias-generic-arg.rs: [missing] -> pass (J1)
  • [ui (polonius)] tests/ui/attributes/key-value-nested-attr-crate-name.rs#normal: [missing] -> pass (J2)
  • [ui (polonius)] tests/ui/attributes/key-value-nested-attr-crate-name.rs#print: [missing] -> pass (J2)
  • [ui (polonius)] tests/ui/attributes/key-value-nested-attr-crate-type.rs#normal: [missing] -> pass (J2)
  • [ui (polonius)] tests/ui/attributes/key-value-nested-attr-crate-type.rs#print: [missing] -> pass (J2)
  • [ui (polonius)] tests/ui/attributes/key-value-nested-attr-fail.rs: [missing] -> pass (J2)
  • [ui (polonius)] tests/ui/attributes/key-value-nested-attr-pass.rs: [missing] -> pass (J2)
  • [ui (polonius)] tests/ui/attributes/key-value-nested-attr-recursion-limit.rs: [missing] -> pass (J2)
  • [ui (polonius)] tests/ui/diagnostic_namespace/unsafe_attr.rs: [missing] -> pass (J2)
  • [ui (polonius)] tests/ui/implied-bounds/implied-bounds-cyclic-hang-issue-118449.rs: [missing] -> pass (J2)
  • [ui] tests/ui/attributes/key-value-nested-attr-crate-name.rs#normal: [missing] -> pass (J4)
  • [ui] tests/ui/attributes/key-value-nested-attr-crate-name.rs#print: [missing] -> pass (J4)
  • [ui] tests/ui/attributes/key-value-nested-attr-crate-type.rs#normal: [missing] -> pass (J4)
  • [ui] tests/ui/attributes/key-value-nested-attr-crate-type.rs#print: [missing] -> pass (J4)
  • [ui] tests/ui/attributes/key-value-nested-attr-fail.rs: [missing] -> pass (J4)
  • [ui] tests/ui/attributes/key-value-nested-attr-pass.rs: [missing] -> pass (J4)
  • [ui] tests/ui/attributes/key-value-nested-attr-recursion-limit.rs: [missing] -> pass (J4)
  • [ui] tests/ui/diagnostic_namespace/unsafe_attr.rs: [missing] -> pass (J4)
  • [ui] tests/ui/implied-bounds/implied-bounds-cyclic-hang-issue-118449.rs: [missing] -> pass (J4)
  • clean::types::tests::is_same_generic: pass -> [missing] (J5)

Stage 2

  • [rustdoc-html] tests/rustdoc-html/deref-to-alias.rs: [missing] -> pass (J0)
  • [rustdoc-html] tests/rustdoc-html/deref/deref-methods-aliased-type.rs: [missing] -> pass (J0)
  • [rustdoc-html] tests/rustdoc-html/deref/deref-on-aliased.rs: [missing] -> pass (J0)
  • [rustdoc-html] tests/rustdoc-html/deref/not-mut-deref.rs: [missing] -> pass (J0)
  • [rustdoc-html] tests/rustdoc-html/notable-trait/type-alias-generic-arg.rs: [missing] -> pass (J0)
  • [ui] tests/ui/attributes/key-value-nested-attr-crate-name.rs#normal: [missing] -> pass (J3)
  • [ui] tests/ui/attributes/key-value-nested-attr-crate-name.rs#print: [missing] -> pass (J3)
  • [ui] tests/ui/attributes/key-value-nested-attr-crate-type.rs#normal: [missing] -> pass (J3)
  • [ui] tests/ui/attributes/key-value-nested-attr-crate-type.rs#print: [missing] -> pass (J3)
  • [ui] tests/ui/attributes/key-value-nested-attr-fail.rs: [missing] -> pass (J3)
  • [ui] tests/ui/attributes/key-value-nested-attr-pass.rs: [missing] -> pass (J3)
  • [ui] tests/ui/attributes/key-value-nested-attr-recursion-limit.rs: [missing] -> pass (J3)
  • [ui] tests/ui/diagnostic_namespace/unsafe_attr.rs: [missing] -> pass (J3)
  • [ui] tests/ui/implied-bounds/implied-bounds-cyclic-hang-issue-118449.rs: [missing] -> pass (J3)

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

Job group index

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 7f56606f4dd7194a437f3bf2199ab1bd2fd94677 --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. test-i686-gnu-nopt-2: 1h 23m -> 2h 32m (+82.6%)
  2. test-x86_64-gnu-stdlib-semver-check: 10m 13s -> 16m 41s (+63.3%)
  3. dist-powerpc64-linux-musl: 1h 5m -> 1h 40m (+53.8%)
  4. test-x86_64-rust-for-linux: 39m 14s -> 59m 17s (+51.1%)
  5. dist-ohos-armv7: 53m 24s -> 1h 17m (+45.8%)
  6. dist-powerpc64le-linux-musl: 1h 9m -> 1h 41m (+45.6%)
  7. dist-riscv64-linux-musl: 1h -> 1h 27m (+44.6%)
  8. test-x86_64-msvc-ext3: 1h 56m -> 1h 4m (-44.3%)
  9. dist-powerpc64le-linux-gnu: 1h 10m -> 1h 40m (+43.5%)
  10. dist-various-2: 36m 24s -> 51m 53s (+42.5%)
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
Copy Markdown
Collaborator

Finished benchmarking commit (7f56606): comparison URL.

Overall result: ❌✅ regressions and improvements - please read:

Our benchmarks found a performance regression caused by this PR.
This might be an actual regression, but it can also be just noise.

Next Steps:

  • If the regression was expected or you think it can be justified,
    please write a comment with sufficient written justification, and add
    @rustbot label: +perf-regression-triaged to it, to mark the regression as triaged.
  • If you think that you know of a way to resolve the regression, try to create
    a new PR with a fix for the regression.
  • If you do not understand the regression or you think that it is just noise,
    you can ask the @rust-lang/wg-compiler-performance working group for help (members of this group
    were already notified of this PR).

@rustbot label: +perf-regression
cc @rust-lang/wg-compiler-performance

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

mean range count
Regressions ❌
(primary)
1.4% [0.2%, 5.9%] 9
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-1.1% [-3.1%, -0.2%] 25
Improvements ✅
(secondary)
-0.4% [-1.7%, -0.1%] 28
All ❌✅ (primary) -0.4% [-3.1%, 5.9%] 34

Max RSS (memory usage)

Results (primary -5.5%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

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

Cycles

Results (primary -0.3%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
3.6% [3.6%, 3.6%] 1
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-1.6% [-1.8%, -1.2%] 3
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) -0.3% [-1.8%, 3.6%] 4

Binary size

Results (primary -0.0%, secondary -0.0%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

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

Bootstrap: 483.426s -> 483.422s (-0.00%)
Artifact size: 406.20 MiB -> 406.22 MiB (0.01%)

@rustbot rustbot added the perf-regression Performance regression. label Nov 9, 2026
@rust-bors

rust-bors Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#165161 rustc_builtin_macros cleanup, part 9 f91f1a6db568fd9e9f2bfc69f344eba48f6435f2
(link)
#165663 Avoid repeated gated spans snapshots during macro matching 713ca2a7751f287b4a6a65bc09486df2e5c07719
(link)
#165637 library: std: process: Make Command::status platform specif… 65d675c6e40e213b3c055ba2b17102476e6aa056
(link)
#163571 [rustdoc] Render Deref methods on aliased items 55d4d536c7affe668cf7c841b69639a26fc3c00f
(link)
#164712 Reject unexpanded attributes in attributes 170ed8a7ee458e8f6f5c5b13d98c294676e215db
(link)
#165516 Point at array length instead of whole array type f9c53bcd7ebadba781410b1eb6e9ea0f579c4859
(link)
#165674 Add regression test for issue 118449 643f183a45b1265da332322806c56029ae0a1ab5
(link)
#165676 Make Proxy weak reference as it seems that it is not drop… 6e04bb3e0776d629a02f5f36f7b26e48f7de7265
(link)
#165695 Add regression test for unsafe diagnostic attributes 62fbf0e3483f25bc0ea504f74989893b2b0ca245
(link)

parent commit: fefe61bee0

In the case of a perf regression, run the following command with the SHAs of each PR you suspect might be the cause: @rust-timer triage $SHA $SHA $SHA..., or run @rust-timer triage all to benchmark all rollup members.

@JonathanBrouwer

Copy link
Copy Markdown
Member Author

@rust-timer triage all

@rust-timer

rust-timer commented Nov 9, 2026 •

Copy link
Copy Markdown
Collaborator
Running triage with 15 benchmarks

Triage only executes the benchmarks on rollup members, that were changed significantly on the rollup.
For this rollup, these benchmarks are:

  • clap_derive-4.5.32
  • clap_derive-4.5.32-nll
  • deref-sidebar-stress
  • derive
  • enum-stress
  • html5ever-0.31.0
  • html5ever-0.31.0-new-solver
  • image-0.25.6
  • issue-58319
  • libc-0.2.172
  • nalgebra-0.33.0
  • serde_derive-1.0.219
  • tt-muncher
  • typenum-1.18.0
  • wg-grammar

#165161 f91f1a6 rustc_builtin_macros cleanup, part 9

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

mean range count
Regressions ❌
(primary)
0.3% [0.2%, 0.3%] 4
Regressions ❌
(secondary)
0.0% [0.0%, 0.0%] 1
Improvements ✅
(primary)
-0.2% [-0.2%, -0.2%] 3
Improvements ✅
(secondary)
-0.3% [-0.4%, -0.1%] 8
All ❌✅ (primary) 0.1% [-0.2%, 0.3%] 7

Max RSS (memory usage)

Results (primary -5.4%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

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

Cycles

Results (secondary -2.4%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

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

Binary size

This perf run didn't have relevant results for this metric.


#165663 713ca2a Avoid repeated gated spans snapshots during macro matching

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-1.2% [-3.1%, -0.2%] 23
Improvements ✅
(secondary)
-0.4% [-1.4%, -0.1%] 19
All ❌✅ (primary) -1.2% [-3.1%, -0.2%] 23

Max RSS (memory usage)

Results (primary -3.6%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

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

Cycles

Results (primary -0.2%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
3.2% [2.3%, 4.0%] 2
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-1.8% [-2.0%, -1.5%] 4
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) -0.2% [-2.0%, 4.0%] 6

Binary size

This perf run didn't have relevant results for this metric.


#165637 65d675c library: std: process: Make Command::status platform specific

This perf run didn't have relevant results for the `instruction count` metric.

Instruction count

This perf run didn't have relevant results for this metric.

Max RSS (memory usage)

Results (primary -4.1%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

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

Cycles

Results (primary 3.3%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

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

Binary size

Results (secondary -0.0%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

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

#163571 55d4d53 [rustdoc] Render Deref methods on aliased items

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

mean range count
Regressions ❌
(primary)
2.6% [0.7%, 6.0%] 5
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-1.7% [-1.7%, -1.7%] 1
All ❌✅ (primary) 2.6% [0.7%, 6.0%] 5

Max RSS (memory usage)

Results (primary -3.9%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

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

Cycles

Results (primary 3.9%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

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

Binary size

This perf run didn't have relevant results for this metric.


#164712 170ed8a Reject unexpanded attributes in attributes

This perf run didn't have relevant results for the `instruction count` metric.

Instruction count

This perf run didn't have relevant results for this metric.

Max RSS (memory usage)

Results (primary -5.5%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

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

Cycles

This perf run didn't have relevant results for this metric.

Binary size

This perf run didn't have relevant results for this metric.


#165516 f9c53bc Point at array length instead of whole array type

This perf run didn't have relevant results for the `instruction count` metric.

Instruction count

This perf run didn't have relevant results for this metric.

Max RSS (memory usage)

Results (primary -5.1%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

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

Cycles

This perf run didn't have relevant results for this metric.

Binary size

This perf run didn't have relevant results for this metric.


#165674 643f183 Add regression test for issue 118449

This perf run didn't have relevant results for the `instruction count` metric.

Instruction count

This perf run didn't have relevant results for this metric.

Max RSS (memory usage)

Results (primary -5.4%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

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

Cycles

This perf run didn't have relevant results for this metric.

Binary size

This perf run didn't have relevant results for this metric.


#165676 6e04bb3 Make Proxy weak reference as it seems that it is not dropped at all

This perf run didn't have relevant results for the `instruction count` metric.

Instruction count

This perf run didn't have relevant results for this metric.

Max RSS (memory usage)

Results (primary -5.7%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

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

Cycles

This perf run didn't have relevant results for this metric.

Binary size

This perf run didn't have relevant results for this metric.


#165695 62fbf0e Add regression test for unsafe diagnostic attributes

This perf run didn't have relevant results for the `instruction count` metric.

Instruction count

This perf run didn't have relevant results for this metric.

Max RSS (memory usage)

Results (primary -3.7%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

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

Cycles

This perf run didn't have relevant results for this metric.

Binary size

This perf run didn't have relevant results for this metric.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-attributes Area: Attributes (`#[…]`, `#![…]`) A-process Area: `std::process` (note: `std::env` is A-env) merged-by-bors This PR was explicitly merged by bors. perf-regression Performance regression. rollup A PR which is a rollup 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. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. T-rustdoc-frontend Relevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output.

Projects

None yet

Development

Successfully merging this pull request may close these issues.