Problem

I really like the upcoming -Zbuild-analysis feature. @weihanglo thank you so much for your work on this!

I‘m currently investigating the distribution of rebuilds and their root causes based on this new feature. For this use-case any context about a run that can be retrieved after the fact is super valuable.

Would it technically be possible to include the command that Cargo was invoked with (such as cargo nextest run or cargo run) as part of the logs?

Proposed Solution

Such information could be added as command field to LogMessage::BuildStarted.

Notes

No response