[roll] Roll fuchsia [cros-es] Migrate core-tests to safer teardown

This CL migrates chromiumos-ec-core-tests to use a single-threaded
dispatcher loop. The motivation for this change is that
|component::OutgoingDirectory| is thread-unsafe and should
not reference a multi-threaded dispatcher. Doing so will
often lead to flakes. If the |component::OutgoingDirectory|
is being destroyed, _while_ there's an in-flight FIDL request
on the internal VFS object, there's a risk for use-after-free
failures.

The pattern used here, with |PerformBlockingWork| is safe and
compatible with multi-threaded code.

Original-Bug: 118385
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/791472
Original-Revision: 9b34b3f6d68659ca8d24d4de0040650ae9865f5d
GitOrigin-RevId: f323cde8f490cc270c02637f03912dcdf4311ab5
Change-Id: Iefe12a1b1b6ff9f213f04e8015c8105b4ed40d30
1 file changed
tree: 39c780681ba8f68b011a710c68990a845ec7ccc7
  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.