Reland "[gtest] Enforce per-test timeout" This is a reland of commit 55908f9fe42a83d211a01c6b228374516f47059f Changes from original: crrev.com/c/3787902 fixes a discovered stack use-after-return. This fix may be unrelated to the test that prompted the revert, ToolsSanityTest.AsanHeapOverflow on ChromeOS-on-Linux, which reoccured on ToT without this patch. Discussion: crbug.com/1342445 Original change's description: > [gtest] Enforce per-test timeout > > The gtest launcher currently enforces an aggregate timeout on each batch > of tests. Offending tests can consume the unused time of other tests in > the batch, which can cause builders to hang. > > This change introduces a more granular timeout detection mechanism. For > each child process, the launcher (parent) process periodically reads its > incomplete XML results file and kills any that have not made progress. > The launcher can then retry the tests that did not complete. > > Bug: 1213243 > Change-Id: I4d638c6c346038d1d137b16dbda51a7cb7703363 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3669127 > Reviewed-by: Gabriel Charette <gab@chromium.org> > Commit-Queue: Jonathan Lee <jonathanjlee@google.com> > Cr-Commit-Position: refs/heads/main@{#1021366} Bug: 1213243 Change-Id: I3e785c70bb73d0e37acfe461b4a18212f9651f5e Cq-Include-Trybots: luci.chromium.try:linux_chromium_chromeos_asan_rel_ng,linux_chromium_asan_rel_ng,win-asan,mac_chromium_asan_rel_ng Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3755603 Commit-Queue: Jonathan Lee <jonathanjlee@google.com> Reviewed-by: Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/main@{#1029272}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.