Skip to content

Conversation

Mark-Simulacrum
Copy link
Member

@Mark-Simulacrum Mark-Simulacrum commented Sep 13, 2025

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-release Relevant to the release subteam, which will review and decide on the PR/issue. labels Sep 13, 2025
@Mark-Simulacrum
Copy link
Member Author

@bors r+ rollup=never p=1

@bors
Copy link
Collaborator

bors commented Sep 13, 2025

📌 Commit fd85120 has been approved by Mark-Simulacrum

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 Sep 13, 2025
@bors
Copy link
Collaborator

bors commented Sep 13, 2025

⌛ Testing commit fd85120 with merge 0e92880...

@rust-log-analyzer
Copy link
Collaborator

The job x86_64-msvc-ext1 failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)
   Verifying foo v0.0.1 (D:\a\rust\rust\build\x86_64-pc-windows-msvc\stage2-tools\x86_64-pc-windows-msvc\tmp\cit\t2383\foo)
 Downloading crates ...
  Downloaded bar v1.0.0 (registry `dummy-registry`)
   Compiling bar v1.0.0
   Compiling foo v0.0.1 (D:\a\rust\rust\build\x86_64-pc-windows-msvc\stage2-tools\x86_64-pc-windows-msvc\tmp\cit\t2383\foo\target\package\foo-0.0.1)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.60s

stack backtrace:
   0: __rustc::rust_begin_unwind
   1: core::panicking::panic_fmt

@bors
Copy link
Collaborator

bors commented Sep 13, 2025

💔 Test failed - checks-actions

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

thread 'package::reserved_windows_name' (1900) panicked at src\tools\cargo\

Hopefully spurious? @bors retry

@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 Sep 13, 2025
@bors
Copy link
Collaborator

bors commented Sep 14, 2025

⌛ Testing commit fd85120 with merge 60a5372...

@bors
Copy link
Collaborator

bors commented Sep 14, 2025

☀️ Test successful - checks-actions
Approved by: Mark-Simulacrum
Pushing 60a5372 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Sep 14, 2025
@bors bors merged commit 60a5372 into rust-lang:master Sep 14, 2025
11 checks passed
@rustbot rustbot added this to the 1.92.0 milestone Sep 14, 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 a015919 (parent) -> 60a5372 (this PR)

Test differences

Show 4 test diffs

Stage 2

  • [run-make] tests/run-make/compressed-debuginfo-zstd: pass -> ignore (ignored if LLVM wasn't build with zstd for ELF section compression (we want LLVM/LLD to be built with zstd support)) (J0)

Additionally, 3 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 60a5372753460ef0db67c2307308a741b17771f3 --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. x86_64-rust-for-linux: 2914.2s -> 3989.6s (36.9%)
  2. dist-apple-various: 3314.2s -> 4381.8s (32.2%)
  3. pr-check-1: 1574.8s -> 2055.1s (30.5%)
  4. pr-check-2: 2282.0s -> 2927.7s (28.3%)
  5. aarch64-apple: 5197.6s -> 6578.2s (26.6%)
  6. x86_64-gnu-miri: 4680.5s -> 5879.0s (25.6%)
  7. x86_64-gnu-tools: 3700.9s -> 4618.5s (24.8%)
  8. test-various: 4824.1s -> 5963.5s (23.6%)
  9. armhf-gnu: 4944.3s -> 5937.8s (20.1%)
  10. dist-aarch64-apple: 6012.3s -> 7182.1s (19.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
Collaborator

Finished benchmarking commit (60a5372): 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 (secondary 2.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)
2.9% [2.9%, 2.9%] 1
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) - - 0

Cycles

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

Binary size

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

Bootstrap: 475.072s -> 473.675s (-0.29%)
Artifact size: 390.15 MiB -> 390.15 MiB (0.00%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merged-by-bors This PR was explicitly merged by bors. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-release Relevant to the release subteam, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants