tree 2674fa9cb0f889a3345410d6b68cc62a88ca2a51
parent 7190f228b7871c99f6e67291513619c74fbf4639
author Sara Adams <sara@engflow.com> 1666597343 -0700
committer Copybara-Service <copybara-worker@google.com> 1666597405 -0700

Bazel profile: improve reporting of critical path components

The Bazel profile reports the critical path. To enable it to be stored in a separate thread, the `tid` is set to 0 throughout. However, this makes it hard to match critical path events to events in the skyframe-evaluator threads.

This change adds the `tid` of the event in the `args` of the `critical path component` event. Like this, the critical path components continue to be listed in the critical path thread, as well as allowing the unique identification of which actual event in the evaluator threads it corresponds to.

Closes #16523.

PiperOrigin-RevId: 483297689
Change-Id: I68cbcf2caa80d98292709ae1358c4ba45489a38c