| commit | 52a44d428cba4840ccba74356a2948126a4fde4b | [log] [tgz] |
|---|---|---|
| author | Googler <plf@google.com> | Wed Nov 13 04:14:53 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Nov 13 04:16:13 2024 -0800 |
| tree | 19356b84722c144d551251fac99969bad6c85cff | |
| parent | 04e362e7dc3051498c827b0d13eb2e9dafabe500 [diff] |
Automated rollback of commit 471aca124968977ecf1920711811c37ce19c1aa7. *** Reason for rollback *** Breaks sharded linking, see [] I had tried with the :interpreter target unknown commit, but the failure didn't appear there anymore and I assumed it was gone. It does appear with ML experiments. Command line is: bin/bash ./learning/gemini/prod/scripts/xm_run.sh learning/gemini/prod/stable/gemini:xm_launch -- --xm_resource_alloc=cml/cml-shared-ml-user --xm_job_name=gemax-prod-gemini-experiment --model=v2:gemini_debug --launch_mode=train_and_eval_split It requires access to Gemini *** Original change description *** Remove implicit _stl attribute from C++ rules. PiperOrigin-RevId: 696073900 Change-Id: I9871d22bbbd6b7ecd74aadd8df4e3b301ba55c8c
{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
