Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flag --incompatible_no_implicit_file_export will break Bazel Remote Cache in a future Bazel release #145

Closed
bazel-flag-bot opened this issue Dec 26, 2019 · 1 comment · Fixed by #158

Comments

@bazel-flag-bot
Copy link

Incompatible flag --incompatible_no_implicit_file_export will be enabled by default in a future Bazel release [1], thus breaking Bazel Remote Cache.

The flag is documented here: bazelbuild/bazel#10225

Please check the following CI builds for build and test results:

Never heard of incompatible flags before? We have documentation that explains everything.

If you don't want to receive any future issues for Bazel Remote Cache or if you have any questions,
please file an issue in https://github.com/bazelbuild/continuous-integration

Important: Please do NOT modify the issue title since that might break our tools.

[1] The target release hasn't been determined yet. Our tool will update the issue title once the flag flip has been scheduled.

@mostynb
Copy link
Collaborator

mostynb commented Dec 29, 2019

Waiting for bazelbuild/rules_go#2315

mostynb added a commit to mostynb/bazel-remote that referenced this issue Jan 10, 2020
mostynb added a commit that referenced this issue Jan 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants