| commit | e46f3d1cb5d6dedf9231921110264f40571b4781 | [log] [tgz] |
|---|---|---|
| author | Yun Peng <pcloudy@google.com> | Wed Feb 21 07:54:31 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Feb 21 07:56:24 2024 -0800 |
| tree | 8f80085f6250e9f9e9b025f4bae05e6bcbca9da7 | |
| parent | 4371c4b23de87116ee376f1e17479ebd997440e4 [diff] |
Improve test coverage on macOS - Add `--test_tag_filters=-no_macos` for macOS to filter out tests that are not suppose to run on Mac, just like the `no_windows` tag. - Fixed PatchApiBlackBoxTest and GitRepositoryBlackBoxTest on newer macOS versions. - Enable previously disabled tests on arm64 macOS platform in presubmit - Disable slow tests on Intel macOS platform in presubmit since they are often the bottleneck. Tests fixed: - Fixes https://github.com/bazelbuild/bazel/issues/16525 - Fixes https://github.com/bazelbuild/bazel/issues/17447 - Fixes https://github.com/bazelbuild/bazel/issues/17411 - Related: https://github.com/bazelbuild/bazel/issues/18776 (fixed on macos_arm64) Closes #21381. PiperOrigin-RevId: 608993052 Change-Id: I03bdf954c358bb736a866ce3a02f6dac4473e47e
{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
