Return REMOTE_CACHE_EVICTED exit code on ThinLTO imports cache eviction. ThinLTO backend compilation reads `.imports` files during Skyframe input discovery prior to spawn execution. When remote cache eviction drops an imports file, `LtoBackendAction.computeImports` caught the cache miss as a generic `IMPORTS_READ_IO_EXCEPTION` (exit code 1). Because Bazel only triggers `--experimental_remote_cache_eviction_retries` when an action returns `REMOTE_CACHE_EVICTED` (exit code 39), builds fail permanently instead of retrying. In `LtoBackendAction.computeImports`, check if an `IOException` reading the imports file is a `CacheNotFoundException` or `BulkTransferException` cache miss. If so, return `Spawn.Code.REMOTE_CACHE_EVICTED` so that input discovery failures from evicted cache entries trigger build retries. Tested: Added `discoverInputs_cacheNotFoundException_throwsRemoteCacheEvictedCode` and `discoverInputs_bulkTransferException_throwsRemoteCacheEvictedCode` in `LtoBackendActionTest`. PiperOrigin-RevId: 971771054 Change-Id: I6c9b84c9a55d727cd930319178a946332df2d977
{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.
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
