Option to include remote execution actions in chrome-trace
Open
enhancement
remote execution
UX
- Dominant language
- Rust
- Stars
- 4.4k
- Forks
- 394
- PR merge metrics
- No merged PRs in 30d
Description
Currently `buck2 debug chrome-trace` does not include actions that were executed via remote execution except for actions that are on the critical path.
Feature request: Add an option to enable the inclusion of all remote execution actions in the chrome-trace, not just those that were on the critical path.
Contributor guide
Assessment
This issue has not been assessed yet.