commit | ce4cf60eff9f59db1035f22c9bcb555d64f84a29 | [log] [tgz] |
---|---|---|
author | nharmata <nharmata@google.com> | Wed Nov 13 10:44:24 2019 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Nov 13 10:45:18 2019 -0800 |
tree | f1572d2e7c35f682b8a522e53508df2800b0582b | |
parent | 9b324d249e100f60849ecc34c6c91a34d3dbc5d5 [diff] |
Refactor test_glob_with_io_error so we get test coverage in both --keep_going and --nokeep_going mode. Also, since that integration test is exercising usage of FileAccessException, add an explicit unit test for that in FileFunctionTest. Also, while I'm here, remove an unused ctor of FileAccessException and also add a hand-written Codec for FileAccessException. See the class javadoc for the motivation of the latter. RELNOTES: None PiperOrigin-RevId: 280230717
{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