GitLab

https://chromium.googlesource.com/external/github.com/google/shaderc/+log/9f04be04a723..05c766a1f461


git log 9f04be04a723..05c766a1f461 --date=short --no-merges --format='%ad %ae %s'
2019-05-16 zoddicus@users.noreply.github.com Add flag to allow filtering tests cases being run (#625)


Created with:
  gclient setdep -r src/third_party/shaderc/src@05c766a1f461

The AutoRoll server is located here: https://autoroll.skia.org/r/shaderc-chromium-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=radial-bots+chrome-roll@google.com

Change-Id: I7436fad667f633ef8406a47b566550532804f87c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1616444Reviewed-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@{#660704}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/99fe071354e3..5737f025b55d


git log 99fe071354e3..5737f025b55d --date=short --no-merges --format='%ad %ae %s'
2019-05-17 ehmaldonado@chromium.org git-cl: Only display a detailed message when git-cl fails.


Created with:
  gclient setdep -r src/third_party/depot_tools@5737f025b55d

The AutoRoll server is located here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.



BUG=chromium:961663,chromium:955206
TBR=agable@chromium.org

Change-Id: Ib4251d8595bcb43845c6f39d0dba74edf3e4455c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1616446Reviewed-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@{#660703}

GestureScrollDebounceTimerOverscroll and
TouchGestureEndDispatchedAfterOverscrollComplete have shown signs of
flakiness on Fuchsia and Linux tsan bots.

Bug: 776424
Change-Id: I346753d25c4510e2e7ff9c8537962a36a79d89aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1616448
Auto-Submit: Fabrice de Gans-Riberi <fdegans@chromium.org>
Commit-Queue: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660702}

Bug: 920920
Change-Id: If3d67f02111cced48e7483b8d952a4ef00c40037
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614688
Commit-Queue: Fabrice de Gans-Riberi <fdegans@chromium.org>
Reviewed-by: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660701}

This reverts commit 61600282.

Reason for revert: Avoiding potential crashes due to mojom struct type update without version update.

Original change's description:
> [App Management] Add support to display managed badging for toggles.
>
> Add support to detect managed pinning and managed permissions
> and display badges next to the toggles.
>
> Screenshot:
> https://bugs.chromium.org/p/chromium/issues/detail?id=953580#c4
>
> TBR: raymes@chromium.org
> Bug: 953580
> Change-Id: Ia7f56f10243bfffe99c229e1255052c882c01262
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1605442
> Commit-Queue: Jeevan Shikaram <jshikaram@chromium.org>
> Reviewed-by: calamity <calamity@chromium.org>
> Reviewed-by: Dominick Ng <dominickn@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#660344}

TBR=calamity@chromium.org,dominickn@chromium.org,jshikaram@chromium.org,raymes@chromium.org

Change-Id: Id79ea8f176c78d02454dede98ac064231a642258
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 953580
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1616761
Commit-Queue: Jeevan Shikaram <jshikaram@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660700}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/4a8e975fb266..45aed26c5e06


Created with:
  gclient setdep -r src-internal@45aed26c5e06

The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome
TBR=beverloo@google.com,collinbaker@google.com,bcwhite@google.com,tasak@google.com

Change-Id: If46ebe52449ca81492e2c517567df2c4b2558909
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1616443Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#660699}

The anchor view is not updated until the slide animation is completed so this case previous would exit early when trying to switch tabs when the slide animation had not yet finished.

Bug: 910739
Change-Id: Ia5b28301dbab6a7c678228c153a92281a396ca33
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1616006
Commit-Queue: Caroline Rising <corising@chromium.org>
Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660698}

Bug: 921444
Change-Id: I07e7fd9ebd368639badb599c41bcb5ed8900e25d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614724
Commit-Queue: Charles . <charleszhao@chromium.org>
Reviewed-by: Charles . <charleszhao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660697}

Kerberos requires a host name to be able to obtain a ticket. Using an IP
address results in an authentication error. Detecting this case and
giving the user a more detail error message is a better user experience.

BUG=907207

Change-Id: I0369326a79501cefa2f2736d4a7933c79b740783
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1530282
Commit-Queue: Anand Mistry <amistry@chromium.org>
Reviewed-by: Sam McNally <sammc@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660696}

Set kAutofillSaveCreditCardUsesStrikeSystemV2 to default.

Bug: 884817
Change-Id: Ic0ff1d87fc9773735cda00e92b8d204bc442b50b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1615805
Commit-Queue: Anne Lim <annelim@google.com>
Reviewed-by: Jared Saul <jsaul@google.com>
Cr-Commit-Position: refs/heads/master@{#660695}

This CL updates the Plugin VM launcher strings and sets them as
translatable.

Change-Id: I39fda7cae344279073692af91b10fb6a03c14b9e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1602196Reviewed-by: Nicholas Verne <nverne@chromium.org>
Commit-Queue: Nicholas Verne <nverne@chromium.org>
Auto-Submit: Timothy Loh <timloh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660694}

This change adds the ability to export the activity log history as JSON
through an option in the 3 dots dropdown menu. The exported data is a
list of extension activities as returned by GetExtensionActivities from
the chrome.activityLogPrivate API (therefore the data might be different
than what's seen in the UI itself) but sorted by timestamp in ascending
order.

Screenshot: https://imgur.com/a/YNpyFCd

Bug: 832354
Change-Id: If891931bfa042e3f1eadecc6f6384198c4a2c6b4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1602074
Commit-Queue: Kelvin Jiang <kelvinjiang@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660693}

Raw image preview requests contain the source file as a DOM fileSystem
URL. Add a helper to resolve the fileEntry associated with the URL and
read its content into an ArrayBuffer with the DOM fileSystem API.

Add closure markup / comments, add externs/platform.js to BUILD.gn for
the DOM fileSystem API declarations, and Closure compile the lot.

Bug: 904630
Change-Id: I80d3f695dfce939b92d42932db666c3ab272ac69
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611624Reviewed-by: Luciano Pacheco <lucmult@chromium.org>
Commit-Queue: Noel Gordon <noel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660692}

We switch KeyboardControllerState to the new style according to [1].

This also gives us a benefit that we no longer have to handle the
COUNT enum value with NOTREACHED.

[1] https://chromium.googlesource.com/chromium/src.git/+/HEAD/tools/metrics/histograms/README.md#enum-histograms

TBR=sky@chromium.org

Bug: 845780
Change-Id: I84869a08e3f6187c767818643fd94db7dc590b08
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611070Reviewed-by: Darren Shen <shend@chromium.org>
Reviewed-by: Yuichiro Hanada <yhanada@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660691}

Bug: 881215
Change-Id: Ib39e29d773c5d94e23943929cce1572ac7cd619c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614769Reviewed-by: Dan Erat <derat@chromium.org>
Commit-Queue: Jia Meng <jiameng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660690}

Creates a quarantine service to be used to perform file scanning
/ invoking attachment services.

This change creates the service but does not implement the quarantine
logic.

A follow up change will move quarantine implementation from
components/services/download to the service,
and add the logic to call the service.

Bug: 870998
Change-Id: I21a06a98bed59ce01774d4da5b8319c1dfe7b55d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1595156Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Patrick Monette <pmonette@chromium.org>
Reviewed-by: Asanka Herath <asanka@chromium.org>
Commit-Queue: Alexander Woolf <alewoolf@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#660689}

This CL makes "cancel" the initially focused button in PWA installation
confirmation dialogs. This is to prevent accidental installations if the
user holds down enter.
The "install" button is still coloured blue as if it were the default action.

Before: https://bugs.chromium.org/p/chromium/issues/attachment?aid=391193&signed_aid=oHH2Y0KPtmjQ0oX90XEI4A==&inline=1
After: https://bugs.chromium.org/p/chromium/issues/attachment?aid=392968&signed_aid=sk4b6UZkAkZ9U6T9qqwovw==&inline=1

Change-Id: I05ac2d11aa15077395c617e5ba067025de6d98ca
Bug: 957848
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1588070
Commit-Queue: Alan Cutter <alancutter@chromium.org>
Auto-Submit: Alan Cutter <alancutter@chromium.org>
Reviewed-by: Jay Harris <harrisjay@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660688}

The App Service's apps::CrostiniApps class now listens for the
preference that enables or disables Crostini, and shows or hides the
Crostini Terminal app respectively.

The App Service + App List UI integration code (the
c/b/ui/app_list/app_service_* changes) also now hard-codes a Crostini
app folder, the same as the existing behavior (with the App Service
disabled), hard-coded into c/b/ui/app_list/crostini/*.

This commit also makes further changes to CrostiniAppModelBuilderTest so
that it works with the Mojo IPC based App Service.

Together, this fixes `unit_tests --enable-features=AppServiceAsh
--gtest_filter="CrostiniAppModelBuilderTest.*"`. It fails before and
passes after this commit.

Note that `unit_tests --gtest_filter="CrostiniAppModelBuilderTest.*"`,
without AppServiceAsh enabled, passes both before and after this commit.

BUG=826982

Change-Id: Id2bd1aa9d4de0389aa94eb5c1ce8211fe5997a11
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1598896
Commit-Queue: Nigel Tao <nigeltao@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Timothy Loh <timloh@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660687}

ContentSuggestionsCoordinator creates an AuthenticationService object
from BrowserState and passes it to NTPHomeMediator.

NTPHomeMediator can use this AuthenticationService to determine if
user is signed in or not and to fetch the user's avatar if user is
signed in.

Bug: 961120
Change-Id: I1935594130295926c76cfa1f469f8647e7dd4b49
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1612334
Commit-Queue: Peter Lee <pkl@chromium.org>
Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660686}

Chrome and Ash synchronized separate ShelfModel instances for Mash.
This is no longer necessary, given the discontinuation of Mash.

Remove Chrome's ShelfModel instance, use Ash's instance directly.
Remove shelf.mojom, struct traits, RemoteShelfItemDelegate, etc.

Cleanup ShelfController, ChromeLauncherController, ShelfItemDelegate.
Move ShelfModel access from Shell to a static singleton accessor.
Discontinue usage of menu.mojom for the Shelf; use SimpleMenuModel.
Remove unused shelf_alignment_menu.cc.

TBR=tsepez@chromium.org

Bug: 958215, 958247
Test: Automated; no Chrome OS shelf regressions.
Change-Id: Ib315c596bf1048e6aab3cfb754b9f6b402b93794
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1595553
Commit-Queue: Michael Wasserman <msw@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660685}

This code is being restored after having been removed from:
https://chromium-review.googlesource.com/c/chromium/src/+/1603743

Only change to restored code is to remove any |use_window_service|
params/codepaths that were present in the originally removed version.

This fixes a regression in Assistant which prevented Assistant Settings
and cards (implemented using NavigableContents) from rendering to the
user.

Bug: b:132717712
Change-Id: I27f3595f8e25bcf91664ea27beec27bf39855a31
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1613723Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Commit-Queue: David Black <dmblack@google.com>
Cr-Commit-Position: refs/heads/master@{#660684}

Bug: None
Change-Id: I18128ec2dbd49db91fd31275614b3a958235bd34
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1613649
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660683}

First, it adds (Base | Enhanced)UnweightedTree200 experiments, which
are like the originals but with 200 training examples maximum
instead of 100.

Since we're focusing on unweighted regression, this CL removes:

 - BaseTable
     This didn't seem to be representative of real MediaCapabilities
     probably due to lack of data / no data persistence.  Since we
     are focusing on unweighted anyway, BaseUnweightedTable or
     BaseUnweightedTree are better baselines.  We can also compare
     those to the upcoming unweighted MediaCapabilities experiment.

 - BaseTree
     This was an okay stand-in for MediaCapabilities, but since we
     are focusing on unweighted tasks, it's unclear that it means
     much as a baseline anymore.  BaseUnweightedTree is better to
     use as a baseline now.

 - EnhancedTree
     This didn't perform much differently than BaseTree, and was
     weighted anyway.

 - EnhancedUnweightedTree
     This didn't perform much differently than the unweighted tree,
     so no need to maintain it.  The newly-added 200 variant has
     a larger training set maximum size (200(!)), so we can see if
     that lets us get some more value from the new features.  To
     check the value of the features, compare the 200 variant to the
     BaseUnweightedTree200 instead.

 - BinarySmoothness
     This isn't a regression task.

Change-Id: I18b5a8bd042d7e44ba0c2e7e3780fa4fbc31c6a5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1606596Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Chrome Cunningham <chcunningham@chromium.org>
Commit-Queue: Frank Liberato <liberato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660682}

This reverts commit 8bb6bea4.

Reason for revert:

Findit (https://goo.gl/kROfz5) identified CL at revision 660506 as the
culprit for failures in the build cycles as shown on:
https://analysis.chromium.org/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtLzhiYjZiZWE0OGQ0MTMxMjQ4NDU1YmZkYjE1YTVjZDllODQxZThiMGIM

Sample Failed Build: https://ci.chromium.org/buildbot/chromium.memory/Linux%20MSan%20Tests/16868

Sample Failed Step: content_browsertests

Sending to CQ since there were merge conflicts upon reverting

Original change's description:
> Refactor to remove RenderWidget::PageScaleFactorChanged().
>
> This refactor moves the logic in RenderWidget::PageScaleFactorChanged()
> to RenderWidget::SetPageScaleStateAndLimits(). This removes the need for
> RenderViewImpl::PageScaleFactorChanged() to call GetWidget().
>
> Bug: 924336
> Change-Id: Ia6a345f31b80fcfda9f9dcb0a2c2765aac7ff613
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614080
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Commit-Queue: James MacLean <wjmaclean@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#660506}

TBR=dcheng@chromium.org,wjmaclean@chromium.org

Bug: 924336
Change-Id: Ic126ac8a219336fc60203c989230843225ac65b0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614472
Commit-Queue: Collin Baker <collinbaker@chromium.org>
Reviewed-by: Collin Baker <collinbaker@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660681}

Change-Id: Ieeb0e3f19358e5c204cbcb10d036010536d5da26
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1615596Reviewed-by: Vlad Tsyrklevich <vtsyrklevich@chromium.org>
Commit-Queue: Alexei Filippov <alph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660680}

https://pdfium.googlesource.com/pdfium.git/+log/908d73f65ad9..c5202e607426


git log 908d73f65ad9..c5202e607426 --date=short --no-merges --format='%ad %ae %s'
2019-05-16 thestig@chromium.org Fix a typo in CPDF_ImageRenderer::StartRenderDIBBase().
2019-05-16 thestig@chromium.org Revert "Temporarily disable EOL policy for .in files."
2019-05-16 thestig@chromium.org Tidy CPDF_StructElement.
2019-05-16 thestig@chromium.org Fix CRLF issues with bug_557223.in.


Created with:
  gclient setdep -r src/third_party/pdfium@c5202e607426

The AutoRoll server is located here: https://autoroll.skia.org/r/pdfium-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=pdfium-deps-rolls@chromium.org

Change-Id: Ib46a16be03f64b16264e7262ae5e0209f6bd92a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1616202Reviewed-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@{#660679}

Bug: None
Test: None
Change-Id: I74576fdeef30b3672b6e58a967c97c51bde150c9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1615312Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660678}

This will allow the download to happen in reduced mode.

BUG=942770

Change-Id: Ic7a61e978e5212bb8163143a005726d86197fd8a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1610994
Commit-Queue: Min Qin <qinmin@chromium.org>
Reviewed-by: Jian Li <jianli@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660677}

This change makes sure that the tab hover card is hidden and animation is stopped when a tab is deleted.

Bug: 963913
Change-Id: Icac21962a9fa2720bd2e55dd3e72d4cd441bedfc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1615599
Commit-Queue: Caroline Rising <corising@chromium.org>
Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660676}

Bug: 646113
Change-Id: I7ba7eb2950593576f6552b3a681a74437f6bffa4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1616150Reviewed-by: David Benjamin <davidben@chromium.org>
Commit-Queue: Eric Roman <eroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660675}

WillStart time:
On Android, this is now just measuring a PostTask for most navigations.
Other platforms are very fast (99th %ile ~1ms).

Ignored:
This measured with more data in Android.TabNavigationInterceptResult

Bug: None
Change-Id: I0c050ba9ee14e7a2904e97e549d23895234f81ba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1615363Reviewed-by: Nate Fischer <ntfschr@chromium.org>
Commit-Queue: Charlie Harrison <csharrison@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660674}

https://chromium.googlesource.com/angle/angle.git/+log/aefbea29626b..06de90c66c18


git log aefbea29626b..06de90c66c18 --date=short --no-merges --format='%ad %ae %s'
2019-05-16 syoussefi@chromium.org Vulkan: Re-enable a handful of suppressed ES3 tests
2019-05-16 jmadill@chromium.org Break debugger on assertion failure.


Created with:
  gclient setdep -r src/third_party/angle@06de90c66c18

The AutoRoll server is located here: https://autoroll.skia.org/r/angle-chromium-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

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_optional_gpu_tests_rel
TBR=syoussefi@google.com

Change-Id: I0e8cec0f1c0b0bd233bff94a2af3ab1d258799da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1616201Reviewed-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@{#660673}

This changelist
https://chromium-review.googlesource.com/c/chromium/src/+/1611313
has a bug in it where bot_platforms.py's configuration says not to
schedule blink_perf.display_locking on Nexus 5X Perf, but the
shard map for Nexus 5X Perf does contain blink_perf.display_locking.

This changelist fixes that bug by adding the configuration to
bot_platforms.py and it adds a presubmit test to cover that.
That presubmit is really just a more specific presubmit than
what is in perf_data_generator.py, so I also deleted the existing
check from there. (The difference is that the new check is
per-platform. I think that the check should be in
generate_perf_sharding because that is where we configure shard maps,
versus perf_data_generator is for generating buildbot json files,
which should become decoupled in the future.

I also deleted the Telemetry-specific test cases from
perf_data_generator_unittest.py. I'm thinking these tests
are no longer necessary since we now verify consistency in
PRESUBMIT.


Change-Id: I31afa1fd8782951f750e5f5c5c8b7fb959f5a049
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614358Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Caleb Rouleau <crouleau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660672}

This reverts commit b85dc559.

Reason for revert: build failure on https://ci.chromium.org/p/chromium/builders/ci/win-archive-dbg/4

Error is "../../net/third_party/quiche/src/quic/tools/quic_toy_client.cc(45,10): fatal error: 'netdb.h' file not found"

Original change's description:
> Roll src/net/third_party/quiche/src/ 63d0bc4ae..8474fd7a2 (17 commits)
> 
>     https://quiche.googlesource.com/quiche.git/+log/63d0bc4ae8dc..8474fd7a2f24
> 
>     $ git log 63d0bc4ae..8474fd7a2 --date=short --no-merges --format='%ad %ae %s'
>     2019-05-16 rch gfe-relnote: n/a - Remove overly broad include from quic_toy_client.h
>     2019-05-16 fayang Add logging only ack_frame accessor.
>     2019-05-15 rch gfe-relnote: n/a - Add missing include for quic_flag_utils.h in quic_packet.cc
>     2019-05-15 nharper Add QUIC_BUG_IF to QuicUtils::GetCryptoStreamId
>     2019-05-15 rch Move virtually all the toy client logic out of quic_client_bin.cc and into a new QuicToyClient class which can be used in chromium.
>     2019-05-15 wub gfe-relnote: (n/a) Delete use_stateless_rejects_if_peer_supported from QuicCryptoServerStream's constructor. No behavior change, not protected.
>     2019-05-15 dschinazi Replace a DCHECK with a parse failure in connection ID parsing
>     2019-05-15 rch Move drop_response_body from QuicClient to QuicSpdyClientBase to share with chromium
>     2019-05-15 rch Extract the FakeProofVerifier from quic_client_bin.cc to facilitate sharing with Chromium.
>     2019-05-15 dschinazi Add QuicFramer Probe methods
>     2019-05-15 vasilvv Remove .impl() method from QuicSocketAddress and QuicIpAddress.
>     2019-05-15 quiche-dev Change QuartcClientEndpoint to handle client-side version negotiation.
>     2019-05-15 wub In quic_client_bin.cc, print the "Request (succeeded|failed)" messages in stdout instead of stderr.
>     2019-05-15 fkastenholz Have separate uni- and bi-directional stream limits for IETF QUIC
>     2019-05-15 wub Fix a use-after-free in quic_client.
>     2019-05-14 quiche-dev Project import generated by Copybara.
>     2019-05-14 fayang gfe-relnote: Deprecate gfe2_reloadable_flag_quic_fix_termination_packets.
> 
>     Created with:
>       roll-dep src/net/third_party/quiche/src src/third_party/quic_trace/src
> 
> Change-Id: I43e3ac80816bade7d80e2ca8ae9f92bb3f457d95
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614938
> Commit-Queue: Ryan Hamilton <rch@chromium.org>
> Reviewed-by: Steve Anton <steveanton@chromium.org>
> Reviewed-by: Zhongyi Shi <zhongyi@chromium.org>
> Auto-Submit: Ryan Hamilton <rch@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#660666}

TBR=rch@chromium.org,zhongyi@chromium.org,steveanton@chromium.org

Change-Id: I7d74bb2f140d840ec93a9e55883a6694a19cc157
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1616423Reviewed-by: Collin Baker <collinbaker@chromium.org>
Commit-Queue: Collin Baker <collinbaker@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660671}

Bug: None
Change-Id: I5c3c5eaba63041bbad30d53b2590382eafba45a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1613747Reviewed-by: Esmael El-Moslimany <aee@chromium.org>
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660670}

This reverts commit 84c7124e.

Reason for revert: It looks like this caused flakiness in OutOfProcessPPAPITest.FlashFullscreen.

See:
https://ci.chromium.org/p/chromium/builders/ci/Linux%20Tests
https://findit-for-me.appspot.com/p/chromium/flake-portal/analysis/analyze?key=ag9zfmZpbmRpdC1mb3ItbWVyqAELEhdNYXN0ZXJGbGFrZUFuYWx5c2lzUm9vdCJyY2hyb21pdW0ubWVtb3J5L0xpbnV4IEFTYW4gTFNhbiBUZXN0cyAoMSkvNjA5NTgvYnJvd3Nlcl90ZXN0cy9UM1YwVDJaUWNtOWpaWE56VUZCQlVFbFVaWE4wTGtac1lYTm9SblZzYkhOamNtVmxiZz09DAsSE01hc3RlckZsYWtlQW5hbHlzaXMYAQw
https://findit-for-me.appspot.com/p/chromium/flake-portal/analysis/analyze?key=ag9zfmZpbmRpdC1mb3ItbWVyqQELEhdNYXN0ZXJGbGFrZUFuYWx5c2lzUm9vdCJzY2hyb21pdW0ubGludXgvTGludXggVGVzdHMvNzc4NjgvYnJvd3Nlcl90ZXN0cyBvbiBVYnVudHUtMTYuMDQvVDNWMFQyWlFjbTlqWlhOelVGQkJVRWxVWlhOMExrWnNZWE5vUm5Wc2JITmpjbVZsYmc9PQwLEhNNYXN0ZXJGbGFrZUFuYWx5c2lzGAEM

Original change's description:
> Fix weird artifacts during resizing browser window on Linux
> 
> This CL uses _NET_WM_SYNC_REQUEST to synchronize with desktop
> compositor during resize.
> Without this CL, resize steps are:
> 1. Desktop compositor(WM) resizes chrome browser window.
> 2. Desktop compositor draws a new frame with the current browser window
>    without waiting chrome to complete handle the ConfigureNotify event.
>    For SW rendering, compositor uses the content before resizing. It will
>    out of synced size between compositor and chrome.
>    For GPU rendering, compositor uses the framebuffer before resizing, the
>    behavior is undefined. It cause weird artifacts.
> 4. Desktop compositor go to step 1, to issue a new resize.
> 5. Chrome finished handle the ConfigureNotify and rendered a new frame.
> 6. Desktop compositor draws a new frame again with right size.
> 
> With this CL, resize steps are:
> 1. Desktop compositor sends client message _NET_WM_SYNC_REQUEST to notify
>    about the incoming resize
> 2. Desktop compositor WM resizes chrome browser window.
> 3. Desktop compositor waits on an alert on value change of a XSYNC counter
>    on chrome window.
> 4. Chrome handles the ConfigureNotify event, and renders a new frame.
> 5. Chrome increases the XSYNC counter on chrome window.
> 6. Desktop compositor gets the alert of counter change, and draws a new
>    frame with new content from chrome.
> 7. Desktop compositor responses user mouse move events, and starts a new
>    resize process, go to step 1.
> 
> 
> Change-Id: I51aafe03b8aac73ce6570976bbe36c6f4d86531a
> Bug: 961858
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1602285
> Commit-Queue: Peng Huang <penghuang@chromium.org>
> Reviewed-by: Scott Violet <sky@chromium.org>
> Reviewed-by: kylechar <kylechar@chromium.org>
> Reviewed-by: Ken Buchanan <kenrb@chromium.org>
> Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
> Reviewed-by: Antoine Labour <piman@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#660532}

TBR=penghuang@chromium.org,sky@chromium.org,kenrb@chromium.org,kylechar@chromium.org,piman@chromium.org,thomasanderson@chromium.org

Change-Id: I863ea3a4bb6b39fd3c65c4ea1dbbb56072988a26
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 961858
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1616384Reviewed-by: Collin Baker <collinbaker@chromium.org>
Commit-Queue: Collin Baker <collinbaker@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660669}

TBR=piman@chromium.org

Bug: None
Change-Id: I7097c8dd3ebbd7690228fcfcd79dec746a913de5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1616018Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660668}

Bug: 960915
Change-Id: I3e39cc3ba6e4e98ad9a01ac2ab9028fa1a1f76d7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614433
Commit-Queue: Taylor Bergquist <tbergquist@chromium.org>
Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660667}

    https://quiche.googlesource.com/quiche.git/+log/63d0bc4ae8dc..8474fd7a2f24

    $ git log 63d0bc4ae..8474fd7a2 --date=short --no-merges --format='%ad %ae %s'
    2019-05-16 rch gfe-relnote: n/a - Remove overly broad include from quic_toy_client.h
    2019-05-16 fayang Add logging only ack_frame accessor.
    2019-05-15 rch gfe-relnote: n/a - Add missing include for quic_flag_utils.h in quic_packet.cc
    2019-05-15 nharper Add QUIC_BUG_IF to QuicUtils::GetCryptoStreamId
    2019-05-15 rch Move virtually all the toy client logic out of quic_client_bin.cc and into a new QuicToyClient class which can be used in chromium.
    2019-05-15 wub gfe-relnote: (n/a) Delete use_stateless_rejects_if_peer_supported from QuicCryptoServerStream's constructor. No behavior change, not protected.
    2019-05-15 dschinazi Replace a DCHECK with a parse failure in connection ID parsing
    2019-05-15 rch Move drop_response_body from QuicClient to QuicSpdyClientBase to share with chromium
    2019-05-15 rch Extract the FakeProofVerifier from quic_client_bin.cc to facilitate sharing with Chromium.
    2019-05-15 dschinazi Add QuicFramer Probe methods
    2019-05-15 vasilvv Remove .impl() method from QuicSocketAddress and QuicIpAddress.
    2019-05-15 quiche-dev Change QuartcClientEndpoint to handle client-side version negotiation.
    2019-05-15 wub In quic_client_bin.cc, print the "Request (succeeded|failed)" messages in stdout instead of stderr.
    2019-05-15 fkastenholz Have separate uni- and bi-directional stream limits for IETF QUIC
    2019-05-15 wub Fix a use-after-free in quic_client.
    2019-05-14 quiche-dev Project import generated by Copybara.
    2019-05-14 fayang gfe-relnote: Deprecate gfe2_reloadable_flag_quic_fix_termination_packets.

    Created with:
      roll-dep src/net/third_party/quiche/src src/third_party/quic_trace/src

Change-Id: I43e3ac80816bade7d80e2ca8ae9f92bb3f457d95
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614938
Commit-Queue: Ryan Hamilton <rch@chromium.org>
Reviewed-by: Steve Anton <steveanton@chromium.org>
Reviewed-by: Zhongyi Shi <zhongyi@chromium.org>
Auto-Submit: Ryan Hamilton <rch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660666}

Bug: 621383
Change-Id: Ie2da4387a8352073c6d2221274b39034c8ee285c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1616148
Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#660665}