We observe both of these tests timeout when running on slow systems (e.g. the Fuchsia/ARM64/Rel FYI bot, which runs Fuchsia under QEMU s/w emulation https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/fuchsia-fyi-arm64-rel/476).

Both of these tests run on Fuchsia/ARM64/Rel and pass after between ~35s and ~50s.  Because TestLauncher is configured with a per-test timeout of 45s, the longer runs are retrospectively marked as timeouts.

Both tests include eight death expectations.  Under Fuchsia (and other fork()-less platforms, like Windows), this means they are performing eight content_unittests process startup/run/teardown(crash) cycles, in sequence, for each test.

The same issue appears to affect these tests on linux-win-cross-rel (issue 851446).

Short-term we should either increase the per-test timeout for content_unittests on this bot, or disable these long-running tests.