[roll] Roll fuchsia [component][fuzzing] Handle repeated signals to target processes This CL modifies how realmfuzzer's target `Process` handles signals received from the engine's `ProcessProxy`. In particular, it relaxes `Process`'s expectation that signals will strictly alternate between `kStart`/`kStartLeakCheck` and `kFinish`. In practice, when trying a finite set of inputs, the engine may instruct the process proxies to start, only to subsequently determine no inputs remain. This can leave the processes stuck, especially if a subsequent workflow sends different signals than the ones the process is expecting. With this change, the process will always handle all signals. If it receives multiple `kStart`s, it will simply reset the accumulate coverage. If it receives multiple `kFinish`es, it will republish the coverage. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/793799 Original-Revision: 2ff365c475b021b26165b03d2fa372b3ff425f22 GitOrigin-RevId: 57021fd6708eda30ab2e5534bdc0dd83aa56d1aa Change-Id: Ifd6ce23db6af4e4571df894bde4d6011695ec233
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.