GitLab

Simplifies testVrIntentStartsVrShell and test2dIntentExitsVrShell.

Change-Id: I9a8b6413741afab62f03ffb667969c30821f93a3
Reviewed-on: https://chromium-review.googlesource.com/1113757Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570075}

Use a map to track pressed keys. The key for the map is the physical
code that was pressed and the value is a potentially rewritten code.

This allows us to generate appropriate release events when physical
keys are released, while still allowing the event rewriting logic
to work as expected.

Note: Exo clients will always see a release for the same code as
the code that was generated when the physical key was pressed. This
is necessary in order to not break client side keyboard state
tracking and might not match the events that are generated internally.
That is because event rewrite logic is usually not rewriting both the
press and the release events, often just the press event.

Bug: 847500
Test: exo_unittests --gtest_filter=KeyboardTest.OnKeyboardKey
Tbr: hidehiko@chromium.org
Change-Id: I23240304bd377e3855971edd079ade1b537a74f9
Reviewed-on: https://chromium-review.googlesource.com/1112967Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Commit-Queue: David Reveman <reveman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570074}

https://android.googlesource.com/platform/external/perfetto.git/+log/82901f0040da..c6347f057d3a


git log 82901f0040da..c6347f057d3a --date=short --no-merges --format='%ad %ae %s'
2018-06-25 lalitm@google.com trace_processor: fix memory leaks in sched slice tests
2018-06-25 treehugger-gerrit@google.com Merge "trace_processor: add unit and integration tests for sched slice table"
2018-06-25 treehugger-gerrit@google.com Merge "trace_processor: fix gcc build"
2018-06-25 lalitm@google.com trace_processor: add unit and integration tests for sched slice table
2018-06-25 lalitm@google.com trace_processor: fix gcc build


Created with:
  gclient setdep -r src/third_party/perfetto@c6347f057d3a

The AutoRoll server is located here: https://perfetto-chromium-roll.skia.org

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:80416541,chromium:80416541,chromium:80416541
TBR=perfetto-bugs@google.com

Change-Id: I22d8e88796ae0c26c571b4e169f2f220799dfdf1
Reviewed-on: https://chromium-review.googlesource.com/1113818
Reviewed-by: <perfetto-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: <perfetto-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#570073}

RenderWidgetHostViewAura should use IsMouseLocked instead of
mouse_locked_ because the locked state is stored in RWHV_event_handler.

Remove mouse_locked_ from the base class to prevent misuse.

Bug: 812964
Change-Id: I5201c7b6d77d1e52f9da2344899b6ab293e44f86
Reviewed-on: https://chromium-review.googlesource.com/1102911Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Ella Ge <eirage@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570072}

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

Update the location string, not only the security icon, when the
security state changes to indicate correct URL on interstitials.

Bug: 853332
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I3ba5e7dcaf26945f394892354127be01fa9564a7
Reviewed-on: https://chromium-review.googlesource.com/1113744
Commit-Queue: Stepan Khapugin <stkhapugin@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570070}

Describe what makes a good report.

Change-Id: Ia76e5eea68cd4ed490d0282662db432c7167cab3
Reviewed-on: https://chromium-review.googlesource.com/1110274
Commit-Queue: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Chris Palmer <palmer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570069}

Bug: 855883
Change-Id: I208dab13ef989714b5385b92a70fb70155bddf3c
TBR: mlamouri@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/1113897Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Commit-Queue: Mounir Lamouri <mlamouri@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570068}

Rather than waiting for the page flip event to return the status, return
it right after it's determined, which is immediately after submitting the
page flip to the kernel. This requires splitting the page flip callback
into two callbacks, one that takes the status and one that takes the
presentation feedback. This should be familiar as the GLSurface API has
exactly the same separation.

This does not actually change when GbmSurfaceless passes the ACK along,
so there should be no visible change. Changing when the ACK is returned
from GbmSurfacless can be done but would also require changes to
viz::BufferQueue.

Bug: 851997
Test: unit tests, CrOS still renders

Change-Id: Ided422ca3065e431ca8c9a5909b3faae72d97cc5
Reviewed-on: https://chromium-review.googlesource.com/1104863Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Commit-Queue: Michael Spang <spang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570067}

This tests when the inline-size is [min-content]:
* A `­` produces a break opportunity when computing the
  min-content inline size.
* The hyphen character generated by `­` is included into
  the min-content inline size.

Originally developed in [CL:1111895].

[min-content]: https://www.w3.org/TR/css-sizing-3/#valdef-width-min-content
[CL:1111895] https://chromium-review.googlesource.com/c/chromium/src/+/1111895

Bug: 636993
Change-Id: Ib492b2db023a5169247ca00e5b745e42ec33d197
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Reviewed-on: https://chromium-review.googlesource.com/1113085
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570066}

Consider two views: A and its child view B.

The "Views::Layout" trace event for B is currently emitted when A calls
B's Layout as part of A's Layout. This is less intuitive than calling it
in B's Layout, but is better because it can capture an event for a B
which doesn't call through to the base class Layout implementation in
its Layout.

Unfortunately, this still leaves many gaps:
1) Layout managers
2) Views whose *parents* don't call the base class implementation
3) Layouts triggered by bounds changes
4) Probably some more I can't think of right now.

This change adds extra trace events to address #3 from the list above.

Bug: 850128, 835983
Change-Id: I135ac0e8b2c6b9e277dce6da06e9d0aeae7dfbd1
Reviewed-on: https://chromium-review.googlesource.com/1112466
Commit-Queue: Leonard Grey <lgrey@chromium.org>
Reviewed-by: Robert Liao <robliao@chromium.org>
Reviewed-by: Trent Apted <tapted@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570065}

This patch removes an optimization added in [1] to not invalidate
graphics layers when the offset from layout object changes. This
offset is no longer used for scroll offset so the original intent
no longer applies [2]. Removing this optimization causes an additional
invalidation in a rare case (vertical writing mode scroll origin
changes) but reduces complexity in a difficult area of code.

This patch also removes a SetNeedsDisplay of the scrolling contents when
the scroll layer's offset changes. The scrolling contents layer is now
only invalidated if the offset actually changes. No tests were affected
by this change.

In addition, all callsites were setting the offset_from_layout_object_
to an IntSize, so the type has been updated from DoubleSize to IntSize.

[1] https://trac.webkit.org/changeset/134628/webkit
[2] https://chromium.googlesource.com/chromium/src/+/0241ab94255bdc1fcb0c84b6cd2a0937ecf9fb90

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

https://webrtc.googlesource.com/src.git/+log/3ecec176a825..8396e3498fd4


git log 3ecec176a825..8396e3498fd4 --date=short --no-merges --format='%ad %ae %s'
2018-06-25 aleloi@webrtc.org Remove APM limiter in Audio Mixer.
2018-06-25 minyue@webrtc.org Adding jitter buffer plots for all SSRCs in event log visualizer.
2018-06-25 titovartem@webrtc.org Extract third party part of g722 codec into separate target


Created with:
  gclient setdep -r src/third_party/webrtc@8396e3498fd4

The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org

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:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: I3dd1ca3fdf095e61da98ab391ed06554b55d0bdf
Reviewed-on: https://chromium-review.googlesource.com/1113817Reviewed-by: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#570063}

Bug: 853329
Change-Id: Icde8c71cd03fcec6bf2c4d2b97cca580fdc98c52
Reviewed-on: https://chromium-review.googlesource.com/1103060Reviewed-by: agrieve <agrieve@chromium.org>
Commit-Queue: Sam Maier <smaier@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570062}

ShapingLineBreaker handles trailing spaces at the end of
wrapped lines. But when the line ends with hard break or at
the end of a block, NGLineBreaker needs to remove the
trailing spaces.

When the trailing space is not safe-to-break; e.g., the font
has kerning pairs between the last non-space character and
the trailing spaces, this patch ensures that the line width
is correct by reshaping the end.

Not doing so caused min-content and max-content differ when
there are no break opportunities, because trailing spaces for
min-content is handled by ShapingLineBreaker while for max-
content is handled by NGLineBreaker.

Bug: 636993
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: If8c810b7e4cfccfd7a35f6dd48d15ce67b98c036
Reviewed-on: https://chromium-review.googlesource.com/1111749
Commit-Queue: Emil A Eklund <eae@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570061}

This CL removes some unneeded ash includes and fixes the only ash
vector icon dependency in src/chrome.

Bug: 798569
Change-Id: I17acd7fb17dc5716f639606b7da31f7e123a13ad
Reviewed-on: https://chromium-review.googlesource.com/1110997Reviewed-by: Evan Stade <estade@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570060}

  In order to roll GN a3bcd204..7f29218b (r567268:r570036) and pick up
  the following changes:

  5321951e Change "gn check" to report all incorrect include
  6955d08c [gn] Doc: Fix toochain typo and clarify the toolchain syntax.

TBR=dpranke@chromium.org

Change-Id: I74be13541e722d5ad5fd8199e6242928ffb084d2
Reviewed-on: https://chromium-review.googlesource.com/1113747Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Sylvain Defresne <sdefresne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570059}

We should reset last text node seen by the whitespace attacher when
entering an option or optgroup element. We normally do that when we see
a layout object, but these element do not have layout objects. We
incorrectly treated them as display:contents during layout tree
rebuild.

This caused a fuzzer DCHECK failure in WhitespaceAttacher where we did
not reset the WhitespaceAttacher for an optgroup which we thought were
a display:contents but not registered as one in the WhitespaceAttacher.

Bug: 855949
Change-Id: I5c341a3f47a4e76216db6f712ecacfc939b5f7fa
Reviewed-on: https://chromium-review.googlesource.com/1113339Reviewed-by: Anders Ruud <andruud@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570058}

Later attempts to perform this initialization seem to fail
potentially because of a dlopen() bug, so perform the
initialization early, right after dlopen() on libcronet
succeeded.

Bug: 853725
Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I9132dff672f91d7962909531f01c6bada4fee964
Reviewed-on: https://chromium-review.googlesource.com/1110377Reviewed-by: Andrei Kapishnikov <kapishnikov@chromium.org>
Reviewed-by: Adenilson Cavalcanti <cavalcantii@chromium.org>
Commit-Queue: Paul Jensen <pauljensen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570057}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/b1475672..cc00dcbd

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_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;luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org

Change-Id: I3d52fb9e32fcf9bae295394bc971b39ac142605b
Reviewed-on: https://chromium-review.googlesource.com/1113499Reviewed-by: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#570056}

BUG=85144
TBR=tedchoc@chromium.org

Change-Id: I675926ce3b3fe445b5d329e2cf0b7958960b2bd4
Reviewed-on: https://chromium-review.googlesource.com/1113801Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570055}

It appears this was missed in https://chromium-review.googlesource.com/1091504
because it was listed separately.

TBR=flackr@chromium.org
BUG=762717

Change-Id: Id0fce202ec87376003b96e448c22f3e9ed7e0de2
Reviewed-on: https://chromium-review.googlesource.com/1113500Reviewed-by: Peter Mayo <petermayo@chromium.org>
Commit-Queue: Peter Mayo <petermayo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570054}

Some of CallbackBase constructors has small bodies that is even smaller
than their size of the invocation set up.
This CL marks such constructors as inline for smaller binary size, and
reduces the stripped binary size of chrome on linux by 156kB.

Change-Id: I95999f4aebda6bc886dcfb66bc284ec0d42ccc86
Reviewed-on: https://chromium-review.googlesource.com/1113088Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570053}

https://skia.googlesource.com/skia.git/+log/900b5364d12e..c050a1a185bf


git log 900b5364d12e..c050a1a185bf --date=short --no-merges --format='%ad %ae %s'
2018-06-25 caryclark@skia.org fix pathop fuzz timeout
2018-06-25 csmartdalton@google.com ccpr: Blacklist PowerVR Rogue in GL
2018-06-25 robertphillips@google.com Fix abandonment of programs


Created with:
  gclient setdep -r src/third_party/skia@c050a1a185bf

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

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=master.tryserver.blink:linux_trusty_blink_rel;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

BUG=chromium:855751
TBR=jcgregorio@chromium.org

Change-Id: I0a0c1caa01189dcb6eabc028f9f698df2d07e3d0
Reviewed-on: https://chromium-review.googlesource.com/1113479Reviewed-by: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#570052}

Custom backgrounds should only be applied when Google is set
as the search provider. Adds ApplyGoogleNtpThemeElements to
set/unset the background as needed.

Bug: 851290
Change-Id: I2fa7ca1081df818b455df27d1496047b0a800765
Reviewed-on: https://chromium-review.googlesource.com/1112379Reviewed-by: Marc Treib <treib@chromium.org>
Commit-Queue: Kyle Milka <kmilka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570051}

This reverts commit 040f2ad0.

Reason for revert: <INSERT REASONING HERE>

Original change's description:
> Fork AudioInputController to the audio service.
> 
> Also migrate the audio service to it. We want to add audio processing
> capabilities to the audio service, and the media/ code cannot depend
> on services/audio/, so we need the AudioInputController code in the
> audio service. There's a very sketched design doc for processing in the
> audio service at
> https://docs.google.com/document/d/1HJnii4kuBXshVM202TVPJt_9iDmlaCX-VhatjRxRbC4/edit#.
> 
> Bug: 851959
> Change-Id: Icabef727e6d309f86472d2fb401d7383051fa0ae
> Reviewed-on: https://chromium-review.googlesource.com/1104464
> Commit-Queue: Max Morin <maxmorin@chromium.org>
> Reviewed-by: Olga Sharonova <olka@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#570014}

TBR=olka@chromium.org,maxmorin@chromium.org

Change-Id: I3727f7454ec28718e327335baec3960365afbe93
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 851959,856215
Reviewed-on: https://chromium-review.googlesource.com/1113837Reviewed-by: Peng Huang <penghuang@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570050}

Change-Id: If9ceedf3c360c2a52bc7fd582707c90c7646fb8d
Reviewed-on: https://chromium-review.googlesource.com/1112472Reviewed-by: Mike Reed <reed@chromium.org>
Reviewed-by: Robert Phillips <robertphillips@google.com>
Commit-Queue: Greg Daniel <egdaniel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570049}

WebStatePolicyDecider::ShouldAllowResponse is now called when going back
after the form submission. Updated test expectation to match new
behavior.

Bug: 854615
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Icd3357750f56e9f4cac5a158fdd8aeb54dbf6c4b
Reviewed-on: https://chromium-review.googlesource.com/1113449Reviewed-by: Justin Cohen <justincohen@chromium.org>
Commit-Queue: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570048}

This moves message size metrics to be before IPC (and before
truncation) and removes three metrics.

JSDialogs.CountOfJSDialogMessageCharacters is removed;
JSDialogs.CharacterCount.MainFrame/Subframe is replacing it.

JSDialogs.CountOfJSDialogMessageNewlines is not useful as
we do rectangular truncation.

JSDialogs.CharacterCountUserSuppressed was just broken as it
was gated by "if (did_suppress_message)", and
"did_suppress_message" was a non-null bool pointer.

BUG=804081

Change-Id: I874e0aebf545096939dc12299843ba85a6dad121
Reviewed-on: https://chromium-review.googlesource.com/1112471Reviewed-by: Leonard Grey <lgrey@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570047}

Start of support for screen magnification on chromecast. Consists of:

   * A port of PartialMagnificationController from Ash to Cast. Note
     that the first patchset is a direct copy, with modifications in
     subsequent patch sets, so a diff with patchset 1 will show the
     modifications made.

   * A base interface (MagnificationController) for implementations,
     as we will probably port fullscreen magnification as well.

   * Installation of the PartialMagnificationController on the root
     window via the window manager, but currently disabled.

Bug: internal b/110481596
Bug: internal b/110532452
Test: manual and unit test
Change-Id: Ia72f9b662304f5b5b3864c7fdfa7012677bfe883
Reviewed-on: https://chromium-review.googlesource.com/1111904
Commit-Queue: Ryan Daum <rdaum@chromium.org>
Reviewed-by: Alex Sakhartchouk <alexst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570046}

Disable libaom long enough to make it into a nightly build.
This will allow us to determine the binary impact on official
builds.

BUG=chromium:851691
TBR=tomfinegan@chromium.org
CC=dalecurtis@chromium.org

Change-Id: Id22aba8d9f59c93a930ca64efa238c3138b61fc1
Reviewed-on: https://chromium-review.googlesource.com/1113518Reviewed-by: Johann Koenig <johannkoenig@google.com>
Commit-Queue: Johann Koenig <johannkoenig@google.com>
Cr-Commit-Position: refs/heads/master@{#570045}

Change-Id: Ifadcbeb60007662da55832c5e20e8c4b9433a0ec
Reviewed-on: https://chromium-review.googlesource.com/1113549
Commit-Queue: Pavel Feldman <pfeldman@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Reviewed-by: Eric Seckler <eseckler@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570044}

LowPriorityForSubFrameThrottleableTask study isn't using is_subframe
signal. That is, all throttleable tasks are assigned low priority
regardles of the type of the frame.

Change-Id: I1e924ef483b458a9b0d21e81a91d275901b9cb37
Reviewed-on: https://chromium-review.googlesource.com/1112248
Commit-Queue: Farah Charab <farahcharab@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570043}

https://webrtc.googlesource.com/src.git/+log/bdee46d275a3..3ecec176a825


git log bdee46d275a3..3ecec176a825 --date=short --no-merges --format='%ad %ae %s'
2018-06-25 titovartem@webrtc.org Extract third party part of g711 codec into separate target
2018-06-25 hta@webrtc.org Ensure that PC usage is recorded if a PC is alive for 60 seconds.


Created with:
  gclient setdep -r src/third_party/webrtc@3ecec176a825

The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org

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:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng

BUG=chromium:718508
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: Iee0e5bb9cd87a73f9bb556a0bc7320016e03bfad
Reviewed-on: https://chromium-review.googlesource.com/1113480Reviewed-by: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#570042}

This worker function is designed to test the behaviour of the
partition allocator by restricting the amount of memory available and
then intentionally exhausting it. Doing this leaves some of the global
state associated with the allocator in a bad state. Thus these tests
are non-hermetic. This Cl wraps up the call to the work function in a
EXPECT_DEATH to force the test to be run its own process, which
prevents the tests from poluting other tests.

This removes the need to have them in their own class and eliminates
the flakiness being seen, since run order no longer affects the
viability of future test cases.

BUG=chromium:851148

Change-Id: I6d63b769d73c0e725a4e0c811d816b62ad15d57b
Reviewed-on: https://chromium-review.googlesource.com/1106602Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Commit-Queue: Ryan Harrison <rharrison@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570041}

Change-Id: I6fb5914ede0c6741284b9962afb269a8c51ff175
Bug: 852517, 855630
Reviewed-on: https://chromium-review.googlesource.com/1099602
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Reviewed-by: Matt Reynolds <mattreynolds@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570040}

The MSAN bots are significantly faster in recent days (speed increased
more than 30%). Re-enable the OpenImageFiles browser test on MSAN.

Tbr: fukino-san, slangley
Bug: 836254
Change-Id: Id83c665e11ebb65f9dee79e354baba80be8ae52d
Reviewed-on: https://chromium-review.googlesource.com/1113637Reviewed-by: Noel Gordon <noel@chromium.org>
Commit-Queue: Noel Gordon <noel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570039}

The MSAN bots are significantly faster in recent days (speed increased
more than 30%). Re-enable the OpenAudioFiles browser test on MSAN.

Tbr: fukino-san, slangley
Bug: 836254
Change-Id: Id5757c7f462c1cd5adb117c46718867ad90916d5
Reviewed-on: https://chromium-review.googlesource.com/1113561Reviewed-by: Noel Gordon <noel@chromium.org>
Commit-Queue: Noel Gordon <noel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570038}

This struct includes authenticated_account_id, which several bridges are
interested in. This is safer and simpler to use compared to reading
from side channels, and prevents a runtime dependency cycle across some
factories.

TBR=estade@chromium.org,rockot@chromium.org

Bug: 850428,834042,854446
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Ib17a4503ff9d284e1a5f4e222e7eeb95b08a024f
Reviewed-on: https://chromium-review.googlesource.com/1111716
Commit-Queue: Mikel Astiz <mastiz@chromium.org>
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Reviewed-by: vitaliii <vitaliii@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Reviewed-by: Christian Dullweber <dullweber@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570037}

Roll in https://github.com/web-platform-tests/wpt/pull/11403 to support
a new feature which fixes the two recently imported infra tests.

Bug: 855395
Change-Id: Ie7439f714fc82fb280bdc4667e6bdb143ffc705c
Reviewed-on: https://chromium-review.googlesource.com/1112562Reviewed-by: Quinten Yearsley <qyearsley@chromium.org>
Commit-Queue: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#570036}