| commit | 99725e144a9d2c4251d7f8e1a41851ba365c683f | [log] [tgz] |
|---|---|---|
| author | michajlo <michajlo@google.com> | Wed Nov 18 14:30:05 2020 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Nov 18 14:31:14 2020 -0800 |
| tree | 757650d0b3147f03a84183e59c07817ee19e5713 | |
| parent | 3e7acaf3f886709d960f508cfe4d2883098fb160 [diff] |
Wire correct interrupt handling from ActionExecutedEvent Generating command line arguments is an interruptible exercise. This might not be ideal, but it is what it is. Instead ignoring-ish the interrupt, declare it in all relevant places up the call stack. This is primarily signature changes, with the exception of FileTransport#asStreamProto which returns a null-valued future if the computation is interrupted. Looking at the documentation and code, this should be WAI. PiperOrigin-RevId: 343157405
{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
