Reland "Disable some flaky win-asan glic-api tests" This reverts commit 48dab07cf68a9f0ca07bdb1a633ccc80f0981842. Reason for revert: relanding with bug fix Bug: 439218355 Original change's description: > Revert "Disable some flaky win-asan glic-api tests" > > This reverts commit 6c1fdb61ab017cabc3967c3a95036a4092a27274. > > Reason for revert: Broke win-asan build: > https://ci.chromium.org/ui/p/chromium/builders/ci/win-asan/36651/overview > > Bug: 439218355 > Original change's description: > > Disable some flaky win-asan glic-api tests > > > > Bug: 439218355 > > Change-Id: I7cc194349625655b81f1ffcf9cde57e24038d56d > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6858616 > > Reviewed-by: Ahmed Moussa <ahmedmoussa@google.com> > > Auto-Submit: Dan Harrington <harringtond@chromium.org> > > Commit-Queue: Ahmed Moussa <ahmedmoussa@google.com> > > Cr-Commit-Position: refs/heads/main@{#1502943} > > Bug: 439218355 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Change-Id: I1dbc561eaf7895fcf063851e603992357862864c > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6860362 > Auto-Submit: Thomas Guilbert <tguilbert@chromium.org> > Owners-Override: Thomas Guilbert <tguilbert@chromium.org> > Commit-Queue: Thomas Guilbert <tguilbert@chromium.org> > Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> > Cr-Commit-Position: refs/heads/main@{#1502978} Bug: 439218355 Change-Id: I30d634501a9dbc11100b325982b7388ac23180af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6858062 Reviewed-by: Thomas Guilbert <tguilbert@chromium.org> Commit-Queue: Ahmed Moussa <ahmedmoussa@google.com> Reviewed-by: Ahmed Moussa <ahmedmoussa@google.com> Cr-Commit-Position: refs/heads/main@{#1503043}
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.