Print timestamp at the start of test execution. The intent is to simplify debugging of timeouts and pre-test latency: this way for timeouts there will be a clear measured interval between `Executing tests...` to `Test timed out at...` lines. One side-effect of this will be to guarantee all test logs are unique, rather than just the ones that contain a timestamped log entry or timeout. I don't expect this to be an issue, as the vast majority of logs should already be unique for some reason or another. RELNOTES: Print timestamp at the start of test execution logs. PiperOrigin-RevId: 549006113 Change-Id: Iae7441a60bd7f6cbca8e96369618a44f68273039
{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
