[roll] Roll fuchsia [bazel] bazel_action.py: Remove genquery build and output files

To get rid of a surprising consistency flake, remove the auto-generated
genquery build file and its output file after running the main
`bazel build` command.

This removes a source of flakes on our consistency builders (example at [1]),
that only happens when Ninja decides to schedule two bazel_action()
commands in a different order between two consecutive clean builds.

This flake was very likely the reason for the revert in [2], and it
is hoped here that this will allow re-landing [3] properly.

[1]: https://ci.chromium.org/ui/p/turquoise/builders/global.ci/core.x64-asan-bazel_consistency/b8698204306356068097/overview
[2]: https://fuchsia-review.googlesource.com/c/fuchsia/+/1423316
[3]: https://fuchsia-review.googlesource.com/c/fuchsia/+/1399534

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1427674
Original-Revision: ea292b346f793df9b5d8659376539d3b9632de0c
GitOrigin-RevId: a11ef07c9d8c34d55e6af1b9935203d8567dc1bf
Change-Id: I96e7d79d794b3c7fdb754906b5889cea798e8a83
1 file changed
tree: 7bea4de6f1232fcd0776934e49fa5aadea28ccd2
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.