[roll] Roll fuchsia [emu] Swap Mutex guards for serial tests

The attached bug explains how we recently discovered that using automock
on async functions is unstable, and attempting to work around this with
a Mutex is insufficient since the mutex is thread-owned and thus does
not guard the static mock contexts between the various tests.

This CL removes the mutex and replaces it with annotations to serial the
tests that utilize the mocking context instead. By serializing the
tests, we give them atomicity and ensure that the context is set, used,
and destroyed all before the next test starts. While this can slow down
the test execution, these are very fast tests and the delay is not
enough to notice or care.

Original-Bug: 119219
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/789178
Original-Revision: 0e05abe95c0ed8213fa52eef6ffb7eff6e8e2e0b
GitOrigin-RevId: 1a7e103c504a98046a4ad9836030d3f387713e56
Change-Id: Ie4bdb417a86ca9fce539fa8843fb0c3171708fc9
1 file changed
tree: fb419a5d539f1b491e0ad2809a0cbfbcf0b81bf5
  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.