[roll] Roll fuchsia [rbe] Control signal-forwarding policy

fuchsia-reproxy-wrap.sh:
* --signal-policy flag to control signal forwarding in nested wrapper
  chains.  Default is 'relay' which isolates the wrapped command in
  its own process group, and forwards signals to the PID, but not PGID.
  Previously, it was forwarding to the entire group ('relay-group'),
  which risks multiplying signals when composing wrappers.
  Each wrapper layer is responsible for forwarding signals to its
  immediate wrapped child (which then assumes responsibility for
  subprocess it owns).  This remains compatible with ninja, which
  takes control of its own forwarding to subprocesses.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1574266
Original-Revision: 78ff32f888a6e2554b8371bd98fc2d84a3a58bb7
GitOrigin-RevId: fb4b1376fb1e48c7fdf38a9c2ffb32dd0d05e278
Change-Id: I3ef3cd33520f1828e16717cb3854345ea757f101
1 file changed
tree: 6404609c01b9c2db313e91d21b99f5f582f820cd
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. 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 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.