[ServiceWorker] Wait for redirect race request in Subresource_FetchHandler_Wins_Redirect test The fetch handler response can complete before the embedded test server observes the losing race network request. This makes the request-count assertion timing-dependent. Pump the run loop until the server records the request before checking that it was deduplicated, matching the synchronization used by nearby race network request tests. This flake was observed in downstream Windows, where the fetch-handler response completed before the EmbeddedTestServer request monitor was visible to the test. The test then reported an expected request count of 1 but observed 0. Bug: 340949948 Change-Id: Ie8eb45420fd04ece24eb9127d63d2a6b01595fb5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8413735 Reviewed-by: Yoshisato Yanagisawa <yyanagisawa@chromium.org> Commit-Queue: Monica Chintala <monicach@microsoft.com> Reviewed-by: Shunya Shishido <sisidovski@chromium.org> Cr-Commit-Position: refs/heads/main@{#1700067}
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.