-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Open
Labels
A-timingsArea: timingsArea: timingsC-cleanupCategory: cleanup within the codebaseCategory: cleanup within the codebaseS-acceptedStatus: Issue or feature is accepted, and has a team member available to help mentor or reviewStatus: Issue or feature is accepted, and has a team member available to help mentor or reviewZ-build-analysisNightly: build-analysisNightly: build-analysis
Description
Problem
cargo report timings is going to supercede the pre-existing cargo build --timings flag. The two parallel implementations that haven't yet fully shared the metric collection logic between them.
Possible solutions
We'd like to remove the old logic of how --timings collect metrics, and instead push relevent LogMessages t an in-memory queue, and after the build, we reuse code in cargo report timings to replay and generate the HTML report.
This is currently blocked on #16420.
Metadata
Metadata
Assignees
Labels
A-timingsArea: timingsArea: timingsC-cleanupCategory: cleanup within the codebaseCategory: cleanup within the codebaseS-acceptedStatus: Issue or feature is accepted, and has a team member available to help mentor or reviewStatus: Issue or feature is accepted, and has a team member available to help mentor or reviewZ-build-analysisNightly: build-analysisNightly: build-analysis