[roll] Roll fuchsia [fint] Collect build perf data even if ninja fails

For consistency with recipes:
https://fuchsia.googlesource.com/infra/recipes/+/HEAD/recipe_modules/build/api.py#1100

I should probably eventually add unit tests to ensure that we do always
do this analysis even if ninja fails, but for now the logic is pretty
easy to inspect.

Original-Bug: 67861
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/512800
Original-Revision: 387d7aa90b235522e37670068ef0c915fca4a4a0
GitOrigin-RevId: 17e9eeb84456b02475370978c7b1898b955efa95
Change-Id: I09eabf1b7136b83b153bebc88f79859b440f3760
1 file changed
tree: ea75c8007fa30e72e94e6b93474393cc70957542
  1. garnet/
  2. infra/
  3. peridot/
  4. third_party/
  5. topaz/
  6. zircon/
  7. firmware
  8. flower
  9. jiri.lock
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. 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.