- 03 Dec, 2020 40 commits
-
-
Harry Cutts authored
Bug: none Test: remove deep-link-focus-id from HTML elements and check tests fail Change-Id: Ie3d4bb5fc58a628c6bf34e21ca624fe0eb39d761 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2551462 Commit-Queue: Harry Cutts <hcutts@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#833123}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/8797714c4a78..abe9657839a4 2020-12-02 syoussefi@chromium.org Vulkan: I/O blocks: Support unsized arrays 2020-12-02 jonahr@google.com Reland "Reinitialize GL_VENDOR string when GPU switches" 2020-12-02 syoussefi@chromium.org Vulkan: Clean up render pass query code 2020-12-02 syoussefi@chromium.org Create helper for identifying builtin names 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 ianelliott@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/+doc/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;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: chromium:1152212 Tbr: ianelliott@google.com Change-Id: Ib96a7c85e6558a1d789160d39ec055ca80a937ce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570167Reviewed-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@{#833122}
-
Yury Khmel authored
https://chromium.googlesource.com/chromiumos/platform2/system_api.git/+log/f6d74c196c6c..7fa43c97b606 $ git log f6d74c196..7fa43c97b --date=short --no-merges --format='%ad %ae %s' 2020-12-02 paulhsia system_api: Add NumberOfInputStreamsWithPermission related constants 2020-11-18 yichengli u2fd: Don't reset pending WebAuthn sessions twice 2020-12-02 garrick system_api: Add fields to ConnectNamespace 2020-10-29 ejcaruso shill: enable IPv6 per APN in mobile operator DB 2020-12-01 dlunev cryptohome: remove now unused UpdateEx call 2020-12-01 garrick system_api: Add network device change signal 2020-11-30 garrick patchpanel: Add support for getting all managed devices. 2020-11-30 garrick patchpanel: Add guest enum type for net device. 2020-11-11 hardikgoyal cryptohome: add AuthSession API in DBUS 2020-12-01 khmel system_api: Add API to pass ARC dalvik memory profile type. Created with: roll-dep src/third_party/cros_system_api BUG=b:160760318 TEST=N/A Change-Id: Ie88b840c598aa0dc85be4416f253b6a70b9b854e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570102 Auto-Submit: Yury Khmel <khmel@google.com> Commit-Queue: Yusuke Sato <yusukes@chromium.org> Reviewed-by:
Yusuke Sato <yusukes@chromium.org> Cr-Commit-Position: refs/heads/master@{#833121}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/1366dd01174e..ae504d46b4c4 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-win-chromium 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/+doc/master/autoroll/README.md Tbr: perfetto-bugs@google.com Change-Id: I257b807860c85f5f26eb76e10d35bdd381e38ebb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570046Reviewed-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@{#833120}
-
chromium-autoroll authored
Roll Chrome Linux PGO profile from chrome-linux-master-1606931953-8f73b2aa50fd158baa3a07c3a6f9cf4c6333162b.profdata to chrome-linux-master-1606953494-bd74c7c56f61c746e2347181ab9ffd8bac2372a6.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-linux-chromium Please CC pgo-profile-sheriffs@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I6f2d13a5a39878853940daf2f2f4218a9b6d062b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570407Reviewed-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@{#833119}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/5334e8976d42..c7112edbe0f4 2020-12-03 bsalomon@google.com Fix swizzles in clear_swizzle GM If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC westont@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Cq-Do-Not-Cancel-Tryjobs: true Bug: None Tbr: westont@google.com Change-Id: I7f9bce263c8090e216bc066b0f6585f418344be3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570536Reviewed-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@{#833118}
-
Findit authored
This reverts commit 5a3ffeb6. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 833103 as the culprit for failures in the build cycles as shown on: https://analysis.chromium.org/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtLzVhM2ZmZWI2ZjQxMzMwNGYyNjFlMzA1OTQwN2MzMzFlMmJhNDdhYmEM Sample Failed Build: https://ci.chromium.org/b/8861972214722070416 Sample Failed Step: compile Original change's description: > media/gpu/video_encode_accelerator_tests: Validates each temporal layer stream > > The test originally validates the entire bitstream. This CL > enables the test to validate each temporal layer stream. For > instance, when --num_temporal_layers=3, the test validates three > streams, TL0, TL0+TL1 and TL0+TL1+TL2. > BitstreamFileWriter and VideoFrameFileWriter ignore bitstreams > and frames in upper layers than to be processed by them. > VideoFrameFileWriter also writes a file with a different prefix > from other VideoFrameFileWriter, so that multiple instances don't > write to the same file names. > > Bug: b:174318867 > Test: video_encode_accelerator_tests --codec=vp9 --num_temporal_layers=3 w/o output_bitstream --output_images=all > Change-Id: Idf2a1e4d2a50e11ca359435ec4495a43b61139f9 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2562801 > Reviewed-by: David Staessens <dstaessens@chromium.org> > Commit-Queue: Hirokazu Honda <hiroh@chromium.org> > Cr-Commit-Position: refs/heads/master@{#833103} Change-Id: I1f9e32ad418487d948efe7b010750e457f2b39c5 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: b:174318867 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570340 Cr-Commit-Position: refs/heads/master@{#833117}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/b6e840c0368f..6e7167456b5e 2020-12-02 sprang@webrtc.org Adds experimental libvpx VP9 speed settings. 2020-12-02 landrey@webrtc.org Set default max_threads_count to DVQA injection helper 2020-12-02 landrey@webrtc.org Fix DVQA cpu usage when Stop is called multiple times 2020-12-02 landrey@webrtc.org Revert "Ignore frames that are comming to DVQA after Stop is called" If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@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/+doc/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I5a69590e02e6879cf4f521ffac0bc2a755b56aa6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570228Reviewed-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@{#833116}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1606931953-e0ca281e08d569bf1b7a3d019134ab44a9fae467.profdata to chrome-mac-master-1606953494-1095cc05af875eadbe87fc6109d3867a4076cbf5.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-mac-chromium Please CC pgo-profile-sheriffs@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:mac-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I191f061566716eabadde2f618f2ad6587f7ff8cb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570506Reviewed-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@{#833115}
-
David Van Cleve authored
The HTML meta tag allows one to set a document's referrer policy by providing values to <meta rel=referrer content={referrer policy here}> In addition to all of the referrer policy identifiers (unsafe-url, no-referrer-when-downgrade, etc), the HTML spec allows a few legacy values for the "content" attribute: "never" is treated as if it instead read "no-referrer", "always" as "unsafe-url", "origin-when-crossorigin" as "origin-when-cross-origin", and "default" as "no-referrer-when-downgrade". This CL incorporates a behavior change proposed in a new spec pull request https://github.com/whatwg/html/pull/5783, which updates the "default" meta tag keyword to, instead of being statically mapped to no-referrer-when-downgrade", cross-reference the actual default policy value. It also adds test coverage for all of the legacy keywords by adding new test cases to wpt/referrer-policy/spec.src.json; the referrer policy WPTs didn't previously cover this behavior. Additionally, the CL removes a few now-redundant Blink web tests covering the behavior that WPTs now verify. This change is web-visible, but I think it's arguably covered by the recently shipped change updating the default referrer policy from its previous value of no-referrer-when-downgrade to a new value of strict-origin-when-cross-origin. [1] At the time the <meta> behavior was originally written into the spec, there wasn't an explicit single source of truth for the "default referrer policy" per se: instead, specs (Fetch, HTML, and the WebAppSec Referrer Policy spec) individually defined fallback behavior in "no policy specified" cases by referring specifically to the "no-referrer-when-downgrade" policy value. [1]: https://groups.google.com/a/chromium.org/g/blink-dev/c/lqFuqwZDDR8/m/nKPRTc7DAQAJ Fixed: 1154350 Change-Id: Ifb3bf9aa9f773c64af1a6e79f39511cf1c1bd8fa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567977Reviewed-by:
Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Commit-Queue: David Van Cleve <davidvc@chromium.org> Cr-Commit-Position: refs/heads/master@{#833114}
-
Alex Ilin authored
Change-Id: Ie26fda72af2d7c5d675619c43fa453f9d045e177 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568282 Auto-Submit: Alex Ilin <alexilin@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Commit-Queue: Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#833113}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/70828422634e..4640dfbfd719 2020-12-03 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). 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 ajp@google.com,apolito@google.com,ehmaldonado@google.com,sokcevic@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/+doc/master/autoroll/README.md Bug: None Tbr: ajp@google.com,apolito@google.com,ehmaldonado@google.com,sokcevic@google.com Change-Id: I7cefb41328fcfba92b0dd4be421d547a5ab52432 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570507Reviewed-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@{#833112}
-
Kenichi Ishibashi authored
Mojofying service worker storage operations introduced some test flakiness. A summary of the cause is: - These tests uses browser contexts and browser contexts initialize storage partition. - Storage partition initialization schedules some tasks which call service worker storage operations but don't wait for results. - Mojo generated bindings for storage operations have DCHECKs to make sure callbacks of these calls are executed before destroying mojo connections. - These DCHECKs fail because tasks don't wait for results. This CL runs pending tasks in ProxyRunTestOnMainThreadLoop() as suggested in [1]. [1] https://chromium-review.googlesource.com/c/chromium/src/+/2561963/comment/e878eb61_e0080fca/ Bug: 1153911, 1133143 Change-Id: Ie930f5ce0aa809e45877127988b99ec603cdcfd5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567010Reviewed-by:
Gabriel Charette <gab@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Cr-Commit-Position: refs/heads/master@{#833111}
-
Matthias Körber authored
Change-Id: I1f3f102bd03d2fa60bf5195403a00e39fc6f3125 Bug: 1007974 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2566949 Commit-Queue: Matthias Körber <koerber@google.com> Commit-Queue: Christoph Schwering <schwering@google.com> Reviewed-by:
Christoph Schwering <schwering@google.com> Cr-Commit-Position: refs/heads/master@{#833110}
-
Zhenyao Mo authored
This is definitely needed until we ship vsync reduction on Windows. BUG=1152036 TEST=none Change-Id: Iab95280deff8029faaa5742d29f57739d10a6f29 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570088 Auto-Submit: Zhenyao Mo <zmo@chromium.org> Commit-Queue: Ilya Sherman <isherman@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#833109}
-
Yann Dago authored
Bug: 1149461 Change-Id: I15ab9cc3c2db147e2dd9222840a5fc8752dc50fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2562229 Commit-Queue: Yann Dago <ydago@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Reviewed-by:
Greg Thompson <grt@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#833108}
-
Gyuyoung Kim authored
This CL converts AwViewMsg_DocumentHasImages and AwViewMsg_DocumentHasImagesResponse to android_webview's LocalMainFrame interface. The response IPC message was handled by reply callback. Bug: 1146492 Change-Id: I03248da153c230e7850d4728bdfd844cd54ca6b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2563015 Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com> Reviewed-by:
Bo <boliu@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Cr-Commit-Position: refs/heads/master@{#833107}
-
Matt Menke authored
I'm working on gettings things like 127.0.0.0.1, foo.0.1, and, potentially, foo.1 rejected at the GURL level. This CL updates a couple tests in advance of that so as to rely on URLs with hostnames like these being considered valid. Bug: 1143453 Change-Id: Iae326c3d5df58b6350fd0b89320f7bf64de9e1e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2565196Reviewed-by:
Eric Orth <ericorth@chromium.org> Reviewed-by:
Xinghui Lu <xinghuilu@chromium.org> Reviewed-by:
mark a. foltz <mfoltz@chromium.org> Commit-Queue: Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#833106}
-
Yuichiro Hanada authored
The proxy IME in Android sometimes fail to find the appropriate KeyboardCode for a Android's KEYCODE. The proxy IME uses ui::VKEY_UNKNOWN for the key event. However, it's rejected in a validation code and the mojo connection is closed as a result. This CL adds a new optional field in KeyEventData struct for a scan code of a key event. The field will be used when the proxy IME fails to find the appropriate KeyboardCode. Bug: b:174259561 Test: component_unittests Change-Id: If4cf5514bdb6cc7026964025e42e4ae6bc3e57b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567141 Commit-Queue: Yuichiro Hanada <yhanada@chromium.org> Reviewed-by:
Jorge Lucangeli Obes <jorgelo@chromium.org> Reviewed-by:
Tetsui Ohkubo <tetsui@chromium.org> Cr-Commit-Position: refs/heads/master@{#833105}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/95ffe036632c..bae138de13ac 2020-12-02 amaiorano@google.com Reactor: add Type* member to Value and remove vtable 2020-12-02 amaiorano@google.com Fix crash from rr::Array with ENABLE_RR_DEBUG_INFO enabled 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/+doc/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;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: I6d20539afa18cd98bd20ca191d95da3bd75143cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570224Reviewed-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@{#833104}
-
Hirokazu Honda authored
The test originally validates the entire bitstream. This CL enables the test to validate each temporal layer stream. For instance, when --num_temporal_layers=3, the test validates three streams, TL0, TL0+TL1 and TL0+TL1+TL2. BitstreamFileWriter and VideoFrameFileWriter ignore bitstreams and frames in upper layers than to be processed by them. VideoFrameFileWriter also writes a file with a different prefix from other VideoFrameFileWriter, so that multiple instances don't write to the same file names. Bug: b:174318867 Test: video_encode_accelerator_tests --codec=vp9 --num_temporal_layers=3 w/o output_bitstream --output_images=all Change-Id: Idf2a1e4d2a50e11ca359435ec4495a43b61139f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2562801Reviewed-by:
David Staessens <dstaessens@chromium.org> Commit-Queue: Hirokazu Honda <hiroh@chromium.org> Cr-Commit-Position: refs/heads/master@{#833103}
-
Dmitry Torokhov authored
This reverts commit a96ef56c. Reason for revert: Parallels have upgraded to QT 5.15 hence the workaround is no longer needed. Original change's description: > exo: temporarily clamp display scale factor to 2 > > Version of QT currently in use by Parallels Desktop does not render > correctly when display scale factor is above 2, so let's use 2 as the > upper bound until they switch to a newer version of QT (5.15 should > have the fix). > > Bug: b/169984627 > Change-Id: Idd31b9a737833fa48ab6b20ae8da5f1bf951b3ff > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2446720 > Commit-Queue: Dmitry Torokhov <dtor@chromium.org> > Reviewed-by: Mitsuru Oshima <oshima@chromium.org> > Cr-Commit-Position: refs/heads/master@{#816020} TBR=oshima@chromium.org,dtor@chromium.org,edcourtney@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: b/169984627 Bug: 1137268 Change-Id: Iba38d0df84c87ed7ade2986704f9d29d5ec75f78 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570309Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Commit-Queue: Dmitry Torokhov <dtor@chromium.org> Cr-Commit-Position: refs/heads/master@{#833102}
-
Xianzhu Wang authored
This CL avoids the problem by - Disabling compositing of SVG child for will-change:top etc. which don't apply. - Including CompositingReason::kSVGRoot on the effect node (if exists) on SVG root to prevent the effect node from being decomposited during PaintArtifactCompositor::Update(), to ensure the composited layer for SVG root will create a render surface when needed. We still need to create a better solution for this (tracked by crbug.com/1154097). Because CompositingReason::kSVGRoot is for pre-CompositeAfterPaint CompositeSVG only to create a GraphicsLayer with ShouldCreateLayersAfterPaint, this CL also disable the logic for CompositeAfterPaint. Bug: 1152691 Change-Id: Ic194501698c0afd5a058647344f812077ed07709 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567614 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
Stefan Zager <szager@chromium.org> Cr-Commit-Position: refs/heads/master@{#833101}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/252a9ed0..5b8d12f1 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: Iab08c3038c25cd5e9f3e92c0ea1eb16e8ab20662 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570330Reviewed-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@{#833100}
-
Brandon Jones authored
Changes the function to accept a GPUAdapter instead of a GPUDevice and return a GPUTextureFormat synchronously rather than via a Promise. The previous function signature is left in place with a deprecation warning. Bug: 1154326 Change-Id: I0593d04933b5bf6d91c6428239fd04a32170210b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2566885Reviewed-by:
Kai Ninomiya <kainino@chromium.org> Reviewed-by:
Corentin Wallez <cwallez@chromium.org> Commit-Queue: Brandon Jones <bajones@chromium.org> Cr-Commit-Position: refs/heads/master@{#833099}
-
Melissa Zhang authored
This CL refactors sharesheet_service_delegate to be identified by its native_window. This is so that we can ensure only one sharesheet for any one native_window at any time. Bug: 1142706 Change-Id: I7892bb5b95f6ab4fa17c772e173084b11e3ab69f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2563010Reviewed-by:
Dominick Ng <dominickn@chromium.org> Commit-Queue: Melissa Zhang <melzhang@chromium.org> Cr-Commit-Position: refs/heads/master@{#833098}
-
Mitsuru Oshima authored
instead of new layer. This will be used to address performance related issue. Bug: None Test: covered by unittest Change-Id: I3b6b0bfdd8ab4fb11b21fd7b84f677169023bfe9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2560549 Commit-Queue: Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Sammie Quon <sammiequon@chromium.org> Cr-Commit-Position: refs/heads/master@{#833097}
-
Adam Langley authored
This #include pulls in quite a lot of headers in render_frame_host.h, a fairly core header. Change-Id: I17288f2e166ec15880ebac6a11f07c574b16d94b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2553021 Commit-Queue: Adam Langley <agl@chromium.org> Commit-Queue: Avi Drissman <avi@chromium.org> Auto-Submit: Adam Langley <agl@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#833096}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/40894189c86a..5334e8976d42 2020-12-02 mtklein@google.com Revert "restore murmur3 for older iOS devices" 2020-12-02 scroggo@google.com Expose more info in SkCodec::FrameInfo 2020-12-02 mtklein@google.com simplify SkSamplingOptions field names 2020-12-02 mtklein@google.com make SkSamplingOptions fields const 2020-12-02 bsalomon@google.com GPU clear values: just 4 floats 2020-12-02 tdenniston@google.com Add test for quadratic Wang's formula 2020-12-02 mtklein@google.com restore murmur3 for older iOS devices 2020-12-02 johnstiles@google.com Fix flipped array dimensions in SkSL. 2020-12-02 bungeman@google.com Subpixel anti-aliasing in FreeType 2.8.1+ 2020-12-02 robertphillips@google.com Revert "Fix bug in GrClearOp combining and remove some asserts" 2020-12-02 johnstiles@google.com Disable inliner on Functions.sksl. 2020-12-02 brianosman@google.com Remove unused inColor If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC westont@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Cq-Do-Not-Cancel-Tryjobs: true Bug: None Tbr: westont@google.com Change-Id: I2956ee5cbf737f00587f8c4a022b476af3377e90 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569516Reviewed-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@{#833095}
-
Krishna Govind authored
TBR=benmason@chromium.org Change-Id: Ia1e0e2402789f0922099353b45edfe6e256596aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569388Reviewed-by:
Krishna Govind <govind@chromium.org> Commit-Queue: Krishna Govind <govind@chromium.org> Cr-Commit-Position: refs/heads/master@{#833094}
-
Zach Trudo authored
RecordHandlerImpl replaces Destination specific handlers with a handler that points directly to the new endpoint. Bug: chromium:1078512 Change-Id: I8dd7ceca2556ad032f2e398cde1987fa4100b016 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2555200 Commit-Queue: Zach Trudo <zatrudo@google.com> Reviewed-by:
Leonid Baraz <lbaraz@chromium.org> Cr-Commit-Position: refs/heads/master@{#833093}
-
Thanh Nguyen authored
Add new function to utility/services.cc that allows us to launch LocalSearchService out of process. Design doc: go/lss-sandboxing Implementation plan: go/lss-sandboxing-impl Bug: 1137560 Change-Id: I921281b6a309f8ffa66a3cd0e4f1e5119a824ec9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2562806Reviewed-by:
Ted Choc <tedchoc@chromium.org> Reviewed-by:
Jia Meng <jiameng@chromium.org> Reviewed-by:
Sam McNally <sammc@chromium.org> Commit-Queue: Thanh Nguyen <thanhdng@chromium.org> Cr-Commit-Position: refs/heads/master@{#833092}
-
Yao Xiao authored
Bug: 1154556 Change-Id: Ib4d6bbb1f94fac80823b729b963f36becd1f3792 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568939 Commit-Queue: Yao Xiao <yaoxia@chromium.org> Reviewed-by:
Josh Karlin <jkarlin@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#833091}
-
Asanka Herath authored
We are making a corresponding change to the server controlled experiment. This change brings the waterfall tests closer in character to what is in the field. Bug: 1154693 Change-Id: I47ec85a18c195b878ee1b0bc074c99417951a000 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568624 Commit-Queue: Asanka Herath <asanka@chromium.org> Reviewed-by:
Caitlin Fischer <caitlinfischer@google.com> Cr-Commit-Position: refs/heads/master@{#833090}
-
Noel Gordon authored
Due to issue 1152084 some users might have incorrectly EXIF orientated JPEG thumbnails in their image loader cache. Update the image loader's IDB cache version to reset (aka clear) the users image loader cache. Bug: 1152084 Change-Id: I3fee9a406c10cca435227418310379cda4b25fac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569194Reviewed-by:
Alex Danilo <adanilo@chromium.org> Commit-Queue: Alex Danilo <adanilo@chromium.org> Auto-Submit: Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#833089}
-
Brian Sheedy authored
The Windows Intel pool has had a mix of HD and UHD 630 GPUs for a while now, so there's no need to specifically test UHD 630 GPUs anymore. Bug: 1154460 Change-Id: I27d43dc6c74dd332fe7575743bb17007cb30617c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570124 Commit-Queue: Yuly Novikov <ynovikov@chromium.org> Auto-Submit: Brian Sheedy <bsheedy@chromium.org> Reviewed-by:
Yuly Novikov <ynovikov@chromium.org> Cr-Commit-Position: refs/heads/master@{#833088}
-
Brian Sheedy authored
We already have stable tests running on RX 5500 XTs with more capacity, so no reason to keep the old AMD builder around. Bug: 1154895 Change-Id: Idd16c259e8c74903b8def0289155444ebef85a91 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570387 Auto-Submit: Brian Sheedy <bsheedy@chromium.org> Reviewed-by:
Yuly Novikov <ynovikov@chromium.org> Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#833087}
-
David Trainor authored
This reverts commit dde99fda. Reason for revert: Reliably failing due to timeout on android-marshmallow-x86-rel-non-cq. Sample failure: https://ci.chromium.org/ui/p/chromium/builders/ci/android-marshmallow-x86-rel-non-cq/1034/overview Original change's description: > [remoteobjects] Add JavaBridgeBasicsTest#testWebViewAfterRenderViewSwapped > > This CL adds JavaBridgeBasicsTest#testWebViewAfterRenderViewSwapped > to recreate the regression scenario described in > https://crbug.com/572053, and to verify that the new code works as > expected. > > Bug: 1105935 > Change-Id: Ie527f0c452a9d3eac7fe0c91797b792eff15c23d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2564931 > Reviewed-by: Bo <boliu@chromium.org> > Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org> > Commit-Queue: Miyoung Shin <myid.shin@igalia.com> > Cr-Commit-Position: refs/heads/master@{#832636} TBR=boliu@chromium.org,oksamyt@chromium.org,myid.shin@igalia.com,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com Change-Id: Id346701be025b4b61e8eae07442a902c5c009bd0 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1105935 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570449Reviewed-by:
David Trainor <dtrainor@chromium.org> Commit-Queue: David Trainor <dtrainor@chromium.org> Cr-Commit-Position: refs/heads/master@{#833086}
-
Bao-Duy Tran authored
This script is used for on-the-fly autogen of C++ code from legacy input_methods.txt [1] config file that's mostly obsolete and on track for full deprecation. This cleanup is in prep for trimming the script to just what's still really in use nowadays from input_methods.txt. [1] https://source.chromium.org/chromium/chromium/src/+/master:chromeos/ime/input_methods.txt;drc=5ab33d25bc676b63e4afbcfade6f9265a5f5a3ea Bug: 1134526,1134465 Change-Id: Id8b235958deaee0f2d935f8e384af9c4e0cc19c7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568923Reviewed-by:
Yuichiro Hanada <yhanada@chromium.org> Reviewed-by:
Darren Shen <shend@chromium.org> Reviewed-by:
My Nguyen <myy@chromium.org> Commit-Queue: Bao-Duy Tran <tranbaoduy@chromium.org> Cr-Commit-Position: refs/heads/master@{#833085}
-
Victor Costan authored
//tools/mb/mb_config_expectations/tryserver.chromium.mac.json was updated by running "tools/mb/mb.py train" //infra/config/generated/* was updated by running "lucicfg generate infra/config/main.star" Bug: 1154062 Change-Id: I13a9e0bb1dd2a7f3ccdaf30fa600de4cedafa92c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2566335Reviewed-by:
Stephen Martinis <martiniss@chromium.org> Commit-Queue: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#833084}
-