| commit | 80c7a4dd6048626616093ae7dc6baf8060c9e26f | [log] [tgz] |
|---|---|---|
| author | Carmen Chui <carmenchui@users.noreply.github.com> | Fri Jun 27 10:46:42 2025 -0400 |
| committer | GitHub <noreply@github.com> | Fri Jun 27 14:46:42 2025 +0000 |
| tree | 25c669f70e8eac8739ba402a10b7b4e449486196 | |
| parent | 066a162fb3a53c7a4e1355580de635182ae92216 [diff] |
Attempt to fix Bazel CI failure on Ubuntu (#26395) We started seeing cc_integration_test failures on Ubuntu only on Bazel CI. Example failed CI run: https://buildkite.com/bazel/google-bazel-presubmit/builds/92979 Failing test log (Ctrl+F `tsan`): https://storage.googleapis.com/bazel-untrusted-buildkite-artifacts/019784eb-e36a-476b-8268-eb41dd690353/src/test/shell/bazel/cc_integration_test/shard_4_of_10/test.log This CL fixes the failure, though I have no idea why this suddenly started happening earlier today (things I ruled out: Bazel code changes, docker container pushes, remote cache poisoning). PiperOrigin-RevId: 773497839 Change-Id: I2324a9668bfe28e24c222c12d6c82de60e7bd1df Co-authored-by: Googler <wyv@google.com>
{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
