Skip to content

Update cargo submodule#153067

Merged
rust-bors[bot] merged 1 commit intorust-lang:mainfrom
arlosi:update-cargo
Feb 26, 2026
Merged

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

Conversation

@arlosi
Copy link
Contributor

@arlosi arlosi commented Feb 25, 2026

8 commits in 8cc0cb136772b8f54eafe0d163fcb7226a06af0c..f298b8c82da0cba538516b45b04a480fc501d4c0 2026-02-17 12:16:26 +0000 to 2026-02-24 21:59:20 +0000

8 commits in 8cc0cb136772b8f54eafe0d163fcb7226a06af0c..f298b8c82da0cba538516b45b04a480fc501d4c0
2026-02-17 12:16:26 +0000 to 2026-02-24 21:59:20 +0000
- fix(host-config): fix panic when cross-compiling with host-config (rust-lang/cargo#16674)
- doc: improve documentation on using cfg values with build scripts (rust-lang/cargo#16671)
- Fix typo in cargo-yank docs (rust-lang/cargo#16656)
- fix(job_queue): Handle Clippy CLI arguments in `fix` message (rust-lang/cargo#16652)
- Add a test for fingerprint checking when a symlink target changes (rust-lang/cargo#16661)
- Fix parallel locking when `-Zfine-grain-locking` is enabled (rust-lang/cargo#16659)
- fix(cli): Remove `--lockfile-path` (rust-lang/cargo#16621)
- test(build-std): Update error message (rust-lang/cargo#16658)
@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 25, 2026
@rustbot
Copy link
Collaborator

rustbot commented Feb 25, 2026

Some changes occurred in src/tools/cargo

cc @ehuss

@rustbot
Copy link
Collaborator

rustbot commented Feb 25, 2026

r? @ehuss

rustbot has assigned @ehuss.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

  • Owners of files modified in this PR: @ehuss

@rustbot
Copy link
Collaborator

rustbot commented Feb 25, 2026

⚠️ Warning ⚠️

  • Some commits in this PR modify submodules.

    If this was not intentional, see I changed a submodule on accident in the rustc dev guide.

  • There are issue links (such as #123) in the commit messages of the following commits.
    Please move them to the PR description, to avoid spamming the issues with references to the commit, and so this bot can automatically canonicalize them to avoid issues with subtree.

@ehuss
Copy link
Contributor

ehuss commented Feb 25, 2026

@bors r+ rollup=never p=1

@rust-bors
Copy link
Contributor

rust-bors bot commented Feb 25, 2026

📌 Commit 8581df5 has been approved by ehuss

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 Feb 25, 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 Feb 26, 2026
@rust-bors
Copy link
Contributor

rust-bors bot commented Feb 26, 2026

☀️ Test successful - CI
Approved by: ehuss
Duration: 4h 16m 30s
Pushing 69b7853 to main...

@rust-bors rust-bors bot merged commit 69b7853 into rust-lang:main Feb 26, 2026
12 checks passed
@rustbot rustbot added this to the 1.95.0 milestone Feb 26, 2026
@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 f02672c (parent) -> 69b7853 (this PR)

Test differences

Show 21 test diffs

Stage 2

  • cross_compile::cross_with_host_config: [missing] -> pass (J0)
  • freshness::symlink_to_package: [missing] -> pass (J0)
  • lockfile_path::cli_add_lockfile_override: pass -> [missing] (J0)
  • lockfile_path::cli_assert_respect_pinned_version_from_lockfile_path: pass -> [missing] (J0)
  • lockfile_path::cli_basic_lockfile_created: pass -> [missing] (J0)
  • lockfile_path::cli_basic_lockfile_override: pass -> [missing] (J0)
  • lockfile_path::cli_basic_lockfile_read: pass -> [missing] (J0)
  • lockfile_path::cli_broken_symlink: pass -> [missing] (J0)
  • lockfile_path::cli_clean_lockfile_override: pass -> [missing] (J0)
  • lockfile_path::cli_fix_lockfile_override: pass -> [missing] (J0)
  • lockfile_path::cli_ignored_when_config_set: pass -> [missing] (J0)
  • lockfile_path::cli_install_lock_file_path_must_present: pass -> [missing] (J0)
  • lockfile_path::cli_install_respects_lock_file_path: pass -> [missing] (J0)
  • lockfile_path::cli_loop_symlink: pass -> [missing] (J0)
  • lockfile_path::cli_must_be_nightly: pass -> [missing] (J0)
  • lockfile_path::cli_must_have_unstable_options: pass -> [missing] (J0)
  • lockfile_path::cli_publish_lockfile_read: pass -> [missing] (J0)
  • lockfile_path::cli_remove_lockfile_override: pass -> [missing] (J0)
  • lockfile_path::cli_run_embed: ignore (-Zscript is unstable) -> [missing] (J0)
  • lockfile_path::cli_symlink_in_path: pass -> [missing] (J0)
  • lockfile_path::cli_symlink_lockfile: pass -> [missing] (J0)

Job group index

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 69b78537fac74de40f009b076bcbbf54b77683ad --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. aarch64-apple: 3h 13m -> 4h 9m (+28.5%)
  2. dist-aarch64-apple: 2h 15m -> 1h 42m (-24.4%)
  3. pr-check-1: 34m 29s -> 26m 56s (-21.9%)
  4. dist-apple-various: 1h 43m -> 2h 4m (+20.9%)
  5. i686-gnu-2: 1h 42m -> 1h 25m (-16.8%)
  6. dist-x86_64-apple: 2h 27m -> 2h 3m (-16.3%)
  7. dist-aarch64-llvm-mingw: 1h 52m -> 1h 35m (-14.4%)
  8. x86_64-gnu-tools: 1h 3m -> 55m 43s (-12.4%)
  9. test-various: 2h 7m -> 1h 53m (-11.2%)
  10. x86_64-rust-for-linux: 51m 42s -> 46m 8s (-10.8%)
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 (69b7853): 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)

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

Cycles

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

Binary size

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

Bootstrap: 479.407s -> 480.132s (0.15%)
Artifact size: 395.80 MiB -> 395.80 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants