[roll] Roll fuchsia [ffx][repository] fix test flake from ExecutableFileBusy

When running tests in parallel, one test thread can have the executable
script for another test open for writing when the second test tries to
spawn it. The `fork` call inside `Command::spawn` inherits the file
descriptors of the parent, including the write handle to the script.
This causes the `exec` call to fail with `ExecutableFileBusy` (ETXTBSY).

This change introduces a Mutex to serialize the creation and spawning of
these test scripts, ensuring that no process can hold a write handle to
an executable that another process is trying to run.

See also: https://github.com/rust-lang/rust/issues/114554

Original-Bug: b/450633577
Original-Fixed: b/450633577
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1408715
Original-Revision: bd0a4c14be05e300761cc096328cc5c19f63d74d
GitOrigin-RevId: e28f503d976f30e892c4717d43609b511da99c61
Change-Id: I5633be2536ebca06c248296d6b642ab302e9ad78
1 file changed
tree: ad9b4a43d24f053c0f77f5d5a2f7378e72d87368
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
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 in one of the communication channels documented at get involved.

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.