commit 1fa3d4050e050e7f4e2f0eb6d6e9faa5f884ac6e
author Satsuki Ueno <satsukiu@google.com> Thu Jun 23 20:31:11 2022 +0000
committer CQ Bot <fuchsia-internal-scoped@luci-project-accounts.iam.gserviceaccount.com> Thu Jun 23 20:31:11 2022 +0000
tree 5c47ef25bc7aa0bcbe56ac01e2a40022cb74f583
parent 5555d2ae77e3c134f9d5f4dd16292ab87d4647c2

[run-test-suite] Use Rust test for timeout tests

gtest tests always output a note about the random seed used to run a
test.
I tried making some changes which affected the timing at which stdout
is displayed to the user, and this caused timeout tests to fail because
they started showing stdout where none was shown before. Since the test
is specifically verifying timeout behavior, it is inherently sensitive
to timing.
To eliminate flakes related to stdout that may or may not be present,
this change makes the timeout test use a Rust test instead, which never
outputs stdout.

Multiply: run_test_suite_integration_tests

Change-Id: I00f2749964e211fa290e06bfaf72ddc294115e4a
Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/686003
Fuchsia-Auto-Submit: Satsuki Ueno <satsukiu@google.com>
Reviewed-by: Ankur Mittal <anmittal@google.com>
Commit-Queue: Auto-Submit <auto-submit@fuchsia-infra.iam.gserviceaccount.com>