| commit | 36fa60b1805faa7da2c4b5330b4b186740f5f00d | [log] [tgz] |
|---|---|---|
| author | Googler <michajlo@google.com> | Mon Jan 22 17:58:16 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jan 22 18:00:02 2024 -0800 |
| tree | 1253ff59197e264a9e2a7306481e0e33c3ff6d17 | |
| parent | cfd4e5478887e8dcc84c542e8310cbac0c28aa24 [diff] |
Compute pretty paths using symlink-creation results instead of disk state This makes pretty-path printing compatible with --experimental_convenience_symlinks=log_only, where we'd like to pretend the symlinks exist and still log relative to them, but not actually create them. Turns out that instead of inferring symlink state from disk we can pretty easily pass what we know from symlink creation along to pretty-printing. This also establishes a happens-before relationship in the code, so the whole "only call this at the right time" concern should be gone. There is a risk that the on-disk state could be out of sync with what we think it should be, but I'm having a hard time thinking of how that would be desired... PiperOrigin-RevId: 600623440 Change-Id: I9afc9aa7b2e45f911682bde3ce7d20d72a1d9dde
{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
