[roll] Roll fuchsia [rbe][link] Support remote dump_syms

When linking the unstripped binary remotely,
it makes sense to to also run `dump_syms` remotely,
so that their cache-hits correlate.
(Same reasoning for `strip`-ing remotely.)

`dump_syms` invocation is changed so that the redirection
happens inside the `log-it.sh` script, and produces the same output.
This avoids the issues with redirecting a remote execution's
output to a local file, e.g. stdout/stderr size limitations.

Original-Bug: b/42083070
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1008217
Original-Revision: 3ffd61dea8f2ba1078a9f420d479d836f153ef02
GitOrigin-RevId: 244bf8b7a68a8900a5d8613fc45be231854d54fe
Change-Id: Iad3ec8c9a3bb51c8c53a46593f7f040f93459048
1 file changed
tree: b6b2c8b5ffba4df7532d960d2b710361b50d6c35
  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 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.