Do not emit test timeout and size warnings for cached tests. When `--test_verbose_timeout_warnings` is enabled, Bazel checks whether a passing test's execution time is within the expected range for its specified timeout and size (e.g., `MODERATE` or `LONG`). However, when a test is cached locally or remotely, its recorded `test_process_times` duration reflects only the short cache lookup or download time (e.g. ~200ms) rather than the actual test execution duration. Fixes https://github.com/bazelbuild/bazel/issues/13103 PiperOrigin-RevId: 971400182 Change-Id: Iaad15d051c399676999d30269cb1657e04dd869b
{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.
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
