[roll] Roll fuchsia [elf_runner] suppress log warnings on certain components There are some ELF programs that upon exit, produce certain exit codes that are "normal" part of operation. The most interesting of these from Fuchsia's perspective is the sshd binary, which returns a 255 exit code when the client hangs up unexpectedly (e.g. sending SIGINT to a running ssh process). Due to how `ffx` interacts with the Target over ssh in a user-interactive mode, it is commonplace for the user to SIGINT their locally running ffx processes which SIGINT's the SSH process running on the Host, which causes misleading logs on the Target, implying that sshd has had an error (when in-fact there is none). Tests: Added unit tests. Also can do manual testing by: Flash target with new elf_runner binary, run `ffx log --severity trace --component klog` in one terminal. Then in another terminal run `ffx -c ssh.controlmaster.mode='none' log`. Wait until output and then hit Ctrl+C. Observe the trace log in the first console. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1449531 Original-Revision: 5680e1d809b2334042da5336511953dac5683b7e GitOrigin-RevId: 9966425c730bc7cf1a7b9d633cd960db2d520d30 Change-Id: I4ff2256189bb00f2af78e867a9c2a64e388efd62
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 in one of the communication channels documented at get involved.
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.