Spawn execution log: add wall time duration The spawn execution log is useful to compare builds, for example to discover actions that were not cached, and to debug why they were not cached. This change adds the wall time of each spawn, which further allows finding actions that are are faster or slower between two builds. For example, when comparing local and remote builds, this helps discover differences in execution time, particularly if some actions are using persistent workers. Change-Id: Iacda7cd5b0265ec26d0a8fea82db2690582ed922 Closes #13195. Change-Id: I0ef3df9e84c403b88d14cb8cd149571d19874bd0 PiperOrigin-RevId: 388643261
{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:
See CONTRIBUTING.md
