| commit | d8e13c8e1641c8127765994f15444844785dc8d4 | [log] [tgz] |
|---|---|---|
| author | Googler <lberki@google.com> | Tue Apr 11 00:07:32 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Apr 11 00:08:41 2023 -0700 |
| tree | bc988ed94fd29fde5944374d3ec8a03a22c29b86 | |
| parent | f3e066e78d40d46f53a49087b8de45bfbcce2581 [diff] |
Split MetadataProvider.getMetadata() into two methods. One for getting metadata for the inputs of the action and one for its outputs. The principal difference between the two is that when the action starts executing, the metadata for its inputs should be known, so no expensive I/O should be needed. This would in principle allow one to not throw IOException there. It remains for two reasons: * Some conditions are signaled by throwing FileNotFoundException (I haven't investigated very deeply) * Some implementations still do I/O for reasons unknown At the very least, this will allow one to not throw InterruptedException in getInputMetadata(). Work towards fixing #17009. RELNOTES: None. PiperOrigin-RevId: 523318267 Change-Id: Ib3af4c099a0faafb9a8b6d75d04928af47bfbcd1
{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
