Flag --incompatible_no_implicit_file_export will break Flogger in a future Bazel release

[bazel-flag-bot]

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

The flag is documented here: bazelbuild/bazel#10225

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

• Ubuntu 16.04, OpenJDK 8

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

If you don't want to receive any future issues for Flogger 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.

[cpovirk]

(20:22:43) ERROR: /var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/11e901125f13327934febaa92e1e92f1/external/bazel_tools/tools/test/CoverageOutputGenerator/java/com/google/devtools/coverageoutputgenerator/BUILD:4:1: in java_import rule @bazel_tools//tools/test/CoverageOutputGenerator/java/com/google/devtools/coverageoutputgenerator:all_lcov_merger_lib: target '@remote_coverage_tools//:all_lcov_merger_tools_deploy.jar' is not visible from target '@bazel_tools//tools/test/CoverageOutputGenerator/java/com/google/devtools/coverageoutputgenerator:all_lcov_merger_lib'. Check the visibility declaration of the former target if you think the dependency is legitimate

It sounds like there is a chance that this is a problem in Bazel itself, though it's not completely clear to me: bazelbuild/continuous-integration#887 (There's also some discussion on bazelbuild/bazel#10225 and bazelbuild/continuous-integration#891)

I'm going to optimistically close this bug, but I'll subscribe to those 3 bugs in case there are updates.