Re-enable background:news:nytimes to examine crash

Re-enable background:news:nytimes

Also fixes the story for the Nexus7

BUG=664521
Committed: https://crrev.com/08e303fd2871c16b1fb675743e7548bc7e4feff9
Cr-Commit-Position: refs/heads/master@{#434497}

[nednguyen, 2016-11-16 02:26:55]

nednguyen@google.com changed reviewers:
+ nednguyen@google.com

[nednguyen, 2016-11-16 02:26:56]

lgtm

[hjd, 2016-11-25 12:06:32]

Description was changed from

==========
Re-enable background:news:nytimes to examine crash

BUG=664521
COMMIT=false
==========

to

==========
Re-enable background:news:nytimes to examine crash

BUG=664521
==========

[hjd, 2016-11-25 12:07:09]

Description was changed from

==========
Re-enable background:news:nytimes to examine crash

BUG=664521
==========

to

==========
Re-enable background:news:nytimes

BUG=664521
==========

[hjd, 2016-11-25 13:04:48]

Description was changed from

==========
Re-enable background:news:nytimes

BUG=664521
==========

to

==========
Re-enable background:news:nytimes

Also fixes the story for the Nexus7

BUG=664521
==========

[hjd, 2016-11-25 13:04:48]

hjd@chromium.org changed reviewers:
+ perezju@chromium.org

[hjd, 2016-11-25 13:05:00]

ptal, thanks!

[nednguyen, 2016-11-25 13:07:13]

lgtm

[hjd, 2016-11-25 13:34:10]

The CQ bit was checked by hjd@chromium.org

[commit-bot: I haz the power, 2016-11-25 13:34:24]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[perezju, 2016-11-25 14:05:40]

https://codereview.chromium.org/2505803002/diff/20001/tools/perf/page_sets/sy...
File tools/perf/page_sets/system_health/background_stories.py (right):

https://codereview.chromium.org/2505803002/diff/20001/tools/perf/page_sets/sy...
tools/perf/page_sets/system_health/background_stories.py:68:
action_runner.ScrollPageToElement(selector='.nytd-player-poster')
I'm OK with this as a short-term fix, but sounds like like an issue that should
be fixed in ScrollPageToElement?

i.e. the method should check whether it actually scrolled to the thing it was
supposed to, and either retry (like here) or fix whatever is causing it not to
reach the element in the first place?

[commit-bot: I haz the power, 2016-11-25 14:29:28]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1480080850062870,
"parent_rev": "b4fedb46f7417c85014c612655f1f9f0bfc35c28", "commit_rev":
"f91ff7dde33962da867ce40d6485257fe9b639a1"}

[commit-bot: I haz the power, 2016-11-25 14:29:53]

Description was changed from

==========
Re-enable background:news:nytimes

Also fixes the story for the Nexus7

BUG=664521
==========

to

==========
Re-enable background:news:nytimes

Also fixes the story for the Nexus7

BUG=664521
==========

[commit-bot: I haz the power, 2016-11-25 14:29:54]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-11-25 14:33:53]

Description was changed from

==========
Re-enable background:news:nytimes

Also fixes the story for the Nexus7

BUG=664521
==========

to

==========
Re-enable background:news:nytimes

Also fixes the story for the Nexus7

BUG=664521

Committed: https://crrev.com/08e303fd2871c16b1fb675743e7548bc7e4feff9
Cr-Commit-Position: refs/heads/master@{#434497}
==========

[commit-bot: I haz the power, 2016-11-25 14:33:54]

Patchset 2 (id:??) landed as
https://crrev.com/08e303fd2871c16b1fb675743e7548bc7e4feff9
Cr-Commit-Position: refs/heads/master@{#434497}