Add performance tests for full frame cycle

Add performance tests for full frame cycle

They are under paint directory because they mainly test paint + raster
performance after style change.

Add PerfTestRunner.measureFrameTime().

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

[Xianzhu, 2016-10-18 23:19:28]

wangxianzhu@chromium.org changed reviewers:
+ pdr@chromium.org, wkorman@chromium.org

[Xianzhu, 2016-10-18 23:19:36]

The CQ bit was checked by wangxianzhu@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-18 23:20:19]

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

[pdr., 2016-10-18 23:22:08]

Overall looks pretty good. Do we want to hook this up to run on chromeperf?

https://codereview.chromium.org/2429623004/diff/1/third_party/WebKit/Performa...
File third_party/WebKit/PerformanceTests/resources/runner.js (right):

https://codereview.chromium.org/2429623004/diff/1/third_party/WebKit/Performa...
third_party/WebKit/PerformanceTests/resources/runner.js:275: setTimneout(task,
0);
setTimeout?

[commit-bot: I haz the power, 2016-10-19 00:21:29]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-19 00:21:30]

Dry run: Try jobs failed on following builders:
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[Xianzhu, 2016-10-19 03:38:15]

On 2016/10/18 23:22:08, pdr. wrote:
> Overall looks pretty good. Do we want to hook this up to run on chromeperf?
> 

The directory has been hooked up as "blink_perf.paint". We'll see results of the
new tests after this is landed.

https://codereview.chromium.org/2429623004/diff/1/third_party/WebKit/Performa...
File third_party/WebKit/PerformanceTests/resources/runner.js (right):

https://codereview.chromium.org/2429623004/diff/1/third_party/WebKit/Performa...
third_party/WebKit/PerformanceTests/resources/runner.js:275: setTimneout(task,
0);
On 2016/10/18 23:22:08, pdr. wrote:
> setTimeout?

Fixed.

It did break harness tests. Added new harness tests to prevent errors.

[pdr., 2016-10-19 03:50:31]

LGTM

https://codereview.chromium.org/2429623004/diff/20001/third_party/WebKit/Layo...
File third_party/WebKit/LayoutTests/fast/harness/perftests/measure-time.html
(right):

https://codereview.chromium.org/2429623004/diff/20001/third_party/WebKit/Layo...
third_party/WebKit/LayoutTests/fast/harness/perftests/measure-time.html:4: var
virtualTime = Math.floor(Math.random() * 100000);
Nit: could you use a fixed random value like 123456? (here and below)

Your current code isn't flaky but I think it's best to be deterministic when
possible (e.g., easier to debug if it breaks).

[Xianzhu, 2016-10-19 15:17:10]

https://codereview.chromium.org/2429623004/diff/20001/third_party/WebKit/Layo...
File third_party/WebKit/LayoutTests/fast/harness/perftests/measure-time.html
(right):

https://codereview.chromium.org/2429623004/diff/20001/third_party/WebKit/Layo...
third_party/WebKit/LayoutTests/fast/harness/perftests/measure-time.html:4: var
virtualTime = Math.floor(Math.random() * 100000);
On 2016/10/19 03:50:31, pdr. wrote:
> Nit: could you use a fixed random value like 123456? (here and below)
> 
> Your current code isn't flaky but I think it's best to be deterministic when
> possible (e.g., easier to debug if it breaks).

Done.

[Xianzhu, 2016-10-19 15:17:53]

The CQ bit was checked by wangxianzhu@chromium.org

[Xianzhu, 2016-10-19 15:17:54]

The patchset sent to the CQ was uploaded after l-g-t-m from pdr@chromium.org
Link to the patchset: https://codereview.chromium.org/2429623004/#ps40001
(title: "No random")

[commit-bot: I haz the power, 2016-10-19 15:18:14]

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

[commit-bot: I haz the power, 2016-10-19 16:18:43]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-10-21 13:09:10]

Description was changed from

==========
Add performance tests for full frame cycle

They are under paint directory because they mainly test paint + raster
performance after style change.

Add PerfTestRunner.measureFrameTime().
==========

to

==========
Add performance tests for full frame cycle

They are under paint directory because they mainly test paint + raster
performance after style change.

Add PerfTestRunner.measureFrameTime().

Committed: https://crrev.com/da92cf5e2403c21b53274775b080d7df20126b79
Cr-Commit-Position: refs/heads/master@{#426216}
==========

[commit-bot: I haz the power, 2016-10-21 13:09:11]

Patchset 3 (id:??) landed as
https://crrev.com/da92cf5e2403c21b53274775b080d7df20126b79
Cr-Commit-Position: refs/heads/master@{#426216}