commit | d4f79b52565a22866275e00e9c8b6ea53fa1bae8 | [log] [tgz] |
---|---|---|
author | Dominique Fauteux-Chapleau <domfc@chromium.org> | Tue Oct 15 18:43:16 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 15 18:43:16 2024 |
tree | f46a7797daddc26f1f5bd9af89873f41102096dc | |
parent | 270f97e90833f54ed718bdfb8e6d735787d5df87 [diff] |
Revert "Move DataProtectionClipboardBrowserTest to interactive_ui_tests" This reverts commit b57268476629c9f6a0f92ad33903bbc6aa544427. Reason for revert: Didn't fix flakes, see crbug.com/360052665#comment20 Original change's description: > Move DataProtectionClipboardBrowserTest to interactive_ui_tests > > This CL attempts to de-flake DataProtectionClipboardBrowserTest for Mac > by making the tests run in the interactive_ui_tests target to fix focus > issues. > > Bug: 360052665 > Change-Id: If28e2332760e106d4f913b531aef4d158dbb63be > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5912394 > Auto-Submit: Dominique Fauteux-Chapleau <domfc@chromium.org> > Reviewed-by: Nasser Al-shawwa <alshawwa@chromium.org> > Commit-Queue: Dominique Fauteux-Chapleau <domfc@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1364975} Bug: 360052665 Change-Id: Iae98815df35185b59f33d2ea88ae3e8b33c102d8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5933221 Reviewed-by: Nasser Al-shawwa <alshawwa@chromium.org> Commit-Queue: Dominique Fauteux-Chapleau <domfc@chromium.org> Auto-Submit: Dominique Fauteux-Chapleau <domfc@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1368895}
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.