GitLab

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/eb5390d22252..a95071710cf8

$ git log eb5390d22..a95071710 --date=short --no-merges --format='%ad %ae %s'
2016-12-15 aiolos Roll the Chrome reference build for Canary/Dev.
2016-12-15 benjhayden Rename TelemetryInfo.addToValue() to addToHistogram().
2016-12-15 benjhayden Add BuildbotInfo Diagnostic.
2016-12-15 benjhayden Rename RelatedValueSet, RelatedValueMap to RelatedHistogramSet, RelatedHistogramMap.

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

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=catapult-sheriff@chromium.org

Review-Url: https://codereview.chromium.org/2584453004
Cr-Commit-Position: refs/heads/master@{#439066}

Cr-Commit-Position: refs/heads/master@{#439065}

Reland of Getting rid of CompositorFrameMetadata::satisfies_sequences (patchset #1 id:1 of https://codereview.chromium.org/2585543003/ )

Reason for revert:
Relanding this. The real culprit was https://codereview.chromium.org/2578893003/.

Original issue's description:
> Revert of Getting rid of CompositorFrameMetadata::satisfies_sequences (patchset #17 id:380001 of https://codereview.chromium.org/2537943002/ )
>
> Reason for revert:
> Suspected cause of ChromiumOS compile failure.
> https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Builder%20%28dbg%29/builds/81640
>
> Original issue's description:
> > Getting rid of CompositorFrameMetadata::satisfies_sequences
> >
> > This CL helps unify the way we destroy references to surfaces.
> > We currently have two code paths for satisfying a surface sequence.
> > One is through calling the satisfy callback which is given to the
> > reference holder, and the other one is through populating
> > satisfies_sequences in CompositorFrameMetadata and letting
> > Surface::QueueFrame do the rest of the work. Eventually they both do
> > the same thing: they call SurfaceManager::DidSatisfySequences. This CL
> > gets rid of satisfies_sequences in CompositorFrameMetadata and from now
> > on the only way for satisfying a sequence is through the callback. This
> > is a necessary change because we are phasing out SurfaceSequence and
> > exposing it in CompositorFrameMetadata is not a good idea.
> >
> > BUG=659598
> > CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
> >
> > Committed: https://crrev.com/d0de6cf72a25d789a507d6eb904a8f1ae314d00b
> > Cr-Commit-Position: refs/heads/master@{#439043}
>
> TBR=fsamuel@chromium.org,danakj@chromium.org,dcheng@chromium.org,jbauman@chromium.org,dtrainor@chromium.org,jam@chromium.org,samans@chromium.org
> # Skipping CQ checks because original CL landed less than 1 days ago.
> NOPRESUBMIT=true
> NOTREECHECKS=true
> NOTRY=true
> BUG=659598
>
> Committed: https://crrev.com/f0983129357f6a46b29756ed183115b8dc8e371e
> Cr-Commit-Position: refs/heads/master@{#439051}

TBR=fsamuel@chromium.org,danakj@chromium.org,dcheng@chromium.org,jbauman@chromium.org,dtrainor@chromium.org,jam@chromium.org,samans@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=659598

Review-Url: https://codereview.chromium.org/2583803002
Cr-Commit-Position: refs/heads/master@{#439064}

Revert of Converts chrome to aura-mus (patchset #4 id:60001 of https://codereview.chromium.org/2578893003/ )

Reason for revert:
Broke Linux ChromiumOS Builder (dbg) build.
https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Builder%20%28dbg%29/builds/81640

Original issue's description:
> Converts chrome to aura-mus
>
> aura-mus has a different environment than mus, so WMHelperMus (in exo)
> was updated accordingly.
>
> This breaks switches::kUseMusInRenderer. I'll fix that next.
>
> BUG=672932 663525
> TEST=covered by tests
> R=reveman@chromium.org, sadrul@chromium.org
>
> Committed: https://crrev.com/e3e1ea3c0699e70c8ca5a6a790641c58be4e1381
> Cr-Commit-Position: refs/heads/master@{#439044}

TBR=reveman@chromium.org,sadrul@chromium.org,sky@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=672932 663525

Review-Url: https://codereview.chromium.org/2577963006
Cr-Commit-Position: refs/heads/master@{#439063}

SelectionPopupController.updateActionModeVisibility() is confusing and unnecessary.
This patch refactors code to remove it.

This shouldn't have any behavior changes because
|ContentViewCore.setTouchScrollInProgress()| can't be called if the selection is
being dragged. Likewise when the selection handle dragging stops there shouldn't be
a touch scroll in progress.

Review-Url: https://codereview.chromium.org/2581863002
Cr-Commit-Position: refs/heads/master@{#439062}

This is a requirement for adding a full saturated type implementation.

BUG=672489
NOTRY=true

Review-Url: https://codereview.chromium.org/2578613002
Cr-Commit-Position: refs/heads/master@{#439061}

Revert of Set number of shards for telemetry_unittests to be 2 (patchset #1 id:1 of https://codereview.chromium.org/2579793002/ )

Reason for revert:
telemetry_unittests failing on chromium.linux/Linux Tests (dbg)(1) and linux_chromium_rel_ng.
https://crbug.com/674788

Original issue's description:
> Set number of shards for telemetry_unittests to be 2
>
> This suite currently occasionally is timed out (its usual runtime is 20 minutes total), causing flaky failure
>
> BUG=661434
>
> Committed: https://crrev.com/45cada6244d0cc9c8798e6531d2c1ea0b90a5668
> Cr-Commit-Position: refs/heads/master@{#438859}

TBR=dpranke@chromium.org,maruel@chromium.org,nednguyen@google.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=661434

Review-Url: https://codereview.chromium.org/2583703003
Cr-Commit-Position: refs/heads/master@{#439060}

Review-Url: https://codereview.chromium.org/2379773002
Cr-Commit-Position: refs/heads/master@{#439059}

It's easy to change in the web interface, and I forgot hitting ":wq"
in vim for several minutes several times now.  Uploading without prompt
seems like the better tradeoff to me.

BUG=

Review-Url: https://codereview.chromium.org/2581113002
Cr-Commit-Position: refs/heads/master@{#439058}

BUG=

Review-Url: https://codereview.chromium.org/2585613002
Cr-Commit-Position: refs/heads/master@{#439057}

This CL skips the focus test that is likely the cause of failures and
reenables the test on all platforms.

BUG=640862

Review-Url: https://codereview.chromium.org/2582543005
Cr-Commit-Position: refs/heads/master@{#439056}

Many paint properties depend on piant offset but paint offset changes
currently only cause a local paint property update. The paint
invalidation system ensures the prepaint tree walk is not stopped
so this doesn't result in a bug today. This patch will prevent
paint offset changes from being missed in the future.

This patch also moves the paint offset check to PaintPropertyTreeBuilder.
Additionally, localContext has been renamed context to improve
readability.

BUG=645667
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2

Review-Url: https://codereview.chromium.org/2578393002
Cr-Commit-Position: refs/heads/master@{#439055}

These are now type-checked by compiler.

BUG=none

Review-Url: https://codereview.chromium.org/2580673002
Cr-Commit-Position: refs/heads/master@{#439054}

Renamed make_css_property_descriptor.py to make_css_property_api.py and
modified it so that it also generates API .h files. Added the template
file CSSPropertyAPI.h.tmpl.

To generate the .h file for a property, add the api_class flag to the
property in CSSProperties.in.

BUG=668012

Review-Url: https://codereview.chromium.org/2578773002
Cr-Commit-Position: refs/heads/master@{#439053}

Removes ScopedVector in favor of vector<unique_ptr>  in presentation_service_impl and related files as requested in Avi's
comment in https://codereview.chromium.org/2562603002/

BUG=554289

Review-Url: https://codereview.chromium.org/2574673002
Cr-Commit-Position: refs/heads/master@{#439052}

Revert of Getting rid of CompositorFrameMetadata::satisfies_sequences (patchset #17 id:380001 of https://codereview.chromium.org/2537943002/ )

Reason for revert:
Suspected cause of ChromiumOS compile failure.
https://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Builder%20%28dbg%29/builds/81640

Original issue's description:
> Getting rid of CompositorFrameMetadata::satisfies_sequences
>
> This CL helps unify the way we destroy references to surfaces.
> We currently have two code paths for satisfying a surface sequence.
> One is through calling the satisfy callback which is given to the
> reference holder, and the other one is through populating
> satisfies_sequences in CompositorFrameMetadata and letting
> Surface::QueueFrame do the rest of the work. Eventually they both do
> the same thing: they call SurfaceManager::DidSatisfySequences. This CL
> gets rid of satisfies_sequences in CompositorFrameMetadata and from now
> on the only way for satisfying a sequence is through the callback. This
> is a necessary change because we are phasing out SurfaceSequence and
> exposing it in CompositorFrameMetadata is not a good idea.
>
> BUG=659598
> CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
>
> Committed: https://crrev.com/d0de6cf72a25d789a507d6eb904a8f1ae314d00b
> Cr-Commit-Position: refs/heads/master@{#439043}

TBR=fsamuel@chromium.org,danakj@chromium.org,dcheng@chromium.org,jbauman@chromium.org,dtrainor@chromium.org,jam@chromium.org,samans@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=659598

Review-Url: https://codereview.chromium.org/2585543003
Cr-Commit-Position: refs/heads/master@{#439051}

Installation / updating via Google Play does not require "Installation from
Unknown Sources" to be enabled to work. This CL enables updating WebAPKs if the
update is done via Google Play regardless of whether "Installation from Unknown
Sources" is enabled.

BUG=662149

Review-Url: https://codereview.chromium.org/2555333002
Cr-Commit-Position: refs/heads/master@{#439050}

Ran `tools/clang/scripts/upload_revision.py 289864`.

BUG=674274

Review-Url: https://codereview.chromium.org/2585473003
Cr-Commit-Position: refs/heads/master@{#439049}

Instead of using generic stub objects, use actual
types, because that is more accurate.

R=bashi
BUG=673214

Review-Url: https://codereview.chromium.org/2581613002
Cr-Commit-Position: refs/heads/master@{#439048}

VideoDecodeAcceleratorCapabilities was missing the list of supported
profiles.

BUG=643746
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2579873002
Cr-Commit-Position: refs/heads/master@{#439047}

It was very confusing to filter all features in .tmpl file.
This CL make the context to have origin trial feature contexts
together with names and needs_instance.

Before:
features = [{name, needs_instance}]

After:
features = [{name, needs_instance,
             [constants], [attributes], [methods]}]

BUG=650150

Review-Url: https://codereview.chromium.org/2573713002
Cr-Commit-Position: refs/heads/master@{#439046}

https://skia.googlesource.com/skia.git/+log/d85dd53e288e..780dad1ab946

$ git log d85dd53e2..780dad1ab --date=short --no-merges --format='%ad %ae %s'
2016-12-15 bsalomon Rename "batch" to "op" and sk_sp in 3 path renderer classes:
2016-12-15 msarett Turn on srgb config on all bots, run image decode tests to srgb
2016-12-15 rmistry Blacklist SKPs for the 100k_IMG_DECODE bot
2016-12-15 scroggo Stop supporting kUnknown_BmpHeaderType
2016-12-15 mtklein simplify SkTHash* move support
2016-12-15 bsalomon Convert a few path renderer class batches from Batch to Op.
2016-12-15 scroggo Remove all KTX support
2016-12-15 ethannicholas Added SkLRUCache.h and converted GPU program cache to use it.

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

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
TBR=msarett@google.com

Review-Url: https://codereview.chromium.org/2583713003
Cr-Commit-Position: refs/heads/master@{#439045}

aura-mus has a different environment than mus, so WMHelperMus (in exo)
was updated accordingly.

This breaks switches::kUseMusInRenderer. I'll fix that next.

BUG=672932 663525
TEST=covered by tests
R=reveman@chromium.org, sadrul@chromium.org

Review-Url: https://codereview.chromium.org/2578893003
Cr-Commit-Position: refs/heads/master@{#439044}

This CL helps unify the way we destroy references to surfaces.
We currently have two code paths for satisfying a surface sequence.
One is through calling the satisfy callback which is given to the
reference holder, and the other one is through populating
satisfies_sequences in CompositorFrameMetadata and letting
Surface::QueueFrame do the rest of the work. Eventually they both do
the same thing: they call SurfaceManager::DidSatisfySequences. This CL
gets rid of satisfies_sequences in CompositorFrameMetadata and from now
on the only way for satisfying a sequence is through the callback. This
is a necessary change because we are phasing out SurfaceSequence and
exposing it in CompositorFrameMetadata is not a good idea.

BUG=659598
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel

Review-Url: https://codereview.chromium.org/2537943002
Cr-Commit-Position: refs/heads/master@{#439043}

This patch makes each LocalFrame own an IdleSpellCheckCallback. Future
patches will make this callback handle spell checking in the frame when
IdleTimeSpellChecking is enabled.

BUG=517298

Review-Url: https://codereview.chromium.org/2581063002
Cr-Commit-Position: refs/heads/master@{#439042}

When col/colgroup spans added up to exactly 2^32, the result would
overflow to 0, which was the divisor for a later operation.

This patch clamps col spans to 8190, matching cell colspans. This makes
the problem harder to trigger but doesn't eliminate it.

BUG=660581

Review-Url: https://codereview.chromium.org/2518163002
Cr-Commit-Position: refs/heads/master@{#439041}

BUG=none

Review-Url: https://codereview.chromium.org/2585453003
Cr-Commit-Position: refs/heads/master@{#439040}

This CL cleans up a selectedSite member and replaces it with a more
clear selectedSiteForUnitTest member.

BUG=None
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2580653003
Cr-Commit-Position: refs/heads/master@{#439039}

There were bugs in the handling of the result coming back from an editor. We now have improved logic around:
* Receiving |null| from the editor (cancelling out of an Add flow)
* Receiving an incomplete result (cancelling out of an Edit for an incomplete item)
* Receiving a complete item.

Also updated the tests and added a few new ones.

BUG=673371
TEST=PaymentRequest* (java)

Review-Url: https://codereview.chromium.org/2571513004
Cr-Commit-Position: refs/heads/master@{#439038}

BUG=643746

Review-Url: https://codereview.chromium.org/2569143002
Cr-Commit-Position: refs/heads/master@{#439037}

This code won't actually work. There are a couple of things that need
to be fixed for it to work:

. My understanding from looking at the code is that it will create
  multiple WindowTreeClients in the same thread. That can work, but when
  you do that you have to explicitly pass a WindowPortMus to Windows
  when you create them. That's hard in this case because
  DesktopNativeWidgetAura is creating the windows for you. The fix
  isn't hard, probably set the WindowTreeClient in
  DesktopNativeWidgetAura so that it can create WindowPort correctly.

. aura::WindowTreeClientDelegate has a couple of functions that can't
  be implemented in ViewImpl. Specifically getting the capture client
  and a PropertyConverter. The capture client generally comes from
  WMState and the PropertyConverter can be a singleton. It shouldn't
  be that hard to wire these up.

. aura::Env needs to be created with Mode::MUS.

As my understanding is I can't really run this code yet I didn't
pursue the fixes. If there is a way to run this code I can try and
make these fixes, otherwise I would prefer to postpone.

BUG=674757
TEST=none
R=ben@chromium.org

Review-Url: https://codereview.chromium.org/2585593002
Cr-Commit-Position: refs/heads/master@{#439036}

Reland of [DevTools] Migrate target domain to new generator. (patchset #1 id:1 of https://codereview.chromium.org/2578303002/ )

Reason for revert:
Fixed crash reason in https://codereview.chromium.org/2579923002/

Original issue's description:
> Revert of [DevTools] Migrate target domain to new generator. (patchset #2 id:20001 of https://codereview.chromium.org/2574843003/ )
>
> Reason for revert:
> Speculative
>
> Original issue's description:
> > [DevTools] Migrate target domain to new generator.
> >
> > BUG=664683
> > TBR=pfeldman
> >
> > Committed: https://crrev.com/a1a32123e28de766b5df3c82ec9ed9f8ddadd724
> > Cr-Commit-Position: refs/heads/master@{#438733}
>
> TBR=caseq@chromium.org
> # Skipping CQ checks because original CL landed less than 1 days ago.
> NOPRESUBMIT=true
> NOTREECHECKS=true
> NOTRY=true
> BUG=664683
>
> Committed: https://crrev.com/70847052d87dab3241593b925f87b2b96c031b7e
> Cr-Commit-Position: refs/heads/master@{#438940}

TBR=caseq@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=664683

Review-Url: https://codereview.chromium.org/2581103002
Cr-Commit-Position: refs/heads/master@{#439035}

BUG=570441

Review-Url: https://codereview.chromium.org/2580903003
Cr-Commit-Position: refs/heads/master@{#439034}

The following tests now use testharness.js:
  animation-direction-alternate.html
  animation-direction-alternate-reverse.html
  animation-direction-reverse-fill-mode.html
  animation-direction-reverse-non-hardware.html
  animation-direction-reverse-timing-functions.html

BUG=674123

Review-Url: https://codereview.chromium.org/2573413002
Cr-Commit-Position: refs/heads/master@{#439033}

Once the mojo connection is broken, all subsequent calls to the CDM
should fail.

BUG=671362
TEST=new tests pass

Review-Url: https://codereview.chromium.org/2561263002
Cr-Commit-Position: refs/heads/master@{#439032}

Removing the SiteEngagement experiment as it has gone stable.

BUG=539723

Review-Url: https://codereview.chromium.org/2577503004
Cr-Commit-Position: refs/heads/master@{#439031}

Default frame colors are changed so that inactive frames are always a
blend of 80% white/20% active color to increase contrast.
* The normal/inactive frame is changed to #F6F6F6 on all platforms. (OSX
  was already at this color.)
* The incognito/inactive frame is changed to #D4D5D5 on all platforms
  except OSX.
* The tints applied to theme images are changed to match the new
  lightness ratio as well. Inactive tint is changed to 80% lightness.
  Incognito/inactive is changed to be 74% lightness, which approximates
  blending 80% white on top of the active tint's 30% black. Also
  increased saturation change of incognito/inactive to match
  incognito/active.

Windows will now pick up the user colors specified by the system and use
them when custom drawing the titlebar. It will never draw the titlebar
white unless the user explicitly specifies that color. It uses an 80%
white/20% active blend to calculate inactive frame colors if the user
has no frame color specified, just like above.

BUG=505013,645682

Review-Url: https://codereview.chromium.org/2541873004
Cr-Commit-Position: refs/heads/master@{#439030}

BUG=none
R=lushnikov@chromium.org

Review-Url: https://codereview.chromium.org/2563213002
Cr-Commit-Position: refs/heads/master@{#439029}

iOS builds can set use_xcode_clang = true and use_system_xcode = false when
chromium clang is broken.  This requires prepending DEVELOPER_DIR to clang/clang++, etc

BUG=669094

Review-Url: https://codereview.chromium.org/2578273002
Cr-Commit-Position: refs/heads/master@{#439028}

When complete, the Gtk3 theming code will look completely different
from the Gtk2 code.  This CL splits out NativeThemeGtk in preparation
of this change.

The planned change for gtk3 is to use foreign drawing (see
gtk/demos/gtk-demo/foreigndrawing.c) to provide an implementation of
NativeTheme::GetPartSize and NativeTheme::Paint*.

The Gtk2 theme will continue to use the NativeThemeBase
implementations of these functions while just supplying basic colors.

BUG=132847
R=erg@chromium.org

Review-Url: https://codereview.chromium.org/2579683002
Cr-Commit-Position: refs/heads/master@{#439027}