[modular][testing] Fix race: uninitialized access in TestHarnessLauncher

Observed this race in flaky test:
TestHarnessBuilderTest.AddServiceFromComponent.

I suspect that the thread might be accessing an uninitialized
std::mutex. This CL changes the initialization order to avoid this
condition.

Test: I'm no longer able to make the test hang using:
fx run-test test_harness_fixture_test -t test_harness_fixture_test_bin
-- --gtest_filter='TestHarnessBuilderTest.AddServiceFromComponent'
--gtest_repeat=10000

Change-Id: I11824652f22b08a80a9e34533e5cdca2b9cc09e3
2 files changed
tree: 838eb6424a23a44a2418055e8fcba5ed39c72cd2
  1. boards/
  2. build/
  3. buildtools/
  4. bundles/
  5. docs/
  6. examples/
  7. garnet/
  8. peridot/
  9. products/
  10. scripts/
  11. sdk/
  12. src/
  13. third_party/
  14. tools/
  15. zircon/
  16. .clang-format
  17. .clang-tidy
  18. .dir-locals.el
  19. .gitattributes
  20. .gitignore
  21. .gn
  22. AUTHORS
  23. BUILD.gn
  24. CODE_OF_CONDUCT.md
  25. CONTRIBUTING.md
  26. LICENSE
  27. OWNERS
  28. PATENTS
  29. README.md
  30. rustfmt.toml
README.md

Fuchsia

Pink + Purple == Fuchsia (a new operating system)

What is Fuchsia?

Fuchsia is a modular, capability-based operating system. Fuchsia runs on modern 64-bit Intel and ARM processors.

Fuchsia is an open source project with a code of conduct that we expect everyone who interacts with the project to respect.

How can I build and run Fuchsia?

See Getting Started.

Where can I learn more about Fuchsia?

See the documentation.