commit | 009fb5f11796d3db3acda99fcf72e3b7892c304c | [log] [tgz] |
---|---|---|
author | Joshua Pawlicki <[email protected]> | Fri Jan 18 21:44:47 2019 |
committer | Commit Bot <[email protected]> | Fri Jan 18 21:44:47 2019 |
tree | 5f1e601e7f26a13febab4219b847496b11da8207 | |
parent | 98fc6f195ceb0426f8e227df9248d55c1330aa13 [diff] |
Reland 0a1b4fb27a194a6c4ec3fa22040a4e8152cd45b (https://chromium-review.googlesource.com/c/chromium/src/+/1344880) Relative to the original CL, this changes the setter for skipping scheduled updates into a global value that can be set by browser tests prior to constructing and kicking off the extension updater. This is the pattern used by content verification and other extension-behavior customization. It's my hope that taking this approach will eliminate a lot of long- standing flakiness in several of the tests, so if this sticks I can follow it up with a CL re-enabling several tests. (Or another person who has a better relationship with extensions can.) OCL description: > Simplify extension update check delay after browser start. > > Bug: 907219 > Change-Id: I067fcb333b43f60441e1789cac8caf5b996b7e5d > Reviewed-on: https://chromium-review.googlesource.com/c/1344880 > Commit-Queue: Joshua Pawlicki <[email protected]> > Reviewed-by: Gabriel Charette <[email protected]> > Reviewed-by: Sergey Poromov <[email protected]> > Reviewed-by: Brian White <[email protected]> > Reviewed-by: Devlin <[email protected]> > Cr-Commit-Position: refs/heads/master@{#620845} Bug: 907219, 920040 Change-Id: I35ff0311f84294eca6cd1b23a3fd612d53ea42db Reviewed-on: https://chromium-review.googlesource.com/c/1412796 Auto-Submit: Joshua Pawlicki <[email protected]> Reviewed-by: Devlin <[email protected]> Reviewed-by: Brian White <[email protected]> Reviewed-by: Sergey Poromov <[email protected]> Reviewed-by: Gabriel Charette <[email protected]> Commit-Queue: Joshua Pawlicki <[email protected]> Cr-Commit-Position: refs/heads/master@{#624302}
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.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .