Component Updater: Eliminate test that deletes updater prefs. My first thought was to run the test only in Chromium-branded builds to avoid deleting production updater data. However, the test suite only runs (and only makes sense to run) in Chrome-branded builds. Although it would be possible to inject a mock prefs file, the test doesn't actually cover anything that's sensitive to the contents of the file (unlike the tests above). Therefore, eliminating the test seems like the easiest solution. Fixed: 358158949 Change-Id: I785b6dc179b9c8d52f5a927b244bd82caaedce82 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5802816 Auto-Submit: Joshua Pawlicki <waffles@chromium.org> Reviewed-by: Sorin Jianu <sorin@chromium.org> Commit-Queue: Sorin Jianu <sorin@chromium.org> Cr-Commit-Position: refs/heads/main@{#1344926}
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.