Chromium test launcher checks if test took less than TestTimeouts::test_launcher_timeout(), and reports a timeout even if the test was a success[1].
There's a test in ipc_tests, IPCSyncChannelTest.ChattyServer that takes over 25 seconds on my developer machine. However, we also run the test as part of our CI workflow in more resource constrained environment, where it sometimes hit the 45 seconds mark, eg.
[ OK ] IPCSyncChannelTest.ChattyServer (45567 ms)
This results in flakiness.
It would be nice if the per test timeout was configurable somehow, maybe as a flag for the launcher.
[1] - https://cs.chromium.org/chromium/src/base/test/launcher/unit_test_launcher.cc?sq=package:chromium&dr=C&rcl=1476213403&l=312
Comment 1 by phajdan.jr@chromium.org
, Oct 13 2016Owner: phajdan.jr@chromium.org
Status: WontFix (was: Untriaged)
It's not hardcoded, but controlled by --test-launcher-timeout flag. Please see base/test/test_timeouts.cc : // Test launcher timeout is independent from anything above action timeout. InitializeTimeout(switches::kTestLauncherTimeout, action_timeout_ms_, &test_launcher_timeout_ms_);