[roll] Roll infra/recipes [build] Inline _fint_build function

It's only ever called by the `_build()` function, and now that
`_build()` only ever runs `fint build`, never ninja, having the
fint-specific logic in a separate function doesn't make the code
significantly more readable. If anything, it makes it *less* readable
because there are two different functions where error handling can
occur, which is confusing and no longer necessary.

Expectation file diffs are a result of moving the `with goma_context()`
block to only wrap the `fint build` call rather than all of the logic
that used to be in the `_fint_build()` function. This helps avoid
excessive code indentation and makes it clear that goma only needs to be
enabled when running `fint build`. In particular, we now read the fint
build artifacts *after* shutting down goma rather than before shutting
down goma.

Original-Bug: 67861
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/516321
Original-Revision: 0fa8be8c419e347b8335e8188eea20c9888f1451
GitOrigin-RevId: c59559e431806b7d4345594f34fd6de99009b906
Change-Id: I8019d33ada555a901497bd13eaad6a3c9253e60f
1 file changed
tree: beda159efefab7a493d99459eed2023b36b34914
  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.