Autoshard chromium/src test suites This is an automated CL generated by the autosharder. Optimal shard counts for test suites are calculated by querying recent runtimes. The build that created this CL was https://ci.chromium.org/b/8712552361195164609 R=rubber-stamper@appspot.gserviceaccount.com Ignore-Freeze: True Change-Id: I0fcc6597d5e9b54490cbb6215d780db40e6ce27f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6630234 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: chromium-autosharder@chops-service-accounts.iam.gserviceaccount.com <chromium-autosharder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: chromium-autosharder@chops-service-accounts.iam.gserviceaccount.com <chromium-autosharder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1471143}
ChromiumChromium 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.