GitLab

BookmarkBarViewTest12.CloseWithModalDialog is in timeout.
That's because DialogWaiter is observing for a wrong aura::Env
instance.

BUG=883523
TEST=interactive_ui_tests --enable-features=SingleProcessMash

Change-Id: Ia2b057763e87458a564dbffa25c6cc92889992a6
Reviewed-on: https://chromium-review.googlesource.com/1244125Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Jun Mukai <mukai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594149}

Bug: 822954
Change-Id: Ife5a6460c0215fa188e3734fa781ecfb994e94b9
Reviewed-on: https://chromium-review.googlesource.com/1241994
Commit-Queue: Shubhie Panicker <panicker@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594148}

BUG=888779
TEST=interactive_ui_tests --enable-features=SingleProcessMash

Change-Id: If0653a7dae1e7c156f122680fd6be71b001dd9f3
Reviewed-on: https://chromium-review.googlesource.com/1244300Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Commit-Queue: Jun Mukai <mukai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594147}

This is needed for both sanity test and tast tests, so this applies
the env var changes for every type of test. Normal GTest tests don't
need it, but they'll get it anyway. Shouldn't be harmful.

Change-Id: Ida2bd856fc75a089f899c4e4cfdc56de90d5fa48
Reviewed-on: https://chromium-review.googlesource.com/1244876Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594146}

Use the constants from manifest_constants.* in extension_builder.cc
instead of using string literals.

Bug: None
Change-Id: I111beee9274c7ac347ffb3df0657bb1d1b6327fb
Reviewed-on: https://chromium-review.googlesource.com/1242274
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594145}

DragDropClientMac is one of the few remaining structures that Cocoa
and Views code depends on. Break this dependency cycle, so that we can
move all Cocoa code to ui/views_brige_mac.
* Separate out the interface that Cocoa depends on and move it to
  views_bridge_mac::DragDropClient.
* Make views::DragDropClientMac be a member of the browser side
  structure views::BridgedNativeWidgetHostImpl

Note that this does not solve the problem that drag drop behavior is
not implemented over mojo. When using RemoteMacViews, drag drop
functionality will still be absent.

Bug: 859152
Change-Id: I3d5b8a3b8ae9403effd17436e727ba4298bcae61
Reviewed-on: https://chromium-review.googlesource.com/1244720Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594144}

Currently the destructor of BaseAudioContext has 3 DCHECKs touching
GC-managed objects. This is a violation of GC system. Move them from
the destructor to Uinitialize() method, which gets called before the
destruction.

with --repeat-each=50 option.

Bug: 856317
Test: webaudio/Analyser/realtimeanalyser-float-data.html passes
Change-Id: Ifa898d95feda3fcc1ae82e3e99a27e45edca38ab
Reviewed-on: https://chromium-review.googlesource.com/1237247
Commit-Queue: Hongchan Choi <hongchan@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594143}

Bug: 865062
Change-Id: I8efb1817b1b2bf390189ed117c8773b6a0329ded
Reviewed-on: https://chromium-review.googlesource.com/1244798Reviewed-by: Nate Fischer <ntfschr@chromium.org>
Commit-Queue: Tobias Sargeant <tobiasjs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594142}

https://pdfium.googlesource.com/pdfium.git/+log/9412c8ec36d1..072d829e2cd1


git log 9412c8ec36d1..072d829e2cd1 --date=short --no-merges --format='%ad %ae %s'
2018-09-25 thestig@chromium.org Optimize MaybeEmbedPositionAdjustmentPatterns().


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

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=dsinclair@chromium.org

Change-Id: I77630b895f881d4edeac45c9d9c614fc1e50f782
Reviewed-on: https://chromium-review.googlesource.com/1244537Reviewed-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@{#594141}

This CL uses ScopedBlockingCall to mark blocking calls in /device/usb.

This CL was created by replacing calls to AssertBlockingAllowed()
with instantiations of ScopedBlockingCall(MAY_BLOCK).
I kindly ask the reviewer to make sure of the following:
  - ScopedBlockingCall is instantiated in a scope with minimal CPU usage.
    If this is not the case, ScopedBlockingCall should be instantiated
    closer to the blocking call. See scoped_blocking_call.h for more
    info. Please let me know when/where the blocking call happens if this needs
    to be changed.
  - Parameter |blocking_type| matches expectation (MAY_BLOCK/WILL_BLOCK). See
    BlockingType for more info. While I assumed MAY_BLOCK by default, that might
    not be the best fit if we know that this callsite is guaranteed to block.
  - The ScopedBlockingCall's scope covers the entirety of the blocking operation
    previously asserted against by the AssertBlockingAllowed().

This CL was uploaded by git cl split.

R=reillyg@chromium.org

Bug: 874080
Change-Id: I0ee2ff9b2a81c101f943716b4965d4f21f231e41
Reviewed-on: https://chromium-review.googlesource.com/1191322Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594140}

Make them available to other unit tests.

Change-Id: If1166a9611b4b5455440ceb75c449f61e4cbb8ce
Reviewed-on: https://chromium-review.googlesource.com/1244112
Commit-Queue: Lei Zhang <thestig@chromium.org>
Reviewed-by: Henrique Nakashima <hnakashima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594139}

Bug: 886975
Change-Id: Ic4717d4fc2fbac73137f65154b3055332f9c23ed
Reviewed-on: https://chromium-review.googlesource.com/1244612Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Becky Zhou <huayinz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594138}

Currently only 'position: absolute' uses the padding area of the
containing block in 'top' and 'bottom' properties, 'position: fixed'
uses the content area instead.

The change only affects the value returned by getComputedStyle, the used
value was already correct.

BUG=883585

TEST=external/wpt/css/cssom/getComputedStyle-insets-fixed.html

The test still has some failures due to http://crbug.com/883582,
http://crbug.com/883574 and http://crbug.com/888532.

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: I91a07472026f50cb60e0225a4e8edd515c04ec6a
Reviewed-on: https://chromium-review.googlesource.com/1240124
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594137}

Profiles are unneeded since the changes to use AutomationEventRouter. Previously, we went through the extension system's routing layer, which required a context.

Bug: 888152
Change-Id: I57260ad0507267fee94d6764464b18a141d3b09e
Reviewed-on: https://chromium-review.googlesource.com/1239265
Commit-Queue: David Tseng <dtseng@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594136}

BUG=880210

Change-Id: I44e80bc0866fef5370936db3f2cb4d3eacf620f2
Reviewed-on: https://chromium-review.googlesource.com/1241094Reviewed-by: Leonard Grey <lgrey@chromium.org>
Reviewed-by: Mike Wittman <wittman@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594135}

Use the RenderWidgetResizeHelper's task runner to handle the mojo
messages to and from the BridgedNativeWidget and
BridgedNativeWidgetHost.

Bug: 859152
Change-Id: I3d9fab6cd81edafd74e45d06c658d1bd15e1fde4
Reviewed-on: https://chromium-review.googlesource.com/1244103
Commit-Queue: Sidney San Martín <sdy@chromium.org>
Reviewed-by: Sidney San Martín <sdy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594134}

With User Activation V2, the click activation is carried on to the
following tests since the state is no longer stack-scoped. By
re-ordering tests, this CL makes sure test doesn't fail when User
Activation V2 is enabled.

Bug: 860718
Change-Id: I54ebc6ca2d808323e4b87997b9687c56e2c8606d
Reviewed-on: https://chromium-review.googlesource.com/1244239
Commit-Queue: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594133}

Bug: 878581
Change-Id: I65fc0029da2e3951495a6cd96704085e5c1b942c
Reviewed-on: https://chromium-review.googlesource.com/1227366Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594132}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/29788f1ac1da..89ae8c86b8c8


Created with:
  gclient setdep -r src-internal@89ae8c86b8c8

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.



BUG=chromium:868213
TBR=mmoss@chromium.org

Change-Id: Ib90caca078f76ca4972dbefc844348541a2ae32b
Reviewed-on: https://chromium-review.googlesource.com/1244717Reviewed-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@{#594131}

In Android, accessibility services can respect the |isImportantForAccessibility| property.

Chrome-side, this best matches the concept of an ignored role.

In particular, this means, during linear navigation, a service should ignored this node while looking for the next directed node to visit.

Note that this should have no impact on descendants, unless, of course, they also have isImportantForAccessibility set to false.

Bug: 889074
Change-Id: I33ace3fc1e88450a9d2ce3798bd92feed2e08a19
Reviewed-on: https://chromium-review.googlesource.com/1243486Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594130}

Move some of the static methods in DisplayLinkMac to be anonymous
namespace methods in the cc file, and add comments clarifying their
usage.

Remove the DCHECK ensuring that the initially-captured main thread task
runner be equal to the current main thread task runner, and add a
comment indicating that this may not always be the case.

Bug: 885329
Change-Id: Idfdeb3ba1d20840161f26669e19bdee42aa155c5
Reviewed-on: https://chromium-review.googlesource.com/1234229Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594129}

Swarming mixins had not been used by gpu tests. This CL makes them work,
and adds a test case.

Bug: 871872
Change-Id: I914e16ab57ad3b514cf263f18e0fff195a0f37d8
Reviewed-on: https://chromium-review.googlesource.com/1244172Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Stephen Martinis <martiniss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594128}

This is a preparation step before we add AV1 support.

- Remove container from codec enum names.
- EME_CODEC_WEBM_VP9 -> EME_CODEC_LEGACY_VP9 to differentiate from
  EME_CODEC_VP9, which is for the new multi-part VP9.
- DV -> DOLBY_VISION for better readability.

Bug: 884898
Test: No functionality change.
Change-Id: I23117298ca604c0266487c637cacebdfd6884942
Reviewed-on: https://chromium-review.googlesource.com/1240502Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Reviewed-by: John Rummell <jrummell@chromium.org>
Commit-Queue: Xiaohan Wang <xhwang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594127}

New acorn support couple nice ES features, e.g.,
- for await (...) loop,
- spread operator.

R=lushnikov@chromium.org

Bug: chromium:863656
Change-Id: I057ebf01fcc220ee1e98707343df457358f248f6
Reviewed-on: https://chromium-review.googlesource.com/1244600
Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org>
Reviewed-by: Andrey Lushnikov <lushnikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594126}

This callback allows Java to fetch a favicon for a site from the native code.

Change-Id: Id4a8d86f68ade3b48e0f0dc937fa4b19c3ba8a50
Reviewed-on: https://chromium-review.googlesource.com/1241694
Commit-Queue: Jonathan Freed <freedjm@chromium.org>
Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594125}

If the error is caused by a suspend (or some other kill), it will get
delivered to URLLoader while there may still be live use in a disk_cache
layer write.

Bug: 882246, 881493, 884692
Cq-Include-Trybots: luci.chromium.try:linux_mojo
Change-Id: Ic4f46b8f358940418045351e3f41bb29ef13d05b
Reviewed-on: https://chromium-review.googlesource.com/1240518
Commit-Queue: Maks Orlovich <morlovich@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594124}

Change-Id: I0fe4991ff74227084f179282e9f1d12f471e6bc0
Reviewed-on: https://chromium-review.googlesource.com/1244603Reviewed-by: Doug Arnett <dougarnett@chromium.org>
Commit-Queue: Ryan Sturm <ryansturm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594123}

https://pdfium.googlesource.com/pdfium.git/+log/30dc6aaf878b..9412c8ec36d1


git log 30dc6aaf878b..9412c8ec36d1 --date=short --no-merges --format='%ad %ae %s'
2018-09-25 thestig@chromium.org Get rid of "exceptions" in CBC_QRCoderMatrixUtil.
2018-09-25 thestig@chromium.org Roll third_party/freetype/src/ dfddc2d97..abd997aa7 (9 commits)
2018-09-25 thestig@chromium.org Revert "Remove unreachable code in CPDF_DIBBase."


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

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.



BUG=chromium:888743
TBR=dsinclair@chromium.org

Change-Id: I81e542c61d7966800fd2d4efc2fc4a8f04e8cacc
Reviewed-on: https://chromium-review.googlesource.com/1244115Reviewed-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@{#594122}

Tracking pixel images are small in general and would fit in the 2KB
placeholder image. But it could be double fetched if it gets near the
viewport, before the placeholder range response is received.

One heuristic is to avoid lazyloading image elements with small dimensions
(10x 10) specified in attributes. This CL implements this.

Bug: 875086
Change-Id: I70149e5d57ee7e6216238d84bbdc9d24ee9114fd
Reviewed-on: https://chromium-review.googlesource.com/1198562
Commit-Queue: rajendrant <rajendrant@chromium.org>
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#594121}

Whenever a Preview is shown, the toolbar and status bar color of a CCT
should be set back to the default white color. Note that this may cause
a previously colored CCT to reset to white but that this is intentional
from a UX perspective to bring attention to the fact that the page is a
Preview and to be consistent with the UX of a regular Chrome tab.

Bug: 886947
Change-Id: I763af3315d16d49921c445833234beeb8a4829a9
Reviewed-on: https://chromium-review.googlesource.com/1239033
Commit-Queue: Robert Ogden <robertogden@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594120}

Fieldsets with "contain: size" were not ignoring the legend
when determining their size.

Spec (https://drafts.csswg.org/css-contain/#containment-size):
  "When calculating the size of the containing element,
   it must be treated as having no contents."

The patch is just an early return in
LayoutFieldset::ComputePreferredLogicalWidths()
like we have in other parts of the code.

BUG=882388
TEST=external/wpt/css/css-contain/contain-size-fieldset-001.html

Change-Id: I79425cf9c10ecf794f52cb4f635b95e1be059d81
Reviewed-on: https://chromium-review.googlesource.com/1242357
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594119}

Move the "common" dependencies that are used by all
system_webview_apk_tmpl users into the actual template to avoid
repeating them in multiple places (upstream and downstream), and move
the ones that are only used upstream into a variable to make it clearer
that developers shouldn't add new dependencies to the target itself.

This avoids mistakes where the dependency list upstream and downstream
can get out of sync, and will allow Trichrome to reuse the dependencies
as well.

Change-Id: I415180dd42915ba7ea3cc271f330d97b4e250b23
Reviewed-on: https://chromium-review.googlesource.com/1240976Reviewed-by: Changwan Ryu <changwan@chromium.org>
Commit-Queue: Richard Coles <torne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594118}

The observer is expected to be called at most/exactly once, so make
the observer type OnceClosure instead of (Repeating)Closure.

Bug: None
Test: None
Change-Id: I033ec5ac31b989d96944f5e68373ff1ef79604c7
Reviewed-on: https://chromium-review.googlesource.com/1244098Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: Istiaque Ahmed <lazyboy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594117}

Add timeouts to TestExpectations of:

* http/tests/devtools/coverage/gutter-css.js
* http/tests/devtools/editor/text-editor-enter-behaviour.js

TBR=pbos@chromium.org

Bug: chromium:850358, chromium:888609
Change-Id: I5bcae8612733ffbbf3f953ff668ccc0a2a8eebc9
Reviewed-on: https://chromium-review.googlesource.com/1244368
Commit-Queue: Peter Boström <pbos@chromium.org>
Reviewed-by: Peter Boström <pbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594116}

When we specify will-change: opacity, it is a hint to the browser that
opacity will change. In order to make this perform well, we should
induce an effect node so that we don't have to repaint when the
opacity actually changes. This patch makes it so.

R=pdr@chromium.org, wangxianzhu@chromium.org

Bug: 886389
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: If0979d48f322564d61ad8434eb4435fc8e8f2602
Reviewed-on: https://chromium-review.googlesource.com/1240993
Commit-Queue: vmpstr <vmpstr@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594115}

The paint team has no insight into what proportion of the
Blink complete main frame time is spent in Blink lifecycle
operations vs. script required updates vs. other tasks.
This CL adds metrics that will allow for identifying the
proprtion of main frame time taken by various operations.

Bug: 869966
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Idc73dc6efd1aef5e65df647bc48de84384dba0c8
Reviewed-on: https://chromium-review.googlesource.com/1179995Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Robert Kaplow (sloooow) <rkaplow@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: vmpstr <vmpstr@chromium.org>
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594114}

AXAuraObjCache::GetOrCreate(View* view) can return null if the View
is not yet associated with a Widget. The shortcut viewer creates a
ScrollView that creates a FocusRing before the ScrollView is attached
to the Widget.

Do what AutomationManagerAura does in this case and just don't send
accessibility event updates for these unattached views.

Bug: 889121
Test: added to views_mus_unittests
Change-Id: Ica14908778e45b9b4ee06077bd31c92fb7dfca62
Reviewed-on: https://chromium-review.googlesource.com/1244456Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594113}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/be0a57bc9068..29788f1ac1da


Created with:
  gclient setdep -r src-internal@29788f1ac1da

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.


TBR=mmoss@chromium.org

Change-Id: Ib23f9c4362ab5ea4dbd10bbbcdef4830dd57bdb1
Reviewed-on: https://chromium-review.googlesource.com/1244162Reviewed-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@{#594112}

https://chromium.googlesource.com/angle/angle.git/+log/b36a4816a546..299bdfe75173


git log b36a4816a546..299bdfe75173 --date=short --no-merges --format='%ad %ae %s'
2018-09-25 jmadill@chromium.org Vulkan: Update AMD suppressions.


Created with:
  gclient setdep -r src/third_party/angle@299bdfe75173

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@chromium.org

Change-Id: Ica8d861ce6d637b976fe7f9eda34a66ff48cb4a0
Reviewed-on: https://chromium-review.googlesource.com/1244139Reviewed-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@{#594111}

This reverts commit bc94af5f.

Reason for revert: <INSERT REASONING HERE>

Original change's description:
> Updating blacklist/README.md
> 
> This reflects changes in
> https://chromium-review.googlesource.com/c/chromium/src/+/1225095 that
> added Bloom filter to the blacklist component.
> 
> Change-Id: Icfb9e266a54c88c5306811feec07d30df0a63680
> Reviewed-on: https://chromium-review.googlesource.com/1225491
> Commit-Queue: Ryan Sturm <ryansturm@chromium.org>
> Reviewed-by: Doug Arnett <dougarnett@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#591204}

TBR=dougarnett@chromium.org,ryansturm@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Change-Id: I3c7417dd04e78e437928b432b7100d21c92631de
Reviewed-on: https://chromium-review.googlesource.com/1244400Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Commit-Queue: Ryan Sturm <ryansturm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594110}