[roll] Roll fuchsia [system-update-checker] Check for RebootController PEER_CLOSED

This CL makes system-update-checker explicitly check if the
RebootController server is closed before making the one-way Unblock()
call, because soon the Rust bindings will hide PEER_CLOSED errors from
one-way interactions (fxbug.dev/113160).

There is still a race here. This CL just makes it more explicit. It
might be better to model this as a 2-way method, but this preserves the
existing behavior for now.

Test: fx test system-update-checker-tests
Original-Bug: 113160
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/800322
Original-Revision: d7e393d180309590f927ae6e9556f7a8cc8caf53
GitOrigin-RevId: e1a643f1bbe37caab832583fb1041038de492c54
Change-Id: I3b5ddb8ab1cad00ead650d69985bc28bd3297fc2
1 file changed
tree: 425b5333aa84594530484ee848e0db24c1d68407
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

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.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.