| commit | ecd12b99b913343fcb773e101034fab76fbc69c6 | [log] [tgz] |
|---|---|---|
| author | Drew Fisher <zarvox@fuchsia.infra.roller.google.com> | Tue Nov 28 21:04:06 2023 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Nov 28 13:05:30 2023 -0800 |
| tree | 44854a0bb5e5303e91cf1a826ffbb8f1f269c3de | |
| parent | 21da76587628e82d37de62a7b35ddcfbde7706f9 [diff] |
[roll] Roll fuchsia [botanist] When retrying flashing, read from all serial sockets We've observed these retries get attempted, but they appear to subsequently fail. In particular, it seems that something is causing the serial output from the mux to stop, so botanist never sees the serial logline indicating that the device has successfully booted. I hypothesize that botanist failing to read from the socket it writes to is maybe causing the serial mux implemented by dms to block when it would otherwise attempt to write serial output from the device to other clients with open sockets. Between the previous bug which would cause us to fail to close the socket entirely and a bug where failing to read from the socket causes us to block serial output to all mux clients, we were never seeing serial logs after partway through reboot after the hard power-cycle. Let's start by trying to be a better-behaved mux client, and separately we can look into if it makes sense to make the mux drop lines to clients that aren't keeping up, or if we'd rather keep things blocking and demand well-behaved serial clients. Original-Bug: b/289078335 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/952292 Original-Revision: eedc3486ec091fca0d1d35fb95deee34b28ee8af GitOrigin-RevId: 4f78599547ddf0b23ac9e787b92e20722ae7bf7c Change-Id: Ib55a73bd4923d30c3d7db01da5e92ed733a0e872
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.