| commit | 01a3c768417e19dae8a2ff6a417c8b0472bc638b | [log] [tgz] |
|---|---|---|
| author | janakr <janakr@google.com> | Mon Mar 15 13:14:22 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Mar 15 13:16:02 2021 -0700 |
| tree | 9c11e5a2a21ee6c6aceaad487ee2054504dcc21a | |
| parent | a3353d22617e6bfb7b39ecbf25958b98368807c4 [diff] |
File bug reports when either (1) an IOException is thrown from InMemoryFileSystem operations, or (2) we try to resolve relative symlinks in a Fileset when the behavior is "ERROR". I don't believe that either of these things actually happens in real life, and I would like to remove IOException from these methods, since it propagates quite a ways up the hierarchy (to CompletionFunction, which claims that it can throw an IOException). PiperOrigin-RevId: 363013629
{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
