Update cargo submodule

[weihanglo]

17 commits in 966f94733bbc94ca51ff9f1e4c49ad250ebbdc50..f2932725b045d361ff5f18ba02b1409dd1f44e71
2025-09-16 17:24:45 +0000 to 2025-09-24 11:31:26 +0000

• fix: use host-tuple for host target subsitution (fix: use host-tuple for host target subsitution cargo#16003)
• test(build-std): move away from panic_immediate_abort (test(build-std): move away from panic_immediate_abort  cargo#16006)
• fix: Sparse URLs in TomlLockfileSourceId (fix: Sparse URLs in TomlLockfileSourceId cargo#15990)
• refactor(gctx): extract toml dotted keys validation (refactor(gctx): extract toml dotted keys validation cargo#15998)
• feat: Add lint for global use of hint-mostly-unused (feat: Add lint for global use of hint-mostly-unused cargo#15995)
• Make GlobalContext Sync (Make GlobalContext Sync cargo#15967)
• chore(deps): update cargo-semver-checks to v0.44.0 (chore(deps): update cargo-semver-checks to v0.44.0 cargo#15993)
• fix(frontatter): Only allow horizontal whitespace after fences (fix(frontatter): Only allow horizontal whitespace after fences cargo#15975)
• docs: Add Lockfile schemas docs (docs: Add Lockfile schemas docs cargo#15989)
• Add parallel frontend to the build performance guide (Add parallel frontend to the build performance guide cargo#15970)
• chore(deps): update msrv (3 versions) to v1.88 (chore(deps): update msrv (3 versions) to v1.88 cargo#15988)
• chore(deps): update msrv (1 version) to v1.90 (chore(deps): update msrv (1 version) to v1.90 cargo#15984)
• feat(cargo-util-schemas): Move lockfile schemas (feat(cargo-util-schemas): Move lockfile schemas cargo#15980)
• Clarify multiple version requirement behavior (Clarify multiple version requirement behavior cargo#15979)
• Adds ghostty as supported terminal for term integration (OSC 9;4) (Adds ghostty as supported terminal for term integration (OSC 9;4) cargo#15977)
• docs(team): Fixed broken office hours link (docs(team): Fixed broken office hours link cargo#15976)
• docs: Clarify git sources vs git registries in source replacement documentation (docs: Clarify git sources vs git registries in source replacement documentation cargo#15974)

r? ghost

[rustbot]

Some changes occurred in src/tools/cargo

cc @ehuss

[rustbot]

⚠️ 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.

[weihanglo]

@bors r+ rollup=never p=1

[bors]

📌 Commit 6dafcaf has been approved by weihanglo

It is now in the queue for this repository.

[bors]

⌛ Testing commit 6dafcaf with merge 8c83722...

[bors]

💔 Test failed - checks-actions

[rust-log-analyzer]

A job failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)

   5 | >>> FROM centos:7
   6 |     
   7 |     WORKDIR /build
--------------------
ERROR: failed to build: failed to solve: centos:7: failed to resolve source metadata for docker.io/library/centos:7: unexpected status from HEAD request to https://registry-1.docker.io/v2/library/centos/manifests/7: 401 Unauthorized (did you mean centos?)
Command failed. Attempt 2/5:
#0 building with "sleepy_heyrovsky" instance using docker-container driver

#1 [internal] load build definition from Dockerfile
#1 transferring dockerfile: 3.05kB done
---
   5 | >>> FROM centos:7
   6 |     
   7 |     WORKDIR /build
--------------------
ERROR: failed to build: failed to solve: centos:7: failed to resolve source metadata for docker.io/library/centos:7: unexpected status from HEAD request to https://registry-1.docker.io/v2/library/centos/manifests/7: 401 Unauthorized (did you mean centos?)
Command failed. Attempt 3/5:
#0 building with "sleepy_heyrovsky" instance using docker-container driver

#1 [internal] load build definition from Dockerfile
#1 transferring dockerfile: 3.05kB done
---
   5 | >>> FROM centos:7
   6 |     
   7 |     WORKDIR /build
--------------------
ERROR: failed to build: failed to solve: centos:7: failed to resolve source metadata for docker.io/library/centos:7: unexpected status from HEAD request to https://registry-1.docker.io/v2/library/centos/manifests/7: 401 Unauthorized (did you mean centos?)
Command failed. Attempt 4/5:
#0 building with "sleepy_heyrovsky" instance using docker-container driver

#1 [internal] load build definition from Dockerfile
#1 transferring dockerfile: 3.05kB done
---
   5 | >>> FROM centos:7
   6 |     
   7 |     WORKDIR /build
--------------------
ERROR: failed to build: failed to solve: centos:7: failed to resolve source metadata for docker.io/library/centos:7: unexpected status from HEAD request to https://registry-1.docker.io/v2/library/centos/manifests/7: 401 Unauthorized (did you mean centos?)
Command failed. Attempt 5/5:
#0 building with "sleepy_heyrovsky" instance using docker-container driver

#1 [internal] load build definition from Dockerfile
#1 transferring dockerfile: 3.05kB done
---
   5 | >>> FROM centos:7
   6 |     
   7 |     WORKDIR /build
--------------------
ERROR: failed to build: failed to solve: centos:7: failed to resolve source metadata for docker.io/library/centos:7: unexpected status from HEAD request to https://registry-1.docker.io/v2/library/centos/manifests/7: 401 Unauthorized (did you mean centos?)
The command has failed after 5 attempts.
##[error]Process completed with exit code 1.
Post job cleanup.

[tgross35]

@bors treeclosed=100

Lots of spurious failures, see #t-infra > Failures from Ubuntu 401.

[tgross35]

For after things get fixed,
@bors retry

[tgross35]

Docker says it's back up, let's see
@bors p=101

[bors]

⌛ Testing commit 6dafcaf with merge 78ac912...

[rust-log-analyzer]

A job failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)

[bors]

💔 Test failed - checks-actions

[tgross35]

Still looks spurious but doesn't look like the same failure.
@bors retry

[bors]

⌛ Testing commit 6dafcaf with merge 8e33e36...

[bors]

💔 Test failed - checks-actions

[rust-log-analyzer]

A job failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)

[tgross35]

@bors retry

[bors]

⌛ Testing commit 6dafcaf with merge 9a002b1...

[bors]

💔 Test failed - checks-actions

[rust-log-analyzer]

A job failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)

[tgross35]

@bors retry

[bors]

⌛ Testing commit 6dafcaf with merge bbcbc78...

[tgross35]

@bors treeclosed- looks like it's going

[bors]

☀️ Test successful - checks-actions
Approved by: weihanglo
Pushing bbcbc78 to master...

[github-actions]

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 caccb4d (parent) -> bbcbc78 (this PR)

Test differences

Show 11 test diffs

Stage 2

• default_features_still_included_with_extra_build_std_features: [missing] -> ignore (requires nightly, CARGO_RUN_BUILD_STD_TESTS must be set) (J0)
• lints::blanket_hint_mostly_unused::named_profile_blanket: [missing] -> ignore (-Zhint-mostly-unused is unstable) (J0)
• lints::blanket_hint_mostly_unused::profile_build_override: [missing] -> ignore (-Zhint-mostly-unused is unstable) (J0)
• lints::blanket_hint_mostly_unused::profile_package_wildcard: [missing] -> ignore (-Zhint-mostly-unused is unstable) (J0)
• lints::blanket_hint_mostly_unused::workspace_profile_package_wildcard: [missing] -> ignore (-Zhint-mostly-unused is unstable) (J0)
• test_panic_abort: ignore (requires nightly, CARGO_RUN_BUILD_STD_TESTS must be set) -> [missing] (J0)
• util::context::tests::sync_context: [missing] -> pass (J0)

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

Job group index

• J0: aarch64-apple, aarch64-gnu, x86_64-gnu-aux, x86_64-msvc-ext1

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard bbcbc7818ba27c951f9fd881fd3ec4cd5123b741 --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: 6988.7s -> 5315.6s (-23.9%)
2. x86_64-gnu-llvm-20-1: 3217.9s -> 3568.0s (10.9%)
3. arm-android: 5735.9s -> 6341.5s (10.6%)
4. i686-gnu-2: 5500.4s -> 6034.6s (9.7%)
5. i686-gnu-nopt-1: 7553.6s -> 8244.1s (9.1%)
6. x86_64-gnu-debug: 6710.7s -> 7316.8s (9.0%)
7. tidy: 186.8s -> 170.1s (-8.9%)
8. x86_64-gnu-miri: 4308.6s -> 4685.2s (8.7%)
9. x86_64-msvc-ext1: 7810.1s -> 7167.3s (-8.2%)
10. i686-msvc-2: 8224.5s -> 7551.3s (-8.2%)

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]

Finished benchmarking commit (bbcbc78): 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.3%	[0.3%, 0.3%]	1
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

Results (primary 0.2%, secondary 0.6%)

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

	mean	range	count
Regressions ❌ (primary)	1.4%	[1.4%, 1.4%]	1
Regressions ❌ (secondary)	0.6%	[0.6%, 0.6%]	3
Improvements ✅ (primary)	-1.0%	[-1.0%, -1.0%]	1
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	0.2%	[-1.0%, 1.4%]	2

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: 472.505s -> 470.723s (-0.38%)
Artifact size: 387.91 MiB -> 388.07 MiB (0.04%)