| commit | 3d2bb2a400c48bc51e43db11ac154d999a97881b | [log] [tgz] |
|---|---|---|
| author | Sara Adams <sara@engflow.com> | Mon Oct 24 00:42:23 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Oct 24 00:43:25 2022 -0700 |
| tree | 2674fa9cb0f889a3345410d6b68cc62a88ca2a51 | |
| parent | 7190f228b7871c99f6e67291513619c74fbf4639 [diff] |
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
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
