[roll] Roll infra/recipes [tree_closer] Ignore bisector builds when determining tree closures.

Bisector builds only help to bisect where failures started and shouldn't
actually close the tree, especially since they are triggered on older
commits so a newer commit may have actually passed so we wouldn't want
to close the tree because of a bisector build that failed later.

Original-Bug: 454334580
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1400517
Original-Revision: c1769e59c0c4c14852c5022b844e937281574dec
GitOrigin-RevId: 107d0afe551db4ed5dca4218ac6871e1735e9b1a
Change-Id: Iad750ea55ed8881772b01881519566f06e93b67d
1 file changed
tree: 0f35f4a2197680c51111b702040541d0b18746a2
  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.