You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
buck2: Allow passing --trace-id to buck2 debug chrome-trace
Summary: I've been analyzing chrome-traces from builds that don't always generate them; it'd be nice to allow passing a `--trace-id` to this command so that buck2 downloads it for me rather than me having to materialize it first and pass the path.
Reviewed By: JakobDegen
Differential Revision: D75388796
fbshipit-source-id: 6e7807a710af9d7c7d2429c1a2ba40a234878d9e
help = "Where to write the chrome trace JSON. If a directory is passed, the filename of the event log will be used as a base filename."
47
50
)]
48
51
pubtrace_path:PathArg,
52
+
49
53
/// The path to read the event log from.
50
54
#[clap(
51
55
long,
52
56
help = "A path to an event-log file to read from. Only works for log files with a single command in them. If no event-log is passed, the most recent one will be used.",
53
-
group = "event_log",
54
-
value_name = "PATH"
57
+
value_name = "PATH",
58
+
// Hide because `event_log` below subsumes this.
59
+
hide = true
55
60
)]
56
61
pubpath:Option<PathArg>,
57
62
58
-
/// Which recent command to read the event log from.
59
-
#[clap(
60
-
long,
61
-
help = "Use the event-log from the Nth most recent command (`--recent 0` is the most recent).",
0 commit comments