| commit | de78989c54624c295450688518e7d8a52db7fea1 | [log] [tgz] |
|---|---|---|
| author | arostovtsev <arostovtsev@google.com> | Wed Nov 17 11:29:23 2021 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Nov 17 11:30:57 2021 -0800 |
| tree | de0afaa9f1e4644036a62f01e8c09141245b6990 | |
| parent | 3eeea3a616587822104402402ab4244824ad7456 [diff] |
Do not call handleLabelsCrossingSubpackagesAndPropagateInconsistentFilesystemExceptions if pkgBuilder.buildPartial() failed https://github.com/bazelbuild/bazel/commit/eb349967c8f11bad10db7fe2526bd3c60bca7ee7 changes pkgBuilder.getTargets() to return an unmodifiable set (specifically, the unmodifiable set returned by SnapshottableBiMap.values()) if pkgBuilder.buildPartial() has not yet been successfully called. handleLabelsCrossingSubpackagesAndPropagateInconsistentFilesystemExceptions requires pkgBuilder.buildPartial() to return a mutable set: it calls iterator.remove() on the iterator over the set. Thus, if pkgBuilder.buildPartial() throws, we must not call handleLabelsCrossingSubpackagesAndPropagateInconsistentFilesystemExceptions. PiperOrigin-RevId: 410583227
{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
