| commit | 3f3c370555f955f816639d0b2615d91adaea22c6 | [log] [tgz] |
|---|---|---|
| author | Andy Weiss <dragonbear@fuchsia.infra.roller.google.com> | Thu Nov 18 16:06:24 2021 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Nov 18 08:07:37 2021 -0800 |
| tree | 8a1c674bf55e45052e7b41029a73c8743f81fbdd | |
| parent | 54b027a49f8af982f7f622a61169253ae51bd5ae [diff] |
[roll] Roll fuchsia [ffx] Make sure ascendd binds the socket This is a bit speculative from the failures we are seeing in test flakes. My reading of the code is that there is technically a race condition between telling ascendd to start up and bind a UDS and the daemon trying to talk to that UDS. If the bind does not get scheduled in time we could get the daemon to timeout trying to connect. It would look like the failures that we are seeing where we are getting a file not found error from the OS at connect time. This should not be too big of a difference from the current path, it just forces some of the work to serialize before other work that might depend on it. In practice this appears to happen anyway most of the time so this should not be that big of a difference. Original-Bug: 84938 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/602328 Original-Revision: 5e1789f7e9c1f409617c11f5f48e47cc0c9dbeb1 GitOrigin-RevId: d19e0269c0505d09615d53c4521353f7e5cbfb61 Change-Id: I949bec11f1a20fbd854d7e59cb49de12140cf272
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.