Skip to content

Update cargo submodule#155604

Merged
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
weihanglo:update-cargo
Apr 21, 2026
Merged

Update cargo submodule#155604
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
weihanglo:update-cargo

Conversation

@weihanglo

Copy link
Copy Markdown
Member

9 commits in 7ecf0285ebb408d596e4a8ac76a0980d8edb7005..06ac0e7c05770a8c7bbf67bdd12fa1a1eefdc8ae
2026-04-18 15:34:11 +0000 to 2026-04-21 15:33:56 +0000

r? ghost

@rustbot

rustbot commented Apr 21, 2026

Copy link
Copy Markdown
Collaborator

Some changes occurred in src/tools/cargo

cc @ehuss

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Apr 21, 2026
@rustbot

rustbot commented Apr 21, 2026

Copy link
Copy Markdown
Collaborator

⚠️ Warning ⚠️

@weihanglo

Copy link
Copy Markdown
Member Author

@bors r+ rollup=never p=1

@rust-bors

rust-bors Bot commented Apr 21, 2026

Copy link
Copy Markdown
Contributor

📌 Commit 14db8ba has been approved by weihanglo

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 Apr 21, 2026
@JonathanBrouwer

Copy link
Copy Markdown
Contributor

@bors p=6
Scheduling this before the next rollup

@rust-bors

This comment has been minimized.

@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 Apr 21, 2026
@rust-bors

rust-bors Bot commented Apr 21, 2026

Copy link
Copy Markdown
Contributor

☀️ Test successful - CI
Approved by: weihanglo
Duration: 3h 29m 11s
Pushing 9ec5d5f to main...

@rust-bors
rust-bors Bot merged commit 9ec5d5f into rust-lang:main Apr 21, 2026
12 checks passed
@rustbot rustbot added this to the 1.97.0 milestone Apr 21, 2026
@github-actions

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 d2f88d4 (parent) -> 9ec5d5f (this PR)

Test differences

Show 5 test diffs

Stage 2

  • help::help_man_temp_file_extension: [missing] -> pass (J0)
  • sources::git::utils::tests::github_fast_path_full_hash_returns_needs_fetch: [missing] -> pass (J0)
  • util::network::sleep::returns_in_order: pass -> [missing] (J0)

Additionally, 2 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 9ec5d5f32e19d250c7fbeaa90978c79105b39dee --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. dist-aarch64-linux: 1h 45m -> 2h 44m (+56.1%)
  2. dist-x86_64-msvc-alt: 2h 5m -> 2h 45m (+31.5%)
  3. x86_64-gnu-distcheck: 1h 46m -> 2h 12m (+24.7%)
  4. i686-msvc-1: 3h 2m -> 2h 18m (-24.1%)
  5. dist-ohos-x86_64: 1h 20m -> 1h 2m (-22.9%)
  6. x86_64-msvc-1: 1h 59m -> 2h 25m (+21.4%)
  7. dist-powerpc64le-linux-gnu: 1h 37m -> 1h 17m (-20.9%)
  8. dist-powerpc64-linux-gnu: 1h 35m -> 1h 16m (-20.0%)
  9. x86_64-gnu-llvm-22-1: 1h 4m -> 53m 22s (-17.2%)
  10. pr-check-2: 42m 53s -> 35m 45s (-16.6%)
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.

@weihanglo
weihanglo deleted the update-cargo branch April 21, 2026 23:39
@rust-timer

Copy link
Copy Markdown
Collaborator

Finished benchmarking commit (9ec5d5f): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

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

Max RSS (memory usage)

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

Cycles

Results (secondary 16.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)
18.9% [4.0%, 29.6%] 7
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-3.8% [-3.8%, -3.8%] 1
All ❌✅ (primary) - - 0

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.0% [0.0%, 0.0%] 1
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) - - 0

Bootstrap: 494.08s -> 489.594s (-0.91%)
Artifact size: 394.39 MiB -> 394.45 MiB (0.02%)

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants