SyncFakeServerTestCase: Properly wait for Sync to become active A few test cases in SyncFakeServerTestCase are disabled due to flakiness. What they have in common is that they use waitForSyncEngineInitialized to wait for Sync to become active, which is not quite correct - the engine being initialized happens about halfway through the initialization process. This CL changes those tests to use waitForSyncTransportStateActiveWithTimeout instead. This CL does not re-enable the tests yet - that will happen separately afterwards. Bug: 1420598, 1222348 Change-Id: Ifcf1cedf68d407d8caae281c1bc9d995ceeec112 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4315911 Commit-Queue: Marc Treib <treib@chromium.org> Reviewed-by: Stepan Khapugin <stkhapugin@chromium.org> Reviewed-by: Mihai Sardarescu <msarda@chromium.org> Cr-Commit-Position: refs/heads/main@{#1115605}
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.