bazelbuild / bazelbuild/rules_rust

--experimental_remote_require_cached results in errors

Open
#3,428 4 comments 0 reactions 0 assignees View on GitHub
needs-triage
Dominant language
Starlark
Stars
843
Forks
651
Avg merge
2d 18h
Merged PRs (30d)
15

Description

```
INFO: Analyzed 6 targets (346 packages loaded, 11718 targets configured).
ERROR: /private/var/tmp/_bazel_user/2fe8fca154ecc4fd4bfcc2428eaf334c/external/rules_rust++i+rules_rust_tinyjson/BUILD.bazel:4:37: Compiling Rust (without process_wrapper) rlib tinyjson (4 files) [for tool] failed: (Exit 1): Action must be cached due to --experimental_remote_require_cached but it is not
```

From the Bazel docs:

> [--[no]experimental_remote_require_cached](https://bazel.build/reference/command-line-reference#build-flag--experimental_remote_require_cached) default: "false"
> If set to true, enforce that all actions that can run remotely are cached, or else fail the build. This is useful to troubleshoot non-determinism issues as it allows checking whether actions that should be cached are actually cached without spuriously injecting new results into the cache.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.