-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Closed
Labels
C-bugCategory: bugCategory: bugS-triageStatus: This issue is waiting on initial triage.Status: This issue is waiting on initial triage.regression-from-stable-to-betaRegression in beta that previously worked in stable.Regression in beta that previously worked in stable.
Description
Problem
cargo build --timings
has stopped having a full set of dependency lines in the graph.
Before:

After:

(Both screenshots taken while hovering on num-traits
.)
Steps
- Pick any large project, say https://github.com/gfx-rs/wgpu.git
- Run
cargo +nightly-2025-09-11 clean -p libm && cargo +nightly-2025-09-11 build -p wgpu --lib --timings
twice (to produce a reproducible and reasonably small graph) - Do the same for nightly-2025-09-12.
- Observe that the latter timings graph is missing some lines the former has.
Possible Solution(s)
Based on the presence of a legend in the latter only, this is probably caused by #15923. cc @Kobzol
Notes
@rustbot label +regression-from-stable-to-nightly
Version
This is the first nightly version that demonstrates the problem:
cargo 1.91.0-nightly (24bb93c38 2025-09-10)
release: 1.91.0-nightly
commit-hash: 24bb93c388fb8c211a37986539f24a819dc669d3
commit-date: 2025-09-10
host: aarch64-apple-darwin
libgit2: 1.9.1 (sys:0.20.2 vendored)
libcurl: 8.7.1 (sys:0.4.83+curl-8.15.0 system ssl:(SecureTransport) LibreSSL/3.3.6)
ssl: OpenSSL 3.5.2 5 Aug 2025
os: Mac OS 15.6.1 [64-bit]
Metadata
Metadata
Assignees
Labels
C-bugCategory: bugCategory: bugS-triageStatus: This issue is waiting on initial triage.Status: This issue is waiting on initial triage.regression-from-stable-to-betaRegression in beta that previously worked in stable.Regression in beta that previously worked in stable.