Rewrite broken Facebook test case in top_7_stress

Rewrite broken Facebook test case in top_7_stress

To enable memory.top_7_stress benchmark.

BUG=440305
TEST=tools/perf/run_benchmark memory.top_7_stress

Committed: https://crrev.com/9a5f241dcf8825d10ac1f43bda60ddd17760f044
Cr-Commit-Position: refs/heads/master@{#309340}

[hashimoto, 2014-12-11 12:10:03]

hashimoto@chromium.org changed reviewers:
+ tonyg@chromium.org

[hashimoto, 2014-12-11 12:10:04]

Currently, Facebook test case is failing because
action_runner.ClickElement(text='About') results in a 404 being served (maybe
they don't like serving to bots?).
Rewriting the test to scroll the page, load the next page and scroll again.

Any better alternative ideas would be welcome.

With this fix, I verified that memory.top_7_stress can finish successfully on
Linux.

[tonyg, 2014-12-13 01:05:00]

Wouldn't we need to re-record the pageset along with this change?

[hashimoto, 2014-12-15 04:39:23]

On 2014/12/13 01:05:00, tonyg wrote:
> Wouldn't we need to re-record the pageset along with this change?

Sorry, I'm new to this area. (maybe this task should be handled by an expert
rather than me)
How can I "re-record the pageset"?
Do we keep a record of the pageset used for the benchmarks somewhere?

[tonyg, 2014-12-16 02:55:40]

On 2014/12/15 04:39:23, hashimoto wrote:
> On 2014/12/13 01:05:00, tonyg wrote:
> > Wouldn't we need to re-record the pageset along with this change?
> 
> Sorry, I'm new to this area. (maybe this task should be handled by an expert
> rather than me)
> How can I "re-record the pageset"?
> Do we keep a record of the pageset used for the benchmarks somewhere?

http://www.chromium.org/developers/telemetry/record_a_page_set

[hashimoto, 2014-12-16 07:10:32]

On 2014/12/16 02:55:40, tonyg wrote:
> On 2014/12/15 04:39:23, hashimoto wrote:
> > On 2014/12/13 01:05:00, tonyg wrote:
> > > Wouldn't we need to re-record the pageset along with this change?
> > 
> > Sorry, I'm new to this area. (maybe this task should be handled by an expert
> > rather than me)
> > How can I "re-record the pageset"?
> > Do we keep a record of the pageset used for the benchmarks somewhere?
> 
> http://www.chromium.org/developers/telemetry/record_a_page_set

Thanks for the pointer.
Ran tools/perf/record_wpr top7_stress_page_set and uploaded a new patch set.
PTAL

[hashimoto, 2014-12-16 08:32:33]

Found that changing top_25.json results in breaking smoothness.top_25_smooth
because it's sharing the same wpr with this test.

Uploaded a new patch set which adds top_7_stress.json instead.

top_25_000.wpr.sha1 and top_25_001.wpr.sha1 are reused for the new file
top_7_stress.json.
I did this because record_wpr fails to record Google related data on my
environment. (because the test case is outdated, and the login page rejects
bots.)

[hashimoto, 2014-12-19 06:46:02]

Tony, could you take a look at this CL?

[tonyg, 2014-12-19 18:07:30]

lgtm

[hashimoto, 2014-12-20 03:45:59]

The CQ bit was checked by hashimoto@chromium.org

[commit-bot: I haz the power, 2014-12-20 03:47:06]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/793983003/60001

[commit-bot: I haz the power, 2014-12-20 05:36:23]

Committed patchset #4 (id:60001)

[commit-bot: I haz the power, 2014-12-20 05:37:11]

Patchset 4 (id:??) landed as
https://crrev.com/9a5f241dcf8825d10ac1f43bda60ddd17760f044
Cr-Commit-Position: refs/heads/master@{#309340}

[tonyg, 2014-12-21 19:32:22]

On 2014/12/20 05:37:11, I haz the power (commit-bot) wrote:
> Patchset 4 (id:??) landed as
> https://crrev.com/9a5f241dcf8825d10ac1f43bda60ddd17760f044
> Cr-Commit-Position: refs/heads/master@{#309340}

Looks like this is failing on the bots, but it can't be automatically reverted
on the bots because they don't know how to revert A+ files. So I'm quickly
disabling it here: https://codereview.chromium.org/810333004