commit | b374bd6f372ac3ead20ed8b3a53ad1b60bd26b50 | [log] [tgz] |
---|---|---|
author | Robert Sesek <rsesek@chromium.org> | Thu Mar 11 20:46:29 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 11 20:46:29 2021 |
tree | b14afaca21c20cf5e402939b5624f7b15f659774 | |
parent | 9ca1bfd9d007d167fcadd8f409114668d5428e50 [diff] |
Reland "Default to the threadsafe GTest death_test_style." This is a reland of b579146695ba0c045d26b022e63d199bd23f8349 Original change's description: > Default to the threadsafe GTest death_test_style. > > Using the default style of "fast" can lead to subtle test flakiness. > And on macOS, most of CoreFoundation is not safe to use after fork() > without exec(). Several //base implementations on Mac use CF, and so it > is almost never safe to use the "fast" death_test_style. > > Change-Id: Idcee977978561e0a57ace20b53f597c566708692 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/570500 > Commit-Queue: Robert Sesek <rsesek@chromium.org> > Reviewed-by: danakj <danakj@chromium.org> > Reviewed-by: Gabriel Charette <gab@chromium.org> > Cr-Commit-Position: refs/heads/master@{#854588} Change-Id: I6a30c23e5846b508ef0c1ab29a899c5a7b9f1293 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2747682 Reviewed-by: Sophie Chang <sophiechang@chromium.org> Reviewed-by: Gabriel Charette <gab@chromium.org> Reviewed-by: danakj <danakj@chromium.org> Commit-Queue: Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#862111}
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.