[roll] Roll fuchsia [network] Use highmem builders for Netstack3 and NUB

These were already being used in a couple cases:

- Netstack3 debug builds when enabling optimizations caused a major
  increase in compilation times on the regular builders.
- Debug NUB compilation because the binary is large and needs more
  memory.

This enables highmem builders for the remaining large targets we're
aware of, which are the release Netstack3 and NUB builds.

Targets that notably aren't moving to the highmem builders are:

- Netstack3 instrumented targets, since those aren't optimized at all.
- Non-Netstack3 NUB libs, since as far as we know those don't have the
  same build time issues.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1153392
Original-Revision: 1e4b7157f2c51c4336baa036b8c64270ce7e3938
GitOrigin-RevId: 40d3428e63c82c046ea3b161323adbd655ddad44
Change-Id: I232ff11beed20ba4e9fe942dc8957d17b8424eda
1 file changed
tree: bb5caff044905787f1a0bf8486fc43f6075d685a
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
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.