Skip to content

Update cargo submodule - #161273

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

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

Conversation

@weihanglo

@weihanglo weihanglo commented Aug 18, 2026

Copy link
Copy Markdown
Member

View all comments

6 commits in 8a0d8afba810304bcf9a10bac430be80dd470233..514c56dd7321eecbfdcf9b6479519cf4edfab906
2026-08-15 01:32:53 +0000 to 2026-08-19 00:31:04 +0000

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

rustbot commented Aug 18, 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 Aug 18, 2026

Copy link
Copy Markdown
Contributor

📌 Commit 144981e 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 Aug 18, 2026
@Kobzol

Kobzol commented Aug 18, 2026

Copy link
Copy Markdown
Member

@bors try jobs=dist-x86_64-linux @rust-timer queue

@rust-timer

This comment has been minimized.

@rust-bors

This comment has been minimized.

@rustbot rustbot added the S-waiting-on-perf Status: Waiting on a perf run to be completed. label Aug 18, 2026
rust-bors Bot pushed a commit that referenced this pull request Aug 18, 2026
Update cargo submodule


try-job: dist-x86_64-linux
@rust-bors

rust-bors Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

☀️ Try build successful (CI)
Build commit: 2b31d55 (2b31d55819fbe2688d6819b19544d15c46e81b52)
Base parent: 444dcce (444dcce484c66c8d626806a8556be3b4d3ef381a)

@rust-timer

This comment has been minimized.

@rust-timer

Copy link
Copy Markdown
Collaborator

Finished benchmarking commit (2b31d55): comparison URL.

Overall result: ❌✅ regressions and improvements - no action needed

Benchmarking means the PR may be perf-sensitive. Consider adding rollup=never if this change is not fit for rolling up.

@rustbot label: -S-waiting-on-perf -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)
1.2% [0.8%, 1.7%] 4
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-0.7% [-0.7%, -0.7%] 2
All ❌✅ (primary) - - 0

Max RSS (memory usage)

Results (primary -1.5%, secondary -8.4%)

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)
-1.5% [-1.5%, -1.5%] 1
Improvements ✅
(secondary)
-8.4% [-11.5%, -2.8%] 8
All ❌✅ (primary) -1.5% [-1.5%, -1.5%] 1

Cycles

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

Binary size

Results (primary -58.4%, secondary -39.8%)

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)
-58.4% [-100.0%, -0.0%] 142
Improvements ✅
(secondary)
-39.8% [-100.0%, -0.1%] 197
All ❌✅ (primary) -58.4% [-100.0%, -0.0%] 142

Bootstrap: 455.347s -> 457.651s (0.51%)
Artifact size: 398.98 MiB -> 398.95 MiB (-0.01%)

@rustbot rustbot removed the S-waiting-on-perf Status: Waiting on a perf run to be completed. label Aug 18, 2026
@rust-bors

This comment has been minimized.

rust-bors Bot pushed a commit that referenced this pull request Aug 18, 2026
Update cargo submodule

3 commits in 8a0d8afba810304bcf9a10bac430be80dd470233..36e1162a7989dd1d11b75bfa90283efcbf162cac
2026-08-15 01:32:53 +0000 to 2026-08-18 02:35:44 +0000
- Re-stabilize build-dir layout v2 (rust-lang/cargo#17354)
- Enable `-Zembed-metadata=no` by default on nightly Cargo (rust-lang/cargo#17267)
- fix(frontmatter): Don't panic on a short closing fence before a non-ASCII char (rust-lang/cargo#17274)

r? ghost
@Kobzol

Kobzol commented Aug 18, 2026

Copy link
Copy Markdown
Member
image

Well, you don't see such (binary size) wins often.. :) I suppose that we should start tracking the .rmeta size too, because after this change, the .rlibs might be quite "empty" for some crates.

@rust-log-analyzer

This comment has been minimized.

@rust-bors rust-bors Bot 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 Aug 18, 2026
@rust-bors

rust-bors Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

💔 Test for 4acb4d7 failed: CI. Failed job:

@Kobzol

Kobzol commented Aug 18, 2026

Copy link
Copy Markdown
Member

Hmm, I guess we'll have to add a special env. var to opt out of opting into -Zembed-metadata=no in bootstrap when running Cargo's tests?

@weihanglo

Copy link
Copy Markdown
Member Author

Hmm, I guess we'll have to add a special env. var to opt out of opting into -Zembed-metadata=no in bootstrap when running Cargo's tests?

We probably just need to be more lenient on those snapshots. I am back now and will fix it.

pull Bot pushed a commit to linyihai/cargo that referenced this pull request Aug 19, 2026
### What does this PR try to resolve?

I've considered change

https://github.com/rust-lang/cargo/blob/19112f96270d68fc834ce94bccf789c463078312/src/compiler/build_context/target_info.rs#L353-L356

to

```rust
let cargo_nightly = matches!(
    crate::version().release_channel.as_deref(),
    Some("nightly" | "dev") | None
);
```

As non release channel means you are developing cargo.

Considering it may affect libcargo users, I gave up.
(I am biased as I am a libcargo consumer at work)
Let me know which you think the best.

### How to test and review this PR?

To reproduce this rust-lang/rust failure:
<https://triage.rust-lang.org/gha-logs/rust-lang/rust/95781922166>,

you can run

```
CFG_RELEASE_CHANNEL=nightly cargo +nightly test
```

See
rust-lang/rust#161273 (comment)

**LLM disclosure**: I told LLM to simulate Cargo CI and test against it,
plus rust-lang/rust CI.
@rust-bors rust-bors Bot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Aug 19, 2026
@rustbot

rustbot commented Aug 19, 2026

Copy link
Copy Markdown
Collaborator

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
Copy Markdown
Member Author

@bors try jobs=x86_64-gnu-aux

@rust-bors

This comment has been minimized.

rust-bors Bot pushed a commit that referenced this pull request Aug 19, 2026
Update cargo submodule


try-job: x86_64-gnu-aux
@weihanglo

Copy link
Copy Markdown
Member Author

@bors r+ rollup=never p=1

@rust-bors

rust-bors Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

📌 Commit 352e9f1 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-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Aug 19, 2026
@rust-bors

rust-bors Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

☀️ Try build successful (CI)
Build commit: a764521 (a764521bb589aabdc83250c6e901b02ae8bb2ead)
Base parent: e71c0f1 (e71c0f1e3395b10a8c331317be1a5c107bdf7b2e)

@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 Aug 19, 2026
@rust-bors

rust-bors Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

☀️ Test successful - CI
Approved by: weihanglo
Duration: 3h 1m 50s
Pushing 407371f to main...

@rust-bors
rust-bors Bot merged commit 407371f into rust-lang:main Aug 19, 2026
15 checks passed
@rustbot rustbot added this to the 1.100.0 milestone Aug 19, 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 9ba81c2 (parent) -> 407371f (this PR)

Test differences

Show 10 test diffs

Stage 2

  • build_dir::build_script_should_output_to_build_dir: [missing] -> pass (J0)
  • rustdoc::rustdoc_json_with_new_layout: ignore (--output-format is unstable) -> [missing] (J0)
  • util::frontmatter::test::split_fewer_dashes: [missing] -> pass (J0)
  • util::frontmatter::test::split_fewer_dashes_before_non_ascii: [missing] -> pass (J0)
  • util::frontmatter::test::split_fewer_dashes_by_one: [missing] -> pass (J0)

Additionally, 5 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 407371fb751c935c0380baf9965beca6ae6174e7 --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-msvc-ext1: 1h 27m -> 2h 26m (+66.9%)
  2. x86_64-gnu-stdlib-semver-check: 19m 55s -> 10m 35s (-46.9%)
  3. i686-msvc-1: 3h 6m -> 1h 43m (-44.3%)
  4. x86_64-msvc-2: 2h 35m -> 1h 28m (-43.3%)
  5. x86_64-gnu-llvm-22-1: 54m 14s -> 1h 14m (+37.1%)
  6. i686-gnu-1: 1h 31m -> 2h 5m (+36.4%)
  7. dist-apple-various: 2h 56m -> 1h 57m (-33.6%)
  8. x86_64-gnu-gcc-core-tests: 17m 58s -> 12m 13s (-32.0%)
  9. dist-ohos-aarch64: 1h -> 1h 19m (+32.0%)
  10. x86_64-gnu-llvm-22-3: 1h 51m -> 1h 16m (-31.4%)
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.

@Kobzol

Kobzol commented Aug 19, 2026

Copy link
Copy Markdown
Member

Ok, good, thank you! So starting from the 2026-08-20 nightly (or will it be named 2026-08-19? I always get this wrong), we should have -Zembed-metadata=no used by default.

@rust-timer

Copy link
Copy Markdown
Collaborator

Finished benchmarking commit (407371f): comparison URL.

Overall result: ❌✅ regressions and improvements - 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)
1.2% [0.8%, 1.7%] 4
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-0.7% [-0.7%, -0.7%] 2
All ❌✅ (primary) - - 0

Max RSS (memory usage)

Results (primary -1.0%, secondary -8.4%)

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)
-1.0% [-1.0%, -1.0%] 1
Improvements ✅
(secondary)
-8.4% [-11.4%, -2.9%] 8
All ❌✅ (primary) -1.0% [-1.0%, -1.0%] 1

Cycles

Results (secondary -4.8%)

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

Binary size

Results (primary -65.8%, secondary -66.4%)

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)
-65.8% [-100.0%, -2.7%] 126
Improvements ✅
(secondary)
-66.4% [-100.0%, -1.1%] 118
All ❌✅ (primary) -65.8% [-100.0%, -2.7%] 126

Bootstrap: 455.183s -> 458.213s (0.67%)
Artifact size: 398.99 MiB -> 399.03 MiB (0.01%)

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.

5 participants