commit | 9f7216aa3b24e6a7fddd948c8e2cf71747cc1f3c | [log] [tgz] |
---|---|---|
author | Hiroshige Hayashizaki <hiroshige@chromium.org> | Wed Feb 14 19:37:29 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Feb 14 19:37:29 2024 |
tree | eda65d2b0fa13baca8f9e8d26300c7889e2c286b | |
parent | 78b89c566f2731f4ab17057b78cb93da57c4d9c3 [diff] |
Reland "Re-enable PrivateNetworkAccessBrowserTest.DeprecationTrialSettingNotInheritedByDataURL" This reverts commit d27b8eb9cad8730e92128a7fe9cd6143863c8279. Reason for reland: The original commit was reverted because it landed before the fix https://chromium-review.googlesource.com/c/chromium/src/+/5288036. Now the fix has landed. Original change's description: > Revert "Re-enable PrivateNetworkAccessBrowserTest.DeprecationTrialSettingNotInheritedByDataURL" > > This reverts commit e503ac21dbc1e050bea0213810166ae52367dd8b. > > Reason for revert: b/324679506. The test failed on android-bfcache-rel again after re-enabling it. > > Original change's description: > > Re-enable PrivateNetworkAccessBrowserTest.DeprecationTrialSettingNotInheritedByDataURL > > > > This reverts commit eef095162e82f7ff038290114b1488782f2250b5. > > > > Reason for revert: After a potential fix > > https://chromium-review.googlesource.com/c/chromium/src/+/5288036 > > lands, to see the flakiness is actually fixed. > > > > Original change's description: > > > [garderner] Disabling PrivateNetworkAccessBrowserTest.DeprecationTrialSettingNotInheritedByDataURL test. > > > > > > In this cl, disabling DeprecationTrialSettingNotInheritedByDataURL. > > > Also re-enabling PrivateNetworkRequestPolicyCalculatedPerOrigin test, > > > not needed to be disabled. > > > > > > Change-Id: I94726da029db5de0bf61cb2e50ddcc0e11dfd505 > > > Bug: b/324679506 > > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5293517 > > > Reviewed-by: Hailey Wang <haileywang@google.com> > > > Owners-Override: Ritika Gupta <ritikagup@google.com> > > > Commit-Queue: Ritika Gupta <ritikagup@google.com> > > > Cr-Commit-Position: refs/heads/main@{#1260114} > > > > Bug: 324679506 > > Change-Id: Iecf14c0e7cfea64dcebc68e5a0da9438f6fd731b > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5294579 > > Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> > > Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> > > Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#1260388} > > Bug: 324679506 > Change-Id: Ie6d795183a94afd764e31cb0e6b469e8942025aa > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5296954 > Owners-Override: Xi Han <hanxi@chromium.org> > Auto-Submit: Xi Han <hanxi@chromium.org> > Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> > Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> > Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> > Commit-Queue: Xi Han <hanxi@chromium.org> > Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1260490} Bug: 324679506 Change-Id: I7d97b2a8faee451144492679c1f38d042f2d73fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5297159 Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by: Anton Maliev <amaliev@chromium.org> Cr-Commit-Position: refs/heads/main@{#1260640}
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.