| commit | d72a4cd6d7981b4b33e43f0af7aaec01351d5cb0 | [log] [tgz] |
|---|---|---|
| author | michajlo <michajlo@google.com> | Wed Oct 13 09:26:36 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Oct 13 09:27:53 2021 -0700 |
| tree | 9b9c594c5e857faecad83a89e0a7332df29a1138 | |
| parent | b9ab84178477602df86c90a2f129b110e4431436 [diff] |
Fake out infrastructure to support (some) cpp-isms in the loading phase The issue is BazelMockCcSupport (and likely others) don't currently support the isRealFileSystem=true case. Fake out what is necessary to get by for the time being while we figure out how to make isRealFileSystem mode work or something else altogether. We can't unconditionally stage the files because the isRealFileSystem=false case is used by BuildViewTestCase and seems to mostly work. We don't just fake isRealFileSystem=false all the time because that needs a little more investigation and I'd like to get something in to unblock efforts to open source more tests, which this should do for ones touching just the loading phase. Verified that this gets some QueryIntegrationTest methods that were failing due to missing cpp business to pass. PiperOrigin-RevId: 402851221
{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
