GitLab

Simplified as follows:
- If '--disable-fre' -- skip temporarily
- If a device hasn't been provisioned yet -- skip temporarily
- If FRE has already been completed -- great
- Otherwise, we start the FRE activity to see what to show.

Note that it doesn't matter how exactly Chrome was launched
(say, via the shortcut or via a VIEW intent), it always shows
the full FRE unless it's a test or the Setup Wizard environment.

BUG=450423

Review URL: https://codereview.chromium.org/1171833004

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

Also update the routines to ignore 'pssh' boxes with version 2 or
later.

BUG=460359, 460360
TEST=new unittests pass

Committed: https://crrev.com/b666d7874efac44b359a95329f0cb890e97671df
Cr-Commit-Position: refs/heads/master@{#333556}

Review URL: https://codereview.chromium.org/1149023002

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

BUG=441333

The stack is slightly different now that we're statically linking.

{
   Memcheck:Uninitialized
   fun:av_packet_unpack_dictionary
   fun:add_metadata_from_side_data
   fun:avcodec_decode_video2
   fun:avcodec_decode_video2  <=== THIS REPEATED LINE IS GONE NOW
   fun:_ZN5media18FFmpegVideoDecoder12FFmpegDecodeERK13scoped_refptrINS_13DecoderBufferEEPb
...

}

Example log:
http://build.chromium.org/p/chromium.memory.fyi/builders/Linux%20Tests%20%28valgrind%29%283%29/builds/46166/steps/memory%20test%3A%20media/logs/202EB30501710F5D

Review URL: https://codereview.chromium.org/1173813002

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

with field trial parameters to determine if the network is
prohibitively slow.

Hysteresis is added so that at least k seconds transpire
before the state of the network (prohibitively slow, or
not) is determined again. k is a parameter of the field
trial.

BUG=470596

Review URL: https://codereview.chromium.org/1153543016

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

BUG=488576

Review URL: https://codereview.chromium.org/1170813007

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

BUG=498093,490629,498206

Review URL: https://codereview.chromium.org/1171893008

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/0363313..4b91fed

TBR=enne@chromium.org,yurys@chromium.org

Review URL: https://codereview.chromium.org/1166283008

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

Along the way, clean up some tests' usage of SetTestingFactory().

BUG=NONE
TEST=git cl try

Review URL: https://codereview.chromium.org/1165913002

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

BUG=498519
TBR=kochi@chromium.org, thestig@chromium.org
NOTRY=true

Review URL: https://codereview.chromium.org/1177433004

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

BUG=495682

Review URL: https://codereview.chromium.org/1174773002

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

R=sievers@chromium.org, zmo@chromium.org
BUG=482067

Review URL: https://codereview.chromium.org/1151093006

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

uint32_t is used in the declaration of getnetbyaddr but
stdin.h was not directly included.

This will be needed once this change the newlib headers
lands: https://codereview.chromium.org/1163893003

BUG= https://code.google.com/p/nativeclient/issues/detail?id=4198

Review URL: https://codereview.chromium.org/1167113002

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

Remove unused mojo/public/mojo_sdk.gni.
(we use third_party/mojo's version instead)

Update, use mojo/public/ mojo.gni and mojo_application.gni
(to define Chromium's mojo_root, mojo_native_application)
(we'll need a custom mojo_native_application for 498020)

Remove unnecessary imports of related gni files.

BUG=498020
TEST=Build still works as expected; no regressions.
R=sky@chromium.org
TBR=jochen@chromium.org,xhwang@chromium.org

Review URL: https://codereview.chromium.org/1175693002

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

The current formula for number of raster threads is (num_cpus / 2), minus
1 if using asynchronous uploads.

This will give:
 1~2 threads on 4 core devices
 2~3 threads on 6 core devices
 3~4 threads on 8 core devices

Android can report 6 to 8 cores for big.LITTLE devices, where we don't
really want to utilize all the cores at once.  This change limits the
cores to 4 in the render threads calculation.

R=sievers@chromium.org
R=reveman@chromium.org
BUG=493432

Review URL: https://codereview.chromium.org/1168153004

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

This patch fixes size_t to int truncations for tiles/ and trees/
directories in cc.

BUG=167187
R=danakj
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Review URL: https://codereview.chromium.org/1168903003

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

Remove url:: variants. Add the 4-element version from url:: to base::

Review URL: https://codereview.chromium.org/1172753003

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

BUG=497282

Review URL: https://codereview.chromium.org/1169903002

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

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/be35c6f9..9efbfe82

Please follow these instructions for assigning/CC'ing issues:
https://code.google.com/p/v8-wiki/wiki/TriagingIssues

TBR=hablich@chromium.org,machenbach@chromium.org,yangguo@chromium.org,vogelheim@chromium.org

Review URL: https://codereview.chromium.org/1169853010

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

BUG=489317

Review URL: https://codereview.chromium.org/1174683002

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

Right now, if the results aren't there, the entire sharded perf tests step fails. This doesn't fix the underlying issue, but at least allows the rest of the tests to run and makes it clearer which step failed.

With Patch: http://simonhatch0.mon.corp.google.com:8013/builders/Android%20Nexus7v2%20Perf/builds/593

Without: http://simonhatch0.mon.corp.google.com:8013/builders/Android%20Nexus7v2%20Perf/builds/591

BUG=498412

Review URL: https://codereview.chromium.org/1176613002

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

  function mods end with "$".

"element" inside <webview> is currently the plugin <object> element, i.e.
  the browser plugin. This CL makes it possible to provide a different
  implementation for the element. This CL also provides a stub
  using <iframe>. This will be used by the <webview> using OOPIF
  architecture CL: https://chromiumcodereview.appspot.com/972313002/

BUG=330264
Test=None, no visible changes.

Review URL: https://codereview.chromium.org/1165773004

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

BUG=477827

Review URL: https://codereview.chromium.org/1164423010

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

BUG=chromium:476598
TEST=None

Review URL: https://codereview.chromium.org/1171213002

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

- GCD has begun enforcing stricter requirements for the |state| field
  of devices; this change restores compatibility.

- The GCD device ID is now used as the primary key for hosts when GCD
  support is enabled.

- Hosts registered in GCD now have a magic UUID stored in their tags
  so that Chromoting devices can be distinguished non-Chromoting devices
  stored in GCD.

- The |displayName| field has been officially deprecated.  With this
  change, the user-visible name of a host is stored in the |name|
  field, and the legacy host ID is stored as part of the |state|
  field.

- HostController.getLocalHostId is now aware of the difference between
  GCD and legacy hosts.  Depending on which field is stored in the
  local host config file, it returns the legacy ID |host_id|, or the
  GCD ID |gcd_device_id|.  This logic will move to HostListApi in
  an upcoming patch.

This CL contains some design decisions that may need to be re-visited
before launch.  In particular, there are fields on GCD that may be
more appropriate to use than nonstandard fields in |state|:

- The legacy ID, stored as |state.base._legacyId|, could be stored as
  the |serialNumber| field.  The GCD docs, however, indicate that this
  field is not writable, and it seems wise to store the legacy ID in a
  field that can be removed once migration to GCD is complete.

- Instead of a magic tag, it may make more sense to store a special
  value in |modelManfiest| or |modelManifesetId|.  Unfortunately these
  fields are largely undocumented.

- The host version, stored as |state.base._hostVersion|, could be
  stored as |state.base.firmwareVersion|.  The implications of doing
  so are unclear.

BUG=471928

Review URL: https://codereview.chromium.org/1161813006

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

Last change for making the service side conform to the public name.
Renames all BrowserConnectionX classes to CustomTabsConnectionX.

Review URL: https://codereview.chromium.org/1172753002

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

This is a partial revert of
https://codereview.chromium.org/1140173003/

TEST=in certain contexts involving WebView, toggling on/off ChromeVox repeatedly does not break ChromeVox.
BUG=496664

Review URL: https://codereview.chromium.org/1173523006

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

This CL follows https://codereview.chromium.org/1162103003/

BUG=492787

Review URL: https://codereview.chromium.org/1166373006

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

A new enum value for the DataReductionProxy.ProxyPrefMigrationResult
histogram was added in https://codereview.chromium.org/1148793008, but
this new value wasn't added to histograms.xml. This CL updates
histograms.xml appropriately.

BUG=498429

Review URL: https://codereview.chromium.org/1164423009

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

BUG=

Review URL: https://codereview.chromium.org/1174633002

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

The previous invocation did not work as expected, since the exported
symbols reside in the global namespace instead of on the backgroundSetup
object.

BUG=489929

Review URL: https://codereview.chromium.org/1167643003

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

BUG=498040

Review URL: https://codereview.chromium.org/1165273003

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

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/1831f99..c15d957

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
TBR=djsollen@google.com

Review URL: https://codereview.chromium.org/1169213003

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

VSyncMonitor is not thread-safe, and is not intended to be. When a vsync
request is made from a non-UI thread, there is a race where both a
synthetic and frame-based callback can fire for the same request. Avoid
this by making sure VSyncMonitorTest only requests updates from the UI
thread, representative of production code behavior.

BUG=498007

Review URL: https://codereview.chromium.org/1166223003

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

Also added new features to generate a list of chromium bugs and trigger
tryjobs after upload.

BUG=489922

Review URL: https://codereview.chromium.org/1163333002

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

Use GLES2Interface::GetGraphicsResetStatusKHR() instead now that it
exists.

R=piman@chromium.org
BUG=492447
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Review URL: https://codereview.chromium.org/1168943002

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

Previously reverted by r333185.

TEST=TaskSwitchMetricsRecorderTest.VerifyTaskSwitchesForDesktopAreRecorded
TEST=DesktopTaskSwitchMetricRecorderTest.ActivatePositionableWindowWhenNullWindowWasActivatedLast
TEST=DesktopTaskSwitchMetricRecorderTest.ActivatePositionableWindowWhenADifferentPositionableWindowWasActivatedLast
TEST=DesktopTaskSwitchMetricRecorderTest.ActivatePositionableWindowWhenTheSamePositionableWindowWasActivatedLast
TEST=DesktopTaskSwitchMetricRecorderTest.ActivatePositionableWindowWhenANonPositionableWindowWasActivatedLast
TEST=DesktopTaskSwitchMetricRecorderTest.ActivateNonPositionableWindowBetweenTwoPositionableWindowActivations
TEST=DesktopTaskSwitchMetricRecorderTest.ActivateNullWindow
TEST=DesktopTaskSwitchMetricRecorderTest.ActivateNonPositionableWindow
TEST=DesktopTaskSwitchMetricRecorderTest.ActivatePositionableWindowWithNonInputEventReason
TEST=DesktopTaskSwitchMetricRecorderWithShellIntegrationTest.ActivatePositionableWindowWithInputEvent
TEST=DesktopTaskSwitchMetricRecorderWithShellIntegrationTest.ActivatePositionableWindowWithNonInputEvent

BUG=489813, 489814

Review URL: https://codereview.chromium.org/1171163003

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

When using SingleThreadProxy with impl side painting the scheduler waits
for the READY_TO_DRAW signal indefinitely. If renderer switches from
visible to invisible and back again it gets in a state where it won't
ever call PrepareTiles and not advance frames indefinitely. Calling
PrepareTiles unconditionally on visiblity changes fixes that.

BUG=497473
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Review URL: https://codereview.chromium.org/1169213002

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

- When leaving the tab switcher, don't update the toolbar button states.  This can cause
the home button to be displayed early.

BUG=497602

Review URL: https://codereview.chromium.org/1169233002

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

With startup tracing via Telemetry, tracing may be started from places other than devtool (by reading the trace-config file). So devtool should not maintain the state of the tracing system. It can get the information from the TracingController. This requires adding one more function to TracingController's API.

Startup tracing design doc:
https://docs.google.com/document/d/1yRCXhrQ-0rsfUgNHt9T4YdnmJYrXKN6aK56Ozk3kPVc/edit?usp=sharing

BUG=317481, 482098

Review URL: https://codereview.chromium.org/1171813002

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

This CL will be followed up with:
1. https://codereview.chromium.org/1167693010 (Blink)
2. https://codereview.chromium.org/1163963002 (Chrome)

BUG=445359, 484401

Review URL: https://codereview.chromium.org/1165293005

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