| commit | 21c7fdd5b43c9abed4001106c43550abae5ad2f5 | [log] [tgz] |
|---|---|---|
| author | Charles Celerier <chcl@fuchsia.infra.roller.google.com> | Thu Jan 30 12:38:31 2025 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jan 30 12:41:57 2025 -0800 |
| tree | c54923d221a86602ace90616ec836a7b75c1e706 | |
| parent | 78366c5beb47a23cd3fd84a428ddaedb05c6c9d4 [diff] |
[roll] Roll fuchsia [sdk] Only include RTC conformance test on Linux host builds The mac SDK will no longer contain //src/tests/end_to_end/rtc:rtc_conformance_test_sdk which itself contains a Lacewing test. In general, Lacewing tests are only designed to run on Linux hosts, so we should not build them for mac. This change contains a horrendous hack. While constructing this change, I found that a mac builder would fail when I removed //src/tests/end_to_end/rtc:rtc_conformance_test_sdk from the build graph. After some debugging, it appeared that removing that target caused //src/developer/ffx/frontends/ffx:ffx_bin_unversioned to be built in parallel with various ffx tool metadata targets leading to a failure to read system domain SSL certificates from the host. The hack is to add a dependency from each metadata target to ffx_bin_unversioned to ensure ffx_bin_unversioned is built before them. For a currently unknown reason, this steps around the mac builder failure. If this change lands successfully, then we know we've fixed https://fxbug.dev/388826354 because otherwise we would expect the mac builder failure to continue to reproduce. It's really https://fxrev.dev/1195919 that fixes the issue though. Original-Fixed: 388826354 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1192733 Original-Revision: 5c8f13a86b955315b3d79a68255c3b4fc2936607 GitOrigin-RevId: 8d126a0f58409e5d8b5a5af97975c64852e6ec55 Change-Id: Id68be711f06b0412bb2b21aabc49304bf7b026b4
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.