- 19 Jan, 2021 40 commits
-
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/cf567b6b9616..5eda7597b6b7 2021-01-19 dberris@chromium.org Reland "chromeperf: Anomaly configs in subscriptions" If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/catapult-autoroll Please CC skyostil@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:chromeos-kevin-rel;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: chromium:1158326 Tbr: skyostil@google.com Change-Id: I91a4e19a9636d5dd2aba469ef2d928f4c45b17dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636267Reviewed-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@{#844675}
-
Maggie Cai authored
This reverts commit 21a8ee36. Reason for revert: This CL is likely the culprit for the failure of tests: AssistantTimersBrowserTest.ShouldRemoveTimerWhenStoppingViaNotification AssistantTimersBrowserTest.ShouldTickNotificationsAtRegularIntervals on builder linux-chromeos-chrome First occurance: https://ci.chromium.org/p/chrome/builders/ci/linux-chromeos-chrome/11466 Original change's description: > views-posse: Add metadata to notification_view_md > > Bug: 1159562 > Test: build > Change-Id: I5cd5b56c5ef11899bdac3122ed1525a24bbf6fa5 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2615725 > Reviewed-by: Yoshiki Iguchi <yoshiki@chromium.org> > Reviewed-by: Allen Bauer <kylixrd@chromium.org> > Commit-Queue: Sara Kato <sarakato@chromium.org> > Cr-Commit-Position: refs/heads/master@{#844496} TBR=yoshiki@chromium.org,kylixrd@chromium.org,sarakato@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com Change-Id: I3fe76cb2391afb9ef454f3e3fb8d8c44c6753013 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1159562 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636737Reviewed-by:
Maggie Cai <mxcai@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Maggie Cai <mxcai@chromium.org> Cr-Commit-Position: refs/heads/master@{#844674}
-
Tal Pressman authored
Change-Id: If5bc40ac15f246c8419a2ad92dcd06346ae62d12 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633488Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Tal Pressman <talp@google.com> Cr-Commit-Position: refs/heads/master@{#844673}
-
Kenton Lam authored
This will help as we add more events for additional functionality. Particular flags need to be set for all CustomEvent's so they bubble up through the Polymer components. Change-Id: I11e909b7a6afc6bc9433392e1fbb160156cdf10e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636077 Commit-Queue: Kenton Lam <kentonlam@google.com> Reviewed-by:
Keith Lee <keithlee@chromium.org> Reviewed-by:
John Palmer <jopalmer@chromium.org> Cr-Commit-Position: refs/heads/master@{#844672}
-
Dominik Röttsches authored
After moving OTS to a DEPS-based checkout in [1] but keeping it at the same commit position, now roll OTS forward to upstream tip-of-tree. Update baselines to reflect that OTS changed the wording of some error messages. [1] https://chromium-review.googlesource.com/c/chromium/src/+/2589853 Bug: 1158389 Binary-Size: OTS has not been rolled in a long time and is a required component to protect against malicious web fonts and to avoid bugs in the system font stack. Change-Id: I5999049091f6c4472a0613d5fb5b284929e7702d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2635654 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#844671}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/5635dbb91641..81430e11c81e 2021-01-19 jmadill@chromium.org Vulkan: Remove command processor special functions. 2021-01-18 penghuang@chromium.org Support create ANGLE EGLContext from an external EGLContext 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/+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: None Tbr: cnorthrop@google.com Change-Id: I7151178c817f802ba66f240de9e84fa0ca6f8a73 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636299Reviewed-by:
-
Fergal Daly authored
This test is slow on debug builds in general but on Mac and Win it's slow enough to cause timeout flakes. FIX: Set the entry-count limit to 10. This test takes 15s on my desktop before this change and 6 afterwards, so the build bots should be OK. Bug: 1167300 Change-Id: Iaf3cf63aed26dc0a79a02cb6b2af6ecada30303f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636633Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Fergal Daly <fergal@chromium.org> Cr-Commit-Position: refs/heads/master@{#844669}
-
Yann Dago authored
This fixes the fact that the wrong data was sent to the histogram "Sync.Startup.PolicyLoadTimeout" and uses a new histogram named "Sync.Startup.PolicyLoadTimeout2" to avoid using the wrong data. Bug: 1129065 Change-Id: Iaa42e0ede6348f130a8e1e09ea35c2989aaff955 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2629574 Commit-Queue: Yann Dago <ydago@chromium.org> Reviewed-by:
Caitlin Fischer <caitlinfischer@google.com> Reviewed-by:
Marc Treib <treib@chromium.org> Auto-Submit: Yann Dago <ydago@chromium.org> Cr-Commit-Position: refs/heads/master@{#844668}
-
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 chrome-fuchsia-gardener@grotations.appspotmail.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:fuchsia-arm64-cast;luci.chromium.try:fuchsia-deterministic-dbg;luci.chromium.try:fuchsia-x64-cast Tbr: chrome-fuchsia-gardener@grotations.appspotmail.com Change-Id: I2d8e726c97ed232fbf35df7b10162f99409cf6bb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636505Reviewed-by:
-
Alan Cutter authored
This CL fixes middle clicks on links inside a link capturing web app scope from crashing. These were crashing due to the expectation that the navigating tab was already attached to a browser window (which is incorrect during the navigation throttle) causing a nullptr crash. We should not be link capturing these navigations so this CL checks for and early exits in these cases. Bug: 1159666 Change-Id: I9dae80d84a44e8bf2fa9918ece8fee6d19af2ee2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636009 Commit-Queue: Alan Cutter <alancutter@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/f2a99e868d8f..c1912a4fbb17 2021-01-19 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.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: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Iace1a91741c4cb02f97ef91e24420ee978760512 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636266Reviewed-by:
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1611003391-f38d26b13046eb21865bd4aef763cfd6c815875c.profdata to chrome-win64-master-1611013939-db0b1e97bc691be6bf78d3a336cf34d826bfa98b.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-win64-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:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I4400c7dd961d394fe1a6949ab7a530f1f693350d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636508Reviewed-by:
-
Hui Yingst authored
For a XYZ fit type named destination, if the x or y coordinate is null, that specific coordinate of the current viewport should be retained (See table 151 in ISO 32000-1 for more details.). Also, one null parameter does not invalidate other parameters, all parameters should be handled independently. Currently, the PDF viewer ignores both the x and y coordinates if either one of them is null, and it always resets the viewport position to (0,0) (top-left corner) without retaining the current coordinate which receives a null input. This CL does the following changes to fix this issue: - Makes PDFiumPage::GetPageDestinationTarget() return x and y coordinates separately, so that each null input can be handled individually as an undefined value. - Introduces retrieveCurrentScreenCoordinates() to calculate the current in-screen coordinates of the viewport, so that goToPageAndXY() can use its return value to retain x/y coordinate while navigating to a new destination. Bug: 1163701,1157061 Change-Id: I4a4e8f1e193aab8ad2d5c8f3a277d0892e3e72c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632325Reviewed-by:
dsinclair <dsinclair@chromium.org> Commit-Queue: Hui Yingst <nigi@chromium.org> Cr-Commit-Position: refs/heads/master@{#844663}
-
Ye Kuang authored
Bug: 1141780 Change-Id: I0eac786673ac31f68128059d627d7156c6a8d653 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631894Reviewed-by:
Takuto Ikuta <tikuta@chromium.org> Reviewed-by:
Fumitoshi Ukai <ukai@google.com> Reviewed-by:
Yoshisato Yanagisawa <yyanagisawa@google.com> Commit-Queue: Ye Kuang <yekuang@google.com> Cr-Commit-Position: refs/heads/master@{#844662}
-
chromium-autoroll authored
Roll ChromeOS Orderfiles from 89-4380.0-1610362181-benchmark-89.0.4387.0-r1 to 89-4380.0-1610362181-benchmark-89.0.4389.4-r1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/cros-orderfile-chromium Please CC c-compiler-chrome@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: c-compiler-chrome@google.com Change-Id: I087561bf4471f7e924d3ddbc7f40090127b52a1d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636753Reviewed-by:
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=pbommana@chromium.org Change-Id: Idb6f4477661f20d91cfcdbab48bda80dd3c6f3a3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636773Reviewed-by:
Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#844660}
-
Xianzhu Wang authored
This ensures that cc will rasterize the animating layer at the maximum scale, to avoid 1. blurriness during scaling-up animations (e.g. scale 1 -> 3), 2. too big raster scale (wasting memory) during small scale animations (e.g. scale 0.1 -> 0.3). Previously in the above cases, in simple cases (without ancestor scales), scale 1 for the layer was used for raterization because ui::TransformAnimationCurveAdapter failed to provide the maximum scale of animations. Also remove unused ui::InverseTransformCurveAdapter. Bug: 1161586 Change-Id: Ieb876bc271c98627bd61370c93e806b44be0b868 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2605242 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
Robert Flack <flackr@chromium.org> Cr-Commit-Position: refs/heads/master@{#844659}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/13466d016b58..84e43fa2c447 2021-01-19 tikuta@chromium.org ninjalog uploader: migrate to python3 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 ehmaldonado@google.com,sokcevic@google.com,ajp@google.com,apolito@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: ehmaldonado@google.com,sokcevic@google.com,ajp@google.com,apolito@google.com Change-Id: I472e79748ba8fd8beeb74b26830ba66e25e3c10d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636298Reviewed-by:
-
tby authored
We've changed the proto field used to record structured metrics, this CL changes the metrics provider from using deprecated_structured_event to using structured_data.events. Bug: 1148168 Change-Id: I9b987c2e24886ee72b2f404dcd713981674cc194 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636079Reviewed-by:
Rachel Wong <wrong@chromium.org> Commit-Queue: Tony Yeoman <tby@chromium.org> Cr-Commit-Position: refs/heads/master@{#844657}
-
Kyle Williams authored
Move the various GetCurrentFormFactor functions to the VariationsServiceClient class. BUG=b:177442621 TEST=autoninja -C out/Default/ components:components_unittests && xvfb-run ./out/Default/components_unittests --gtest_filter=FieldTrialUtilTest.* Change-Id: Ib677ed6cfbba91a287cb5c9ef06cf96332e4be3f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633426 Auto-Submit: Kyle Williams <kdgwill@chromium.org> Commit-Queue: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#844656}
-
Song Fangzhen authored
Reject hostnames that resolve to non-public exception unless a raw IP address or a *.local hostname is entered by the user. TODO: Show connection dialog and use the hostname provided by the user. Below documents are from Eric Willigers <ericwilligers@chromium.org>. Explainer: https://github.com/WICG/raw-sockets/blob/master/docs/explainer.md Design doc: https://docs.google.com/document/d/1Xa5nFkIWxkL3hZHvDYWPhT8sZvNeFpCUKNuqIwZHxnE/edit?usp=sharing Bug: 1119661 Change-Id: I9a1300adf8b4acef2fbc2f18c465f86bc11b3859 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631664 Commit-Queue: Eric Willigers <ericwilligers@chromium.org> Reviewed-by:
Glen Robertson <glenrob@chromium.org> Reviewed-by:
Eric Willigers <ericwilligers@chromium.org> Cr-Commit-Position: refs/heads/master@{#844655}
-
Minggang Wang authored
The functions declared in ip_address_space_util.h are needed when moving WebURLLoaderImpl into blink. So, as part of the OnionSoup project, this patch moves the functions to third_party/blink/public/common/net/ and its unit test accordingly. Bug: 1110176 Change-Id: I9a9b7056d6e822eaf39a1f21a8c5fb35379d5ffb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2635217Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Commit-Queue: Minggang Wang <minggang.wang@intel.com> Cr-Commit-Position: refs/heads/master@{#844654}
-
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/goldctl-mac-chromium-autoroll Please CC bsheedy@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/+doc/master/autoroll/README.md Bug: None Tbr: bsheedy@chromium.org Change-Id: I4922c164ada4ac7b75873c1919098eabd48e2ea4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636500Reviewed-by:
-
Rakina Zata Amni authored
Currently we have a per-request buffer limit, but we're seeing some OOM regressions, presumably because we have a lot of small requests that when summed up takes a lot of memory. This CL adds a per-process buffer limit to ensure we can control how much memory buffered network requests in a renderer process can take while in bfcache and hopefully reduce the OOM rate. Bug: 1137682 Change-Id: I7685dab83e3502d7169949acf4b123a2c66a47b5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631388 Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Reviewed-by:
Alexander Timin <altimin@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
-
chromium-autoroll authored
Roll Chrome Win32 PGO profile from chrome-win32-master-1610992290-682e9bbbdeeb2e8d01a84d67f327a574b1495751.profdata to chrome-win32-master-1611003391-e5257fde85260089be74668a059af9daef590c17.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-win32-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:win-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: Ib3e41fd58164d0060b263ea0c32fc11bbba5d72b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632782Reviewed-by:
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1610992290-93f2acc9d0a77f7b507d260e7f325f3b3b6e6de9.profdata to chrome-mac-master-1611013939-848f93cc4650c420e66bbec68de10e40d4656b36.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: I3f606bb364a3d8d100396540df5c6081c85ccd0b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636502Reviewed-by:
-
Luciano Pacheco authored
- Add the JS module for icons.html. - Add the required resources to preprocess_if_exp) Bug: 1133186 Change-Id: Iac0c6f0c84e14bd1511157677452bc643bf9829a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636095 Commit-Queue: Luciano Pacheco <lucmult@chromium.org> Reviewed-by:
Jeremie Boulic <jboulic@chromium.org> Cr-Commit-Position: refs/heads/master@{#844649}
-
Michael Crouse authored
This removes tflite_deps from flatbuffers as it is not needed for the initial operations supported. This also removes those operations from being compiled when TFLite is included in the build. Bug: 1165517 Change-Id: I0e430b689a39e5a6664d789b7c15ce4618391800 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632387Reviewed-by:
Balazs Engedy <engedy@chromium.org> Reviewed-by:
Sophie Chang <sophiechang@chromium.org> Commit-Queue: Michael Crouse <mcrouse@chromium.org> Cr-Commit-Position: refs/heads/master@{#844648}
-
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/goldctl-win-chromium-autoroll Please CC bsheedy@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/+doc/master/autoroll/README.md Bug: None Tbr: bsheedy@chromium.org Change-Id: I477ea0e93269cf6a156b0f74b1017d0893e96661 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636497Reviewed-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/goldctl-linux-chromium-autoroll Please CC bsheedy@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/+doc/master/autoroll/README.md Bug: None Tbr: bsheedy@chromium.org Change-Id: I5ea65641e2c9606a2f078d6946d3aac9ae8c9fac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636498Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/679d118787e7..5635dbb91641 2021-01-18 penghuang@chromium.org Only call context::unMakeCurrent() if context is changed. 2021-01-18 geofflang@google.com Generate internal gl entry point functions as C functions. 2021-01-18 geofflang@google.com GL: Add detection of IMG and Vivante GPUs. 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/+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:983167 Tbr: cnorthrop@google.com Change-Id: I59b6953733a027688b1a408769a41f83a8c04498 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632780Reviewed-by:
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1610992290-a2bb9ab0a72f07714d6834315a5f80b743087bf7.profdata to chrome-win64-master-1611003391-f38d26b13046eb21865bd4aef763cfd6c815875c.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-win64-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:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I1d66aca2f7ee615cdfa968a021a5996c1221ef82 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632781Reviewed-by:
-
Maggie Cai authored
This reverts commit ddd08c52. Reason for revert: This CL is likly the cause for test failure DemoSetupArcSupportedTest.OnlineSetupFlowErrorDefault in builder Linux Chromium OS ASan LSan Tests (1) starting from https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20Chromium%20OS%20ASan%20LSan%20Tests%20(1)/39313/blamelist Original change's description: > OOBE: Arc-ToS Improvements > > Migrate ArcToSScreen to multistep behavior. > Get rid of display: none; and display: block; > > Bug: 1156667 > Change-Id: I4c2fc425edd4883c5edfceb0a5a9f67a6227de7b > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2603744 > Commit-Queue: Ossama Mahmoud <osamafathy@google.com> > Reviewed-by: Denis Kuznetsov [CET] <antrim@chromium.org> > Reviewed-by: Roman Sorokin [CET] <rsorokin@chromium.org> > Cr-Commit-Position: refs/heads/master@{#844554} TBR=antrim@chromium.org,rsorokin@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com,osamafathy@google.com Change-Id: I62973f98fccb5086b852879395d04f4a3050c244 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1156667 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636099Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/dabd9655278a..13466d016b58 2021-01-19 tikuta@chromium.org autoninja: use pure python3 to get build id and for post_build_ninja_summary.py 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: Ib94499c48d057bfffe9f1041dafa59528d7c3042 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636496Reviewed-by:
-
https://chromium-review.googlesource.com/c/chromium/src/+/2633748Nico Weber authored
Change-Id: I027a493f129021059ef8a7b51ca1d5bee01e65ac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2635076 Commit-Queue: Nico Weber <thakis@chromium.org> Commit-Queue: Dirk Pranke <dpranke@google.com> Auto-Submit: Nico Weber <thakis@chromium.org> Reviewed-by:
Dirk Pranke <dpranke@google.com> Cr-Commit-Position: refs/heads/master@{#844641}
-
Maggie Cai authored
This reverts commit ce17e926. Reason for revert: This CL is likely the cause of crash for test MessagePortProviderBrowserTest.PostMessage in builder Linux MSan Test starting from https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20MSan%20Tests/27063/blamelist Original change's description: > PostMessage hookup to allow payment request delegation. > > This CL adds fields to postMessage data structures that convey > the sender Window's intention to delegate a capability to the > receiver Window. The change is behind two runtime flags: one flag > ("CapabilityDelegation") enables the parsing of a new postMessage > option for delegation, while the other flag > ("CapabilityDelegationPaymentRequest") enables transmission of > payment request delegation information to the receiver Window. > > Bug: 1130558 > Change-Id: Ifad482bc9629ea69b9bd802d5f0f7df7c24645f5 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568627 > Commit-Queue: Mustaq Ahmed <mustaq@chromium.org> > Reviewed-by: Daniel Cheng <dcheng@chromium.org> > Reviewed-by: Robert Flack <flackr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#844548} TBR=dcheng@chromium.org,flackr@chromium.org,mustaq@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com Change-Id: I9a6ac999124984ca5ddff2a64f6c4f4eebd56e97 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1130558 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636098Reviewed-by:
-
Xianzhu Wang authored
Previously the maximum animation scale functions returned kInvalidScale if any keyframe in any animation of the element couldn't calculate a scale. Now return kInvalidScale only if none of the keyframes can calculate a scale. Change-Id: Id982445e68fe862c3f2ac1c93d11cb2a49aadcea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631347 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by:
-
Maggie Cai authored
This reverts commit c065ff54. Reason for revert: This CL is likely to cause the test failure in multiple builders. compositing/squashing/remove-from-grouped-mapping-on-reassignment.html Some builders: https://ci.chromium.org/ui/p/chromium/builders/ci/Mac10.15%20Tests/7566/blamelist https://ci.chromium.org/ui/p/chromium/builders/ci/Win7%20Tests%20(1)/113061/blamelist https://ci.chromium.org/ui/p/chromium/builders/ci/Win10%20Tests%20x64/52902/blamelist https://ci.chromium.org/ui/p/chromium/builders/ci/WebKit%20Win10/79230/blamelist https://ci.chromium.org/ui/p/chromium/builders/ci/WebKit%20Win10/79230/blamelist Original change's description: > Not clamp up setTimeout(..., 0) to 1ms for single_shot > > setTimeout(..., 0) is clamping up to 1ms for historical reasons: > crbug.com/402694, and the issue has been open for years which was > blocked by the challenge of updating all test expectations accordingly. > > Chrome doesn't need the clamp for anything in particular and no 1ms > clamp in the spec, moreover, we found Speedometer2 performance can boost > ~1% on Windows without it based on Pinpoint perf. > > Most failure tests failed with this change had been fixed in separated > CLs. > > Bug: 402694 > Change-Id: I46196584b887513ca520221be68099116931d4f2 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2578703 > Reviewed-by: Philip Jägenstedt <foolip@chromium.org> > Reviewed-by: Sami Kyöstilä <skyostil@chromium.org> > Commit-Queue: Wanming Lin <wanming.lin@intel.com> > Cr-Commit-Position: refs/heads/master@{#844459} TBR=skyostil@chromium.org,wanming.lin@intel.com,foolip@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com Change-Id: I0148f4b5cd39d4e1bea66f753c91aaf7da537fb5 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 402694 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636078Reviewed-by:
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/5cf0ef0022c7..29bd8638adb0 2021-01-18 asapersson@webrtc.org Add field trial for allowing cropped resolution when limiting max layers. 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: I8f5671490cd3e3d71004b256fb3445e990045eae Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636495Reviewed-by:
-
Bartek Nowierski authored
Names like |ptr| or |address| don't convey the intention for the pointer to point to the beginning of a slot, and |slot_start| does it. Improve comments while at it. The renaming made it obvious that in one case SlotSpan::FromPointer could be used instead of FromPointerNoAlignmentCheck. Change-Id: I17cc44bcbbfad57e17477bf64d54d140ad279c3e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631719Reviewed-by:
Benoit L <lizeb@chromium.org> Commit-Queue: Bartek Nowierski <bartekn@chromium.org> Cr-Commit-Position: refs/heads/master@{#844636}
-
