[roll] Roll fuchsia [fint] Ignore graph/compdb failures if build failed

Previously if the main ninja invocation failed fatally (e.g. because an
unknown target was specified) then the `ninja graph` invocation would
also fail and camouflage the main ninja failure, e.g.
ci.chromium.org/b/b8832082838651060993. If the main ninja invocation
fails, we should ignore any errors from the ninja graph and compdb calls
to ensure that the proper error message gets propagated to the recipe.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/599782
Original-Revision: ff96101f9b3b84e40d40a78f7558a4b5d8b68402
GitOrigin-RevId: dac14c6bfe75eb54b8100a839148b26eadb71083
Change-Id: I8c392498f9ef8a6961ec4e2fdd834f960d1e68ce
1 file changed
tree: 76b92f1b79a270ebb51023f8931d2ed0206bbdeb
  1. infra/
  2. third_party/
  3. firmware
  4. flower
  5. jiri.lock
  6. minimal
  7. prebuilts
  8. README.md
  9. stem
  10. 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 via the IRC channel #fuchsia on Freenode.

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.