- 24 Mar, 2020 40 commits
-
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/82dd375715f3..643201ce76ac git log 82dd375715f3..643201ce76ac --date=short --first-parent --format='%ad %ae %s' 2020-03-24 treehugger-gerrit@google.com Merge "traced_perf: delay proc-fd signal by 50ms; best-effort execve race mitigation" Created with: gclient setdep -r src/third_party/perfetto@643201ce76ac If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Bug: None Tbr: perfetto-bugs@google.com Change-Id: Icfbea4282db5aec0f655aab9216616e458514e29 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117991Reviewed-by:
chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#752803}
-
Rohit Agarwal authored
We currently don't have extensive tests on java side which checks any leakage of data across activities. This CL adds browser tests to check permission leaks. Bug: 1035770 Change-Id: If5148dead41c8dbda7b1885f48acaf16b8fe90a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2111095 Commit-Queue: Rohit Agarwal <roagarwal@chromium.org> Reviewed-by:
Peter Conn <peconn@chromium.org> Reviewed-by:
Rohit Agarwal <roagarwal@chromium.org> Reviewed-by:
Ramin Halavati <rhalavati@chromium.org> Cr-Commit-Position: refs/heads/master@{#752802}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/glslang/+log/1f0fcbe5a30f..393c564ae0b4 git log 1f0fcbe5a30f..393c564ae0b4 --date=short --first-parent --format='%ad %ae %s' 2020-03-24 johnkslang@users.noreply.github.com Merge pull request #2149 from kainino0x/web-fix-cmake2.8 Created with: gclient setdep -r src/third_party/glslang/src@393c564ae0b4 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/glslang-chromium-autoroll Please CC radial-bots+chrome-roll@google.com,cnorthrop@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_angle_vk32_deqp_rel_ng;luci.chromium.try:android_angle_vk32_rel_ng;luci.chromium.try:android_angle_vk64_deqp_rel_ng;luci.chromium.try:android_angle_vk64_rel_ng;luci.chromium.try:linux_angle_deqp_rel_ng;luci.chromium.try:linux-angle-rel;luci.chromium.try:win-angle-rel-32;luci.chromium.try:win-angle-rel-64;luci.chromium.try:win-angle-deqp-rel-32;luci.chromium.try:win-angle-deqp-rel-64 Bug: None Tbr: radial-bots+chrome-roll@google.com,cnorthrop@google.com Change-Id: I7bc47289f13bd1874b30b8f42a3663bfff678876 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117990Reviewed-by:
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/3decd1af6bde..540bdf92531d git log 3decd1af6bde..540bdf92531d --date=short --first-parent --format='%ad %ae %s' 2020-03-24 bclayton@google.com Regres: Add new run_testlist flags Created with: gclient setdep -r src/third_party/swiftshader@540bdf92531d If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Please CC swiftshader-team+autoroll@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: Ied18b3424f272a80515b320d23657c7c92d636b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117489Reviewed-by:
-
Nohemi Fernandez authored
Due to the sign-in architecture migration that extracts sign-in logic into the mediator it is now possible to test this logic of the code. Bug: 971989 Change-Id: I9a8279007bc219d3a7415a7b404c981073f9024d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2098383 Commit-Queue: Nohemi Fernandez <fernandex@chromium.org> Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Jérôme Lebel <jlebel@chromium.org> Cr-Commit-Position: refs/heads/master@{#752799}
-
Gauthier Ambard authored
In some cases, when the items are created to match the existing WKBackForwardItem, the are not linked to any existing items and they don't inherit their user agent. This only happens when the back/forward navigation is happening before the beginning of the navigation. In that case, the URL of the WKWebView isn't linked to the URL of the current BackForwardItem. In is possible to find the actual item by checking if the URL of the back item or the forward item match the URL of the WebView. If it is the case, the UserAgent of this item can be inherited in the newly created item. It also updates the navigation manager unit tests, replacing the expectations by stub as the expectations weren't checked. This CL is also doing the same thing when getting push state: the new items has its UserAgent set to the previous item user agent. Fixed: 1043633, 1049094 Change-Id: If95d419ef02f6e786fee43de1e401fc4727284bc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2109700 Commit-Queue: Gauthier Ambard <gambard@chromium.org> Reviewed-by:
Ali Juma <ajuma@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#752798}
-
Nico Weber authored
Ran `./tools/clang/scripts/upload_revision.py a1762f9ceb9549b781b7418c7dbe23fe620648f6`. Bug: 1064198 Cq-Include-Trybots: chromium/try:mac_chromium_asan_rel_ng Cq-Include-Trybots: chromium/try:linux_chromium_cfi_rel_ng Cq-Include-Trybots: chromium/try:linux_chromium_msan_rel_ng Cq-Include-Trybots: chromium/try:linux_chromium_chromeos_msan_rel_ng Cq-Include-Trybots: chromium/try:linux-chromeos-dbg,win-asan Cq-Include-Trybots: chromium/try:chromeos-amd64-generic-cfi-thin-lto-rel Cq-Include-Trybots: chromium/try:linux_chromium_compile_dbg_32_ng Cq-Include-Trybots: chromium/try:win7-rel,win-angle-deqp-rel-32 Cq-Include-Trybots: chromium/try:win-angle-deqp-rel-64 Cq-Include-Trybots: chromium/try:dawn-win10-x86-deps-rel Cq-Include-Trybots: chrome/try:iphone-device,ipad-device Cq-Include-Trybots: chrome/try:linux-chromeos-chrome Change-Id: Id001edfdd985b7d1f0532107e0a9aa0f87ad084a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2113689Reviewed-by:
Hans Wennborg <hans@chromium.org> Commit-Queue: Hans Wennborg <hans@chromium.org> Auto-Submit: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#752797}
-
Viktor Semeniuk authored
This is a reland of 39bb3cd1 Original change's description: > [Passwords] No result view fix in password check > > This CL changes the way visibility of 'No result view' is calculated. > The label will be shown only if: > - user had successful check with 0 compromised passwords found > - user is signed in > - breach detection is turned on in settings > > Bug: 1061496 > Change-Id: I9f1e4b5f7aef51749b970964c2b701ee2193ba53 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2108501 > Commit-Queue: Viktor Semeniuk <vsemeniuk@google.com> > Reviewed-by: Jan Wilken Dörrie <jdoerrie@chromium.org> > Cr-Commit-Position: refs/heads/master@{#751674} Bug: 1061496 Change-Id: I838b9383f5a45733aac7dba34875fffc4e12355a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2111177Reviewed-by:
Jan Wilken Dörrie <jdoerrie@chromium.org> Commit-Queue: Viktor Semeniuk <vsemeniuk@google.com> Cr-Commit-Position: refs/heads/master@{#752796}
-
Rayan Kanso authored
This will allow eventually moving the URL to the AppHooksImpl in a downnstream CL, then removing the URL completely. Bug: 1045009 Change-Id: I3ed7398f238a77a93802dd086091544f1508029e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2109763 Commit-Queue: Rayan Kanso <rayankans@chromium.org> Reviewed-by:
Peter Kotwicz <pkotwicz@chromium.org> Reviewed-by:
David Trainor <dtrainor@chromium.org> Cr-Commit-Position: refs/heads/master@{#752795}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/12954138..afbcf655 Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I8b70d49d5141aac22c61ff6b98eeaa7772bf81a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117511Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#752794}
-
Stephen McGruer authored
Replaced with promise_rejects_js and promise_rejects_dom. Bug: 1051932 Change-Id: I5452a5237b476255a8f24e7b9ccddd41f5b30798 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2116562Reviewed-by:
Luke Z <lpz@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#752793}
-
Stephen McGruer authored
Replaced with promise_rejects_js and promise_rejects_dom. Bug: 1051932 Change-Id: I7a7b213a58dfb15eb2dea1325f904ea68e25e18b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2116192Reviewed-by:
-
Trent Apted authored
To test our sandboxed guest, we inject code into its frame when we detect it loading. However, we were not guaranteeing a particular load state when that injection occurred. This CL makes the injected test code more robust to load state, but also exposed a problem: our _integration_ tests (in chrome/browser/ chromeos/web_applications/media_app_integration_browsertest.cc) use content::WaitForLoadStop() before doing the injection in PrepareAppForTest(). This meant'DOMContentLoaded' would never fire in those situations and the event handler was dead code in that context. In reality, our integration tests do not use tasks tied to this handler anyway, so split out the parts of the injected JS that the integration tests actually use into a separate file. To support injecting multiple files, update SandboxedWebUiAppTestBase to initialize with a vector of files to inject rather than just one. Bug: 996088 Change-Id: Idec6c62ffa6c2d71c08ecddd3d69fd0684930e43 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2112032 Commit-Queue: Trent Apted <tapted@chromium.org> Reviewed-by:
dstockwell <dstockwell@chromium.org> Cr-Commit-Position: refs/heads/master@{#752791}
-
Stephen McGruer authored
Replaced with promise_rejects_js and promise_rejects_dom. Bug: 1051932 Change-Id: Ib6884f2caf4276cc94ed24c1e0a392d27fafa80b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2116329Reviewed-by:
-
Stephen McGruer authored
NOTRY=true TBR=robertma@chromium.org Bug: 1062984 Change-Id: Ic71cac577c53f1d94be17819a0e501ac9d56ee32 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117973Reviewed-by:
Stephen McGruer <smcgruer@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#752789}
-
Rune Lillesveen authored
This is the implementation of phase 2 of [1]. When collecting rules from StyleSheetContents into a RuleSet, push refptrs to each @media or @import media query along with its current evaluation into a vector on the RuleSet. When a media feature value or the media type changes, mark stylesheet collections which has media queries for active stylesheet update, but no longer clear their current RuleSet. Instead evaluate the media query sets in the RuleSets during active stylesheet and clear the RuleSet if the media query evaluation changed. This should avoid clearing RuleSets, hence cause less invalidation on changing media query affecting values. [1] https://docs.google.com/document/d/1TMqAq4k3aTHNH1m2sYoj-5QAndNmEXLI1QeD-oQ7jWE/edit#heading=h.vxytkk66ckr2 Bug: 1014920, 589083 Change-Id: I6ef9ffdfb2d94987796db15ebb8c39669e7cf96a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117110Reviewed-by:
Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#752788}
-
Marc Treib authored
- Remove fields that were never used - Mark no-longer-used fields as deprecated - Remove proto-to-value conversions for deprecated fields - Remove/update some comments Bug: none Change-Id: I906857a2d1f7b5e2fcc6df9b242f1744eb37fdfb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2098670 Commit-Queue: Marc Treib <treib@chromium.org> Reviewed-by:
vitaliii <vitaliii@chromium.org> Reviewed-by:
Markus Heintz <markusheintz@chromium.org> Cr-Commit-Position: refs/heads/master@{#752787}
-
Marc Treib authored
Adds a DCHECK to ProcessorEntityTracker::UpdateOrOverrideStorageKey Bug: none Change-Id: Ie1379add4a6ac5e5fa024f7a6ce55140234cc78e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2115472 Commit-Queue: Maksim Moskvitin <mmoskvitin@google.com> Auto-Submit: Marc Treib <treib@chromium.org> Reviewed-by:
Maksim Moskvitin <mmoskvitin@google.com> Cr-Commit-Position: refs/heads/master@{#752786}
-
Antonio Gomes authored
Relevant links: - original WK patch and fix: [1] and [2]. - W3 discussion that led to both WK and Blink to diverge from the spec temporarily (until it got fixed) and match other engine's behaviors (eg, Opera, Firefox): [3] [1] https://bugs.webkit.org/show_bug.cgi?id=116107 [2] http://trac.webkit.org/changeset/150087 [3] https://lists.w3.org/Archives/Public/www-style/2013May/0350.html BUG=1063749 R=dgrogan@chromium.org, robertma@chromium.org Change-Id: I3d2a087875402954b5b96ff011208bb869ed3664 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2115768Reviewed-by:
Robert Ma <robertma@chromium.org> Reviewed-by:
David Grogan <dgrogan@chromium.org> Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Cr-Commit-Position: refs/heads/master@{#752785}
-
Rune Lillesveen authored
Without this CL, every media-query-affecting value change clears RuleSet synchronously for all active stylesheets which have @media rules. Here we mark scopes for an active stylesheet update without clearing the RuleSet, but instead evaluate the size-dependent media queries when updating the active stylesheets. If a sheet had a RuleSet, and the media query result evaluation changed, clear the RuleSet and re-create it. The new behavior is implemented for MediaValueChange::kSize. The current behavior is kept for other media query changes than viewport and device dependent media value changes. That behavior is implemented behind MediaValueChange::kOther. This CL corresponds to phase 1 in [1]. Since this makes sure previously non-active sheets gets their media query evaluations checked when re-added as active sheets, this fixes issues 1014920 and 589083. [1] https://docs.google.com/document/d/1TMqAq4k3aTHNH1m2sYoj-5QAndNmEXLI1QeD-oQ7jWE/ Bug: 1014920, 589083 Change-Id: I089721a8736487b27c9ce019d1a389ee6521808a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2113472Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/6fead3754375..20983e35b3f9 git log 6fead3754375..20983e35b3f9 --date=short --first-parent --format='%ad %ae %s' 2020-03-24 angle-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/SwiftShader 22d73d15e778..6c11cf2ad9ca (5 commits) Created with: gclient setdep -r src/third_party/angle@20983e35b3f9 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC cnorthrop@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;luci.chromium.try:win_optional_gpu_tests_rel Bug: None Tbr: cnorthrop@google.com Change-Id: I30b485e412fdbf4c4fe25e1a7beb271408d6c869 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117488Reviewed-by:
-
Vasilii Sukhanov authored
There was an experiment running with 3 different images shown in the header in the password bubble. This CL stops the experiment and fully launches save_password2.png picture. Bug: 1016814 Change-Id: If6231326b1b8c606682d119019ca67eb45c13483 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2116174Reviewed-by:
Friedrich [CET] <fhorschig@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Commit-Queue: Vasilii Sukhanov <vasilii@chromium.org> Cr-Commit-Position: refs/heads/master@{#752782}
-
Donna Wu authored
Suspend/Resume NFC usage in browser process instead to prevent a compromised renderer from using NFC in background. TBR=kinuko@chromium.org Bug: 520391 Change-Id: I24bfc42fe95882bbfd37a12718602d96bac5fe8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2109464 Commit-Queue: Donna Wu <donna.wu@intel.com> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Reviewed-by:
Leon Han <leon.han@intel.com> Cr-Commit-Position: refs/heads/master@{#752781}
-
Koji Ishii authored
Following bot results are included. 1774 1776 1777 1778 1779 1781 1782 1784 1786 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1815 1816 1817 1818 1819 1823 36 lines were removed and 20 lines were deflaked by consecutive results since 1803. TBR=yosin@chromium.org NOTRY=true Bug: 982194 Change-Id: I2ffa2937cdf75a8f4659659fa60e06a47fc92d89 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2108271Reviewed-by:
Koji Ishii <kojii@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#752780}
-
Nohemi Fernandez authored
Add logging functionality to the upgrade sign-in operation as a part of the sign-in architecture migration. Bug: 971989 Change-Id: I2a7732b955ad563b4a8cac2d7aebdcdfedc976d9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2110650 Commit-Queue: Nohemi Fernandez <fernandex@chromium.org> Reviewed-by:
-
Christoph Schwering authored
This CL adds alt="" to the banner <img> for accessibility purposes. Bug: 1047726 Change-Id: Ib3e94edf8c1131726680e13ef61daf1dfec37ce8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2116231Reviewed-by:
-
Luciano Pacheco authored
Use ResizeObserver to observe the container parent of toolbar buttons, when it resizes, means that the buttons have moved, in this case re-position the dropdown menu to align with its button. This fixes the issue when the user clicks from the search box in a button with dropdown and the search collapses and moves the dropdown button. Bug: 1063337 Change-Id: Ia8ae426778a25ebf472631b1903b884454d8f33f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2114316 Commit-Queue: Noel Gordon <noel@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Auto-Submit: Luciano Pacheco <lucmult@chromium.org> Cr-Commit-Position: refs/heads/master@{#752777}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/6c11cf2ad9ca..3decd1af6bde git log 6c11cf2ad9ca..3decd1af6bde --date=short --first-parent --format='%ad %ae %s' 2020-03-24 bclayton@google.com Merge changes I9862d8e2,Ie1024655 Created with: gclient setdep -r src/third_party/swiftshader@3decd1af6bde If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Please CC swiftshader-team+autoroll@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: Ia1d1d8713ea7fc1308ba5fdab413e2181cd5e194 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117484Reviewed-by:
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC cr-fuchsia+bot@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast Tbr: cr-fuchsia+bot@chromium.org Change-Id: I7d1f14ca98affbe1fecbf30a6c692963987ae412 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117487Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/2b2aec6506a8..8f41598abfd6 git log 2b2aec6506a8..8f41598abfd6 --date=short --first-parent --format='%ad %ae %s' 2020-03-24 yekuang@google.com Roll out new goma client binary VERSION=196 Created with: gclient setdep -r src/third_party/depot_tools@8f41598abfd6 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Please CC agable@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Bug: None Tbr: agable@chromium.org Change-Id: Id0421ab8eb49a13949dd77f740756cd64fd24bc5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117485Reviewed-by:
-
Yuki Shiino authored
Bug: 839389 Change-Id: I87c61a9bfcc0c0b7028d8cf9016323b33dc9af29 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117670Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Cr-Commit-Position: refs/heads/master@{#752773}
-
Dominic Farolino authored
This CL puts the KeepScriptResourceAlive base::Feature under the blink::features namespace. It also adds a corresponding about:flags flag, and RuntimeEnabledFeature. ScriptLoader's behavior depends on the RuntimeEnabledFeature, which is enabled when the base::Feature is enabled. The base::Feature is enabled when the corresponding about:flags flag is enabled. These are the first steps to running experiments with the KeepScriptResourceAlive feature. A subsequent CL will add to fieldtrial_testing_conflig.json, so we can control the base::Feature via Finch. R=kinuko@chromium.org Bug: 1043679 Change-Id: Ib7cd83346c6634dad547311100a614cc43e0fce6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2112172Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Dominic Farolino <dom@chromium.org> Cr-Commit-Position: refs/heads/master@{#752772}
-
Mathias Carlen authored
R=marianfe@google.com Bug: b/151821740 Change-Id: I6d2f99159c8a59bb1a2ebb6d2123c925c0b41b41 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2116076Reviewed-by:
Clemens Arbesser <arbesser@google.com> Reviewed-by:
Marian Fechete <marianfe@google.com> Commit-Queue: Mathias Carlen <mcarlen@chromium.org> Cr-Commit-Position: refs/heads/master@{#752771}
-
Marc Treib authored
Bug: none Change-Id: Ifddb5f627e6334333e3d501e47c2d60789b8c5a3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2116210Reviewed-by:
Jan Krcal <jkrcal@chromium.org> Commit-Queue: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#752770}
-
Marc Treib authored
TestPasswordStore is an in-memory, synchronous version of the real PasswordStore. However, it only implements some subset of the full functionality. In particular, one thing that's missing is support for primary keys, which Sync uses as storage keys. Since PasswordManagerSyncTest doesn't actually need any of the convenience methods offered by TestPasswordStore, and doesn't *seem* to need the sychronicity, this CL just makes these tests use the real PasswordStore implementation. Bug: 1058339 Change-Id: I310e4979109d6175d7685808888955a5748d4193 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2115651Reviewed-by:
Mohamed Amir Yosef <mamir@chromium.org> Commit-Queue: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#752769}
-
Ewann authored
This CL creates a flag and adds cookies to the page info table view. Bug: 1063824 Change-Id: Iad99f21a072a774782d88367ceff17d10be3eed1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2115510 Commit-Queue: Ewann Pellé <ewannpv@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#752768}
-
Jiawei Shao authored
This patch adds early-returns in the request of GPUAdapter and GPUDevice when the WebGPU context is lost. In the following patches we will implement more clean-ups when the WebGPU context is lost. BUG=chromium:996713 Change-Id: I1e6e4723596ed63c8ab7f9200be41dde68b8815e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2112333 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by:
Corentin Wallez <cwallez@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Reviewed-by:
Austin Eng <enga@chromium.org> Reviewed-by:
Kai Ninomiya <kainino@chromium.org> Cr-Commit-Position: refs/heads/master@{#752767}
-
Adam Rice authored
Implement the IncomingStream mixin and ReceiveStream interface that are part of WebTransport. Also implement the receiveStreams() method on QuicTransport. Bug: 1011392 Change-Id: Id6aebc5b49c41dde77458ac4ed99d73bd3331f35 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2094492 Commit-Queue: Adam Rice <ricea@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#752766}
-
Takashi Toyoshima authored
Since it does not seem the marked test is failing recently, let's remove the flaky mark and see how it goes. NOTRY=true Bug: 836242 Change-Id: I6d70b09fe0aff8f86521887619e158e0d01c4d02 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2115130 Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Auto-Submit: Takashi Toyoshima <toyoshim@chromium.org> Cr-Commit-Position: refs/heads/master@{#752765}
-
Luciano Pacheco authored
Bug: 1063337 Change-Id: Ib33c349710aaeb5257027233777bd62b37998834 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2117557 Commit-Queue: Noel Gordon <noel@chromium.org> Reviewed-by:
-
