| commit | d5b4c1b1ec9773f441cf50764b476fc26a9b0842 | [log] [tgz] |
|---|---|---|
| author | Googler <larsrc@google.com> | Mon Mar 06 07:32:57 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Mar 06 07:34:26 2023 -0800 |
| tree | 6d0552dbc70cc7219637dba736e11b09162e97c8 | |
| parent | 38ece3c04105698fc84daa89ba30c5fa692e0403 [diff] |
Set runners for critical path where no spawn was actually executed. Not entirely sure that this does the right thing in all circumstances. Is it possible that an actual spawn runner's update could happen after the call to `finishActionExecution`? What happens around action rewinding? Could we do something about the fileset and symlinking actions that only come through `actionComplete`? That even happens for all actions, so it should not be considered for "non-runner name". Should the runners that are not "real" runners be indicated in some way, in brackets or something? PiperOrigin-RevId: 514405743 Change-Id: I0323f930a0e3ee475fd07d39c375edcfc542fc96
{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
