GitLab

It helps us to don't wait until OnDisconnect method will be invoked
after destructing fake cros_healthd client. We can invoke OnDisconnect
manually without blocking test.

Change-Id: I9f0f675710f8c331fabd27ea806999599595311c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2390662
Commit-Queue: Oleh Lamzin <lamzin@google.com>
Reviewed-by: Paul Moy <pmoy@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805067}

The powerd battery info was designed to be a periodic signal. This was
fine because the need was for low battery warning. Now that we want to
display the Bluetooth battery values continuously, there is a problem
where Chrome does not have the battery values after Chrome restarts (for
example when signing out) until powerd's next battery poll.

A workaround for this is to have an API in powerd for Chrome to request
a signal for a Bluetooth device. This lets Chrome sync with powerd's
battery values when Chrome starts up. This workaround will be removed
when we migrate to go/bluez-battery-provider-api.

Corresponding powerd change: CL:2378569.

BUG=b:166530001

Change-Id: Ibceb1f44f808c6bfa9752cb62f23a8fba236b60b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2378788
Commit-Queue: Ryan Hansberry <hansberry@chromium.org>
Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805066}

Bug: 1120279
Change-Id: I20894d22ca27fff91235b50b03d73c0445d18ed4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2390974
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805065}

use of test-only-api.js in preparation for launching official MojoJS support
in WPT. This would not change the test results on Chromium waterfall
(everything should continue to pass) or upstream WPT (tests currently
fail because MojoJS isn't enabled).

Bug: 1123992
Change-Id: I513e6d432f6c74a62109ea09ce0dbaeefc63b0c4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391224
Commit-Queue: Arnaud Mandy <arnaud.mandy@intel.com>
Reviewed-by: Robert Ma <robertma@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805064}

https://chromium.googlesource.com/angle/angle.git/+log/2d00262a1459..e5882825af72

2020-09-08 cwallez@chromium.org Texture::copyImage: Correctly compare against FBAttachment

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:1125354
Tbr: ianelliott@google.com
Change-Id: I0cae6175b339ac151fb8066e681ad572f38ee26b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399064Reviewed-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@{#805063}

This change adds a threshold for the number of rebuffer events
per frame before LiteVideos stop throttling requests attached
too the frame.

Bug: 1111348
Change-Id: I236fd7f647f81e45114315eb3e0dcc4c0e32083e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2393012
Commit-Queue: Michael Crouse <mcrouse@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: rajendrant <rajendrant@chromium.org>
Reviewed-by: Sophie Chang <sophiechang@chromium.org>
Auto-Submit: Michael Crouse <mcrouse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805062}

Test flaky, disable for now and fix it later.

TBR=tedchoc@chromium.org

Bug: 1126145
Change-Id: Ie6b947dc7d9b1735d25c5f1e7db2fa4cb95c3e53
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398975Reviewed-by: Gang Wu <gangwu@chromium.org>
Commit-Queue: Gang Wu <gangwu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805061}

This adds the standard set of Tast tests to new betty-arc-r bot. But
unlike other CrOS VM tests, we can't run these in GCE since the Android
VM (inside the CrOS VM (inside the GCE VM)) doesn't work well on GCE.

However, they could theoretically run on KVM-enabled baremetal machines
in the lab, which removes the extra GCE VM layer that interferes with
the tests.

So we'll try running them on CrOS device hosts. A bot's device will be
unused during the tests, which is unfortunate. But there's plenty of
head room in the pools, and they're already running CrOS tests, so
adding these fits well to their purpose in life.

Bug: 1120109
Change-Id: I09e6c40935df7d95126e9848bc7f26ac70be2b8b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392943
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Reviewed-by: Erik Staab <estaab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805060}

Roll Chrome Mac PGO profile from chrome-mac-master-1599544645-2607fe83108ec346cd143f52f7129c53aeca332a.profdata to chrome-mac-master-1599587571-75a79fa48b42004db7f7ebb181ae53e5f370e716.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 sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@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: chrome/try:mac-chrome
Tbr: sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@google.com
Change-Id: I2608647fa6fdaeaee4ed0d1e45f5886cd7b38de5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399362Reviewed-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@{#805059}

Disable RenderWidgetHostViewChildFrameBrowserTest.
VisualPropertiesPropagation_DisplayMode on Mac and Linux due to flaky.

Bug: 1126153
Tbr: kenrb@chromium.org
Change-Id: If31a8b4ede074539f250b2869307e36add8b4c1c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399302Reviewed-by: Owen Min <zmin@chromium.org>
Commit-Queue: Owen Min <zmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805058}

This CL fixes an issue where autoscroll may be called on a scrollbar
layer that is deleted. When the pointer is pressed down, an autoscroll
task is scheduled to be executed after ~250ms. The task will execute if
the pointer remains held down. In LayerTreeImpl::UnregisterScrollbar,
DidUnregisterScrollbarLayer only gets called after both scrollbars are
removed. So if you go from 2 to 1 scrollbar while an autoscroll task is
queued, the autoscroll task won't get cancelled. At this point, the
ScrollbarController tries to access the deleted scrollbar and that
leads to an access violation. The fix here is to ensure that the call
to DidUnregisterScrollbarLayer happens for each scrollbar.

Bug: 1106612
Change-Id: I4f1d684830012db8fdd73258c9a9e5231807bcb6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2356809Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Rahul Arakeri <arakeri@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#805057}

Adding a player to MediaSessionImpl automatically requests the audio
focus. We need to fix this up in case a paused player is added due to
entering Picture-in-Picture.

Bug: 1117390, 1117397
Change-Id: I1c8b69dbefe19f6d8a99a3b8d2a01fa2123a47f4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2387643Reviewed-by: Becca Hughes <beccahughes@chromium.org>
Commit-Queue: Wojciech Dzierżanowski <wdzierzanowski@opera.com>
Cr-Commit-Position: refs/heads/master@{#805056}

Revert CL:
https://chromium-review.googlesource.com/c/chromium/src/+/2391598

Original CL:
https://chromium-review.googlesource.com/c/chromium/src/+/2372888

Context:
The revert was done because the waterfall had test failures. It was
later found to be caused by another CL. So the original CL was wrongly
reverted. This CL is to reland it without change.

Bug: 978471, 1102522
Change-Id: I24bfe5815c34cd7fb2ffbcbe33f839334ac08d75
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392763Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805055}

The History URL provider cleans up trailing whitespace from the input
when matching suggestions. However, using this clean input for rich
autocompletion results in inputs like 'g   ' matching suggestions like
'google.com' which would be displayed as 'g   |[oogle.com]'. This CL
uses the original input for rich autocompletion in the history URL
provider.

Bug: 1062446
Change-Id: If31c85a821f6dae924a1ccc8b36a83fcdff97791
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392953Reviewed-by: Tommy Li <tommycli@chromium.org>
Commit-Queue: manuk hovanesian <manukh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805054}

I decided to not move forward with this experiment here:
https://github.com/whatwg/html/issues/5257#issuecomment-607548564

Bug: 1126053
Change-Id: Ic6dd7446f14d38dc5f9f5b9538a9278c88528ef1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399119Reviewed-by: Mason Freed <masonfreed@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805053}

For the following case:
  bar/test.html [ Failure ]
  virtual/foo/bar/* [ Pass ]
  virtual/foo/bar/test.html [ Failure ]
previously the last virtual expectation was mistakenly reported as
redundant.

Now ignore such entries if there is a virtual glob expectation
overriding the base expectation.

Bug: 1124787
Change-Id: I9ab0c751343cf066e5c8f2db803a610e0cbb27e1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2393945
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Auto-Submit: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805052}

When selected, document suggestions get added to the shortcut provider.
Document suggestion descriptions include last accessed date & owner.
Both these can change; caching them in the shortcut provider can result
in showing stale data. A previous CL (crrev.com/c/2107811) excludes
dates from being stored in the shortcut description. This CL likewise
excludes owners.

Bug: 1035105
Change-Id: If1c38d70457835ad41b7df3d3622f91a26fea4d4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392948Reviewed-by: Tommy Li <tommycli@chromium.org>
Commit-Queue: manuk hovanesian <manukh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805051}

Fuse.js is a third party fuzzy search library
used to search tab in tab search

Doc: https://docs.google.com/document/d/1_fXj3gDdKOI7Mk97Usjys7JEYf44bfMTGPhtaEGsMEE/edit
Bug: 1099917
Change-Id: Ibd2e2c341998e5efb1ce8c0fb4f6e7aa777f6997
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375728Reviewed-by: Darin Fisher <darin@chromium.org>
Reviewed-by: Christopher Thompson <cthomp@chromium.org>
Commit-Queue: Yuheng Huang <yuhengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805050}

Disable the test virtual/threaded-composited-iframes/external/wpt/
is-input-pending/tentative/same-origin-subframe.sub.html on Mac due to
flaky.

Bug: 1124978
TBR: npm@chromium.org
Change-Id: I8c690da0f9ab0d456534d353716e708cfe12f54a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399300Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Owen Min <zmin@chromium.org>
Commit-Queue: Owen Min <zmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805049}

Bug: 1115755
Change-Id: Ia67066a172ebd16f4fa9a305eed04986e98210f4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391218Reviewed-by: Shakti Sahu <shaktisahu@chromium.org>
Commit-Queue: Hesen Zhang <hesen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805048}

These files need to be accessible when running wpt
outside chromium environment.

see: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md#mojojs

This is the first step towards making these tests pass outside the Chromium CI

Bug: 1123989
Change-Id: I9600bc52f6c9ec2217ff09c72c6bdcc6a5af4b9f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391255
Commit-Queue: Arnaud Mandy <arnaud.mandy@intel.com>
Reviewed-by: Finnur Thorarinsson <finnur@chromium.org>
Reviewed-by: Michael Moss <mmoss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805047}

Using wpt-import in Chromium 15f9f86c.

Note to sheriffs: This CL imports external tests and adds
expectations for those tests; if this CL is large and causes
a few new failures, please fix the failures by adding new
lines to TestExpectations rather than reverting. See:
https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md

NOAUTOREVERT=true
TBR=smcgruer@google.com

No-Export: true
Change-Id: I5301391d0e0e188a7055a5ce67f8f3d481382376
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398560Reviewed-by: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#805046}

This change forwards the correct --gtest_repeat arg on to gtest instead
of the incorrect --repeat arg when the --repeat flag is used with
run-swarmed.py.

Bug: 1124365
Change-Id: Ie2e8b1a74748f4230570721dfaef845cd1d4f022
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391161Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Commit-Queue: Cammie Smith Barnes <cammie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805045}

This still ensures that the tabstrip is never in Stacked mode with any Tab Groups active. However, it allows Stacked mode if there are no groups created yet. Before, it would disallow Stacked mode if the feature was enabled, even if no groups were created yet.

To keep the separation between Tab Groups and Stacked mode, this change also takes the tabstrip out of Stacked mode if a group is created while in Stacked mode.

Change-Id: Ic359eaf95cf7fd2ebc2b3440a118b715640cfa45
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399010Reviewed-by: Charlene Yan <cyan@chromium.org>
Commit-Queue: Charlene Yan <cyan@chromium.org>
Commit-Queue: Connie Wan <connily@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805044}

Also remove calls to assert sizes are the same since that is covered by asserting the models are in the right order. This will show better debug logs as well when tests fail.


Bug: 1124926
Change-Id: I739c9797e0785e077d16d6a29bc9cf17ce680ea1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2390664Reviewed-by: Kyle Milka <kmilka@chromium.org>
Commit-Queue: Sophey Dong <sophey@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805043}

This add additional EG test coverage for real-time Safe Browsing,
for scenarios identified by the test team when they were manually
testing this feature.

Bug: 1122997
Change-Id: I984babf81e251381965454679fa293426fc4c958
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392977
Commit-Queue: Ali Juma <ajuma@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805042}

R=rockot@google.com

Bug: N/A
Change-Id: I33724debfb3416e6d5b54e5564fe8846f2103841
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2393976Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805041}

Skew tests are being added for the following versions:
1, 85.0.4183.81
2, 86.0.4240.16
3, 84.0.4147.89

TBR=estaab@chromium.org

Bug: 1041619
Change-Id: Ie5ceaa9820fa20f65002a67d903a96c88e953f24
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398956Reviewed-by: Rakib Hasan <rmhasan@google.com>
Commit-Queue: Rakib Hasan <rmhasan@google.com>
Cr-Commit-Position: refs/heads/master@{#805040}

https://chromium.googlesource.com/external/github.com/AOMediaCodec/libavif.git/+log/f88383daa8de..616bd4f9aeca

$ git log f88383daa..616bd4f9a --date=short --no-merges --format='%ad %ae %s'
2020-09-03 wtc Remove 16bpc cases in avifLimitedToFullY(), etc.
2020-09-03 wtc Remove the avifCodecSpecificOptionsGet() function
2020-09-01 wtc Add the libaom-specific option tune=METRIC
2020-09-01 wtc Make avifCodecSpecificOptionsGet a const function

Created with:
  roll-dep src/third_party/libavif/src
R=dalecurtis@chromium.org

Change-Id: Ia50e27556d10ac03221d1c950bcaa510614e65f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398964Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Wan-Teh Chang <wtc@google.com>
Cr-Commit-Position: refs/heads/master@{#805039}

The test was intended for a time when we would fully support tablet mode
with multiple displays and no display mirroring. It seems that just will
not happen in the foreseeable future.

Fixed: 1125848
Change-Id: I13ee5c2a0dd3f717489e615caa083fb74b6b859c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398974Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Avery Musbach <amusbach@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805038}

Before this CL, the child process start-up flow went like this:
 1.) Browser would create a Mojo invitation, with a mojom::ChildProcess
     receiver, that ChildThreadImpl would recover and bind.
 2.) ChildThreadImpl immediately creates a remote for its
     ChildProcessHost so it can start queueing messages for the browser
     process, even though it is not bound to the browser.
 3.) ChildThreadImpl asynchronously waits for ChildProcess::Initialize
     to be invoked by the browser process; this supplies a remote for
     mojom::ChildProcessHostBootstrap, which the child process uses to
     send the receiver for the remote created in (1).
 4.) Browser receives this, binding it to either
     RenderProcessHostImpl::io_thread_host_impl_ or ChildProcessHostImpl

In short, there's an awkward dance that has to be done between the
browser <-> renderer ((3) above), so that they can both immediately
initialize remotes for each other. This CL removes the extra IPC round
trip by removing ChildProcessHostBootstrap, and steps (3) & (4) above.
This is done by attaching a second message pipe to the mojo invitation
corresponding to the ChildProcessHost receiver, so the child process has
it immediately on init. At this point, the child process can create a
remote for the ChildProcessHost, and immediately bind it to the pipe
which is bound to the browser process's ChildProcessHost receiver.

Bug: N/A
R=haraken@chromium.org,rockot@google.com

Change-Id: I8f7b4b698b82e25d1c5c991c9639e57de05a6360
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2393158Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Martin Barbella <mbarbella@chromium.org>
Reviewed-by: Tal Pressman <talp@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805037}

It was introduced in 724239 to inspect accessible trees by process id but this feature was removed in 1113674 as duplicate of inspect by window id feature

Bug: None
Change-Id: Ifec72d6ad2aef9238632588e8a65a77a37ca66d2
AX-Relnotes: n/a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2390852Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Alexander Surkov <asurkov@igalia.com>
Cr-Commit-Position: refs/heads/master@{#805036}

Bug: N/A
Change-Id: I5bb8e59f3a4cf8229bb389636f24243e6b98b64d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2393558Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805035}

https://crrev.com/c/2353193 added a "kDragDrop" UserAction to be used when
accessing dropped entries via the native file system API. But somehow I
forgot to actually hook this up to the D&D code.

This hooks it up by adding a UserAction parameter to CreateFileEntryFromPath
and CreateDirectoryEntryFromPath (and simplifying some bits of code a bit).

Bug: 1124833
Change-Id: Ic8b165441996c64f2849fada1787a613adeee675
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392772Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805034}

Bug: 1084107
Change-Id: I3dc2e16a9907c8a6e84307b27dbec940f8361c43
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398578Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Caitlin Fischer <caitlinfischer@google.com>
Cr-Commit-Position: refs/heads/master@{#805033}

TBR=govind@chromium.org

Change-Id: I94d408a0cfea9d20d19678f40970670d14f61c90
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399006Reviewed-by: Ben Mason <benmason@chromium.org>
Reviewed-by: Krishna Govind <govind@chromium.org>
Commit-Queue: Ben Mason <benmason@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805032}

Replace gpuBenchmarking calls with testdriver calls.
Remove pointerevent_touch-adjustment-click_target from the SlowTests file.

Change-Id: Ifd7cb4d5ab44a8498d99f053c146442ed291848e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398969Reviewed-by: Lan Wei <lanwei@chromium.org>
Commit-Queue: Liviu Tinta <liviutinta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805031}

Change-Id: I3dace6defe908221b2f0783d8bc1cca6a4a6ffd5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391286Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805030}

https://android.googlesource.com/platform/external/perfetto.git/+log/6f29c57c715c..c107c7e93630

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-linux-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: Iaa5ad35519b3988b316663b05c906fd448ec3791
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398839Reviewed-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@{#805029}

Add trybot config for "Win10 Tests x64 1909". Need to test
rebaselining before promoting the win version

Bug: 990885,1125612
Change-Id: Id722ed9a8a841dabce21cd5694186a6cbe0fc281
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2397660Reviewed-by: Garrett Beaty <gbeaty@chromium.org>
Commit-Queue: Ian Struiksma <ianstruiksma@google.com>
Cr-Commit-Position: refs/heads/master@{#805028}