tree 9ec5efd882ab48f06914a64069a590f65f12e3d9
parent 8e0285d15b0414e3434e52119a73ec100a3db6ad
author jmmv <jmmv@google.com> 1555963482 -0700
committer Copybara-Service <copybara-worker@google.com> 1555963549 -0700

Ensure grep-includes can write to its output file by deleting it upfront.

The include scanner deletes existing output files before running
grep-includes, but only did so for outputs that were generated when
scanning the includes of files from the source tree -- not for source
files generated during the build.  Make this happen now in all cases.

The cleanup is necessary in all cases because, when grep-includes runs
remotely, we download its output into a file and set its permissions to
555. If we happen to run this same action locally at a later time, the
local run may not be able to overwrite the local file and we fail the
build.

This should fix random build failures during include scanning observed
when using the dynamic scheduler without local sandboxing in Google-internal
builds.

Addresses https://github.com/bazelbuild/bazel/issues/7818.

RELNOTES: None.
PiperOrigin-RevId: 244718195