| commit | de4da646601f7ea457c35d2ecd08a68ba5f19f2e | [log] [tgz] |
|---|---|---|
| author | Benjamin Peterson <benjamin@engflow.com> | Thu Oct 28 03:45:46 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Oct 28 03:46:51 2021 -0700 |
| tree | ebc65c34416d57cea8659f5348503df17fc79242 | |
| parent | e74fbfd31a4f10e639c8a22fc89822f4f2eef157 [diff] |
Remove test_remote_https_cache. This test claimed to "Test that if 'https' is provided as a scheme for --remote_cache flag, remote cache works." However, it does not establish that. Failing to read or write to the remote cache simply prints a warning, which does not fail this test. The HTTPS remote cache cannot work due to at least the following reasons: 1. The remote worker in this test file does not have the HTTP cache enabled. 2. The test remote worker does not support HTTPS over its HTTP cache. 3. Even if the test remote worker did support HTTPS, the HTTP remote cache client does not read --tls_certificate from the command line. Closes #14133. PiperOrigin-RevId: 406101943
{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
