[roll] Roll fuchsia [ld] Send main bootstrap message in test harness This makes the test fixtures that launch a Zircon process usually send the main bootstrap protocol message for libc, not only the startup dynamic linker's message. The same log pipe is reused as the stderr in both messages. The existing test cases never read that message from the bootstrap channel, since they don't use a libc. The few test cases make custom use of the channel already use the explicit opt-out via RunWithCustomBootstrap(). A new test case uses the ld-tests fixtures to launch libc's generic noop-test executable, thus exercising the test harness bootstrap protocol behavior against a production consumer. Original-Bug: 342469121 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1459710 Original-Revision: cd43d5ee28175b4905057d18c98f571a1bfe5fd0 GitOrigin-RevId: b270276a3428940662c6b74b85cd5598db19a9a8 Change-Id: Ic24f7e50bed405d959b393047448c38e88dd01b6
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.