Skip to content
This repository has been archived by the owner on Aug 30, 2022. It is now read-only.

Flag --incompatible_no_implicit_file_export will break Bazel integration testing in a future Bazel release #165

Closed
bazel-flag-bot opened this issue Dec 26, 2019 · 1 comment

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 integration testing.

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 integration testing 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.

@ittaiz
Copy link
Member

ittaiz commented Jan 17, 2020

closing since this is blocked by bazel moving forward

@ittaiz ittaiz closed this as completed Jan 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants