Skip to content

Update cargo submodule#153823

Merged
rust-bors[bot] merged 1 commit intorust-lang:mainfrom
weihanglo:update-cargo
Mar 13, 2026
Merged

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

Conversation

@weihanglo
Copy link
Member

@weihanglo weihanglo commented Mar 13, 2026

21 commits in 90ed291a50efc459e0c380d7b455777ed41c6799..cbb9bb8bd0fb272b1be0d63a010701ecb3d1d6d3
2026-03-05 15:11:25 +0000 to 2026-03-13 14:34:16 +0000

@rustbot
Copy link
Collaborator

rustbot commented Mar 13, 2026

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 Mar 13, 2026
@rustbot
Copy link
Collaborator

rustbot commented Mar 13, 2026

⚠️ Warning ⚠️

@weihanglo
Copy link
Member Author

@bors r+ rollup=never p=1

@rust-bors
Copy link
Contributor

rust-bors bot commented Mar 13, 2026

📋 This PR cannot be approved because it has merge conflicts. Please resolve the conflicts and try again.

@rustbot
Copy link
Collaborator

rustbot commented Mar 13, 2026

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

@weihanglo
Copy link
Member Author

@bors r+ rollup=never p=1

@rust-bors
Copy link
Contributor

rust-bors bot commented Mar 13, 2026

📌 Commit 83c0242 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 Mar 13, 2026
@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 Mar 13, 2026
@rust-bors
Copy link
Contributor

rust-bors bot commented Mar 13, 2026

☀️ Test successful - CI
Approved by: weihanglo
Duration: 3h 8m 27s
Pushing f1ceedf to main...

@rust-bors rust-bors bot merged commit f1ceedf into rust-lang:main Mar 13, 2026
12 checks passed
@rustbot rustbot added this to the 1.96.0 milestone Mar 13, 2026
@weihanglo weihanglo deleted the update-cargo branch March 13, 2026 20:05
@github-actions
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 0e4bafc (parent) -> f1ceedf (this PR)

Test differences

Show 7 test diffs

Stage 2

  • build_std_does_not_warn_about_implicit_std_deps: [missing] -> ignore (requires nightly, CARGO_RUN_BUILD_STD_TESTS must be set) (J0)
  • git::dep_with_scp_like_submodule_url: [missing] -> pass (J0)
  • package::repackage_smaller_crate_has_trailing_garbage: [missing] -> pass (J0)
  • package::repackage_smaller_local_dep_tmp_registry_checksum_match: [missing] -> pass (J0)
  • warning_override::keep_going: [missing] -> pass (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 f1ceedfd34d0cc9fbfe13f6d8a63944a21694e76 --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-x86_64-apple: 1h 39m -> 2h 8m (+29.1%)
  2. pr-check-1: 35m 13s -> 27m 33s (-21.8%)
  3. pr-check-2: 44m 57s -> 37m 52s (-15.8%)
  4. dist-aarch64-msvc: 1h 31m -> 1h 46m (+15.3%)
  5. aarch64-gnu-debug: 1h 14m -> 1h 3m (-14.0%)
  6. dist-apple-various: 1h 38m -> 1h 24m (-13.8%)
  7. x86_64-rust-for-linux: 53m 5s -> 45m 58s (-13.4%)
  8. dist-aarch64-llvm-mingw: 1h 41m -> 1h 53m (+10.8%)
  9. i686-gnu-nopt-1: 2h 22m -> 2h 7m (-10.5%)
  10. aarch64-gnu-llvm-21-1: 59m 21s -> 53m 9s (-10.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 (f1ceedf): comparison URL.

Overall result: ❌ regressions - no action needed

@rustbot label: -perf-regression

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

Max RSS (memory usage)

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

Cycles

Results (primary 2.4%, secondary -0.3%)

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

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

Binary size

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

Bootstrap: 481.956s -> 478.63s (-0.69%)
Artifact size: 396.74 MiB -> 394.82 MiB (-0.49%)

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.

warning: feature frontmatter is declared but not used

3 participants