| commit | bf0de1bb6ef32f064580e4d09ed1cd8931aac0fe | [log] [tgz] |
|---|---|---|
| author | Googler <hvd@google.com> | Thu Nov 23 00:54:53 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Nov 23 00:56:15 2023 -0800 |
| tree | f923c051a89cd2c3c3c0cf5362390313d164533e | |
| parent | 6d0716d465846a2954dceb49598aecd55ce7ed20 [diff] |
Automated rollback of commit 01f620599c6138de4b4551da92917148ab18efe3. *** Reason for rollback *** Fix jdeps_test RBE failure The culprit change added a new class that presumably pushed us over the xargs arg limit. Unfortunately, jdeps does not support @argfile, so this change updates the command buffer size to twice the default on RBE. Fixes https://github.com/bazelbuild/bazel/issues/20288 *** Original change description *** Disable //src/test/shell/bazel:jdeps_test on RBE build to fix presubmit Related https://github.com/bazelbuild/bazel/issues/20288 PiperOrigin-RevId: 584820138 Change-Id: I6f5157d7e72c539a5fdc81841a35543df473aa4a
{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
