Revert unfinished work of "full-frame-measurement"

Revert unfinished work of "full-frame-measurement"

I wanted to measure full-frame performance using the existing
performance tests, but used a method requiring internal API of
content_shell. I didn't finish the remaining work of setting up
reference build of content_shell etc. Also slimiming paint will
change how compositing update, paint invalidation and paint work.

This CL reverts the unfinished work of "full-frame-measurement" by:
- Renaming PerfTestRunner.forceLayoutOrFullFrame() to
  PerfTestRunner.forceLayout();
- Removing full-frame-measurement benchmarks requiring content_shell;
- Removing content_shell from perf bot build.

Future full-frame-measurement tests should use requestAnimationFrame().
(See third_party/WebKit/PerformanceTests/Paint/large-table*.html
created by jchaffraix@ for example.)

BUG=426599
R=jchaffraix@chromium.org,nednguyen@google.com
TBR=wangxianzhu@chromium.org (build/all.gyp)
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_10_10_perf_bisect;tryserver.chromium.perf:win_perf_bisect

Committed: https://crrev.com/5cba1e2af6c1e29afbe088413bfbf6f94d6eb0f3
Cr-Commit-Position: refs/heads/master@{#367562}

[Xianzhu, 2016-01-04 18:36:01]

Description was changed from

==========
Revert unfinished work of "full-frame-measurement"

I wanted to measure full-frame performance using the existing
performance tests, but used a method requiring internal API of
content_shell. I didn't finish the remaining work of setting up
reference build of content_shell etc. Also slimiming paint will
change how compositing update, paint invalidation and paint work.

This CL reverts the unfinished work of "full-frame-measurement":
- Rename PerfTestRunner.forceLayoutOrFullFrame() to
  PerfTestRunner.forceLayout();
- Remove full-frame-measurement benchmarks requiring content_shell;
- Remove content_shell from perf bot build.

Future full-frame-measurement tests should use requestAnimationFrame().
(See third_party/WebKit/PerformanceTests/Paint/large-table*.html
created by jchaffraix@ for example.)

BUG=426599
==========

to

==========
Revert unfinished work of "full-frame-measurement"

I wanted to measure full-frame performance using the existing
performance tests, but used a method requiring internal API of
content_shell. I didn't finish the remaining work of setting up
reference build of content_shell etc. Also slimiming paint will
change how compositing update, paint invalidation and paint work.

This CL reverts the unfinished work of "full-frame-measurement":
- Rename PerfTestRunner.forceLayoutOrFullFrame() to
  PerfTestRunner.forceLayout();
- Remove full-frame-measurement benchmarks requiring content_shell;
- Remove content_shell from perf bot build.

Future full-frame-measurement tests should use requestAnimationFrame().
(See third_party/WebKit/PerformanceTests/Paint/large-table*.html
created by jchaffraix@ for example.)

BUG=426599
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_10_10_perf_bisect;tryserver.chromium.perf:win_perf_bisect
==========

[Xianzhu, 2016-01-04 18:38:01]

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

[commit-bot: I haz the power, 2016-01-04 18:39:23]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1557953002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1557953002/1

[Xianzhu, 2016-01-04 18:39:27]

wangxianzhu@chromium.org changed reviewers:
+ jchaffraix@chromium.org, nednguyen@google.com

[Xianzhu, 2016-01-04 18:39:27]

Ptal:
nednguyen@: tools/perf/
jchaffraix@: third_party/WebKit/PerformanceTests/

[nednguyen, 2016-01-04 18:41:02]

lgtm

[commit-bot: I haz the power, 2016-01-04 21:01:50]

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

[commit-bot: I haz the power, 2016-01-04 21:01:52]

Dry run: This issue passed the CQ dry run.

[Julien - ping for review, 2016-01-05 09:26:11]

lgtm

[Xianzhu, 2016-01-05 17:21:16]

Description was changed from

==========
Revert unfinished work of "full-frame-measurement"

I wanted to measure full-frame performance using the existing
performance tests, but used a method requiring internal API of
content_shell. I didn't finish the remaining work of setting up
reference build of content_shell etc. Also slimiming paint will
change how compositing update, paint invalidation and paint work.

This CL reverts the unfinished work of "full-frame-measurement":
- Rename PerfTestRunner.forceLayoutOrFullFrame() to
  PerfTestRunner.forceLayout();
- Remove full-frame-measurement benchmarks requiring content_shell;
- Remove content_shell from perf bot build.

Future full-frame-measurement tests should use requestAnimationFrame().
(See third_party/WebKit/PerformanceTests/Paint/large-table*.html
created by jchaffraix@ for example.)

BUG=426599
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_10_10_perf_bisect;tryserver.chromium.perf:win_perf_bisect
==========

to

==========
Revert unfinished work of "full-frame-measurement"

I wanted to measure full-frame performance using the existing
performance tests, but used a method requiring internal API of
content_shell. I didn't finish the remaining work of setting up
reference build of content_shell etc. Also slimiming paint will
change how compositing update, paint invalidation and paint work.

This CL reverts the unfinished work of "full-frame-measurement" by:
- Renaming PerfTestRunner.forceLayoutOrFullFrame() to
  PerfTestRunner.forceLayout();
- Removing full-frame-measurement benchmarks requiring content_shell;
- Removing content_shell from perf bot build.

Future full-frame-measurement tests should use requestAnimationFrame().
(See third_party/WebKit/PerformanceTests/Paint/large-table*.html
created by jchaffraix@ for example.)

BUG=426599
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_10_10_perf_bisect;tryserver.chromium.perf:win_perf_bisect
==========

[Xianzhu, 2016-01-05 17:21:36]

The CQ bit was checked by wangxianzhu@chromium.org

[commit-bot: I haz the power, 2016-01-05 17:21:52]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1557953002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1557953002/1

[commit-bot: I haz the power, 2016-01-05 17:31:38]

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

[commit-bot: I haz the power, 2016-01-05 17:31:38]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[Xianzhu, 2016-01-05 17:33:03]

Description was changed from

==========
Revert unfinished work of "full-frame-measurement"

I wanted to measure full-frame performance using the existing
performance tests, but used a method requiring internal API of
content_shell. I didn't finish the remaining work of setting up
reference build of content_shell etc. Also slimiming paint will
change how compositing update, paint invalidation and paint work.

This CL reverts the unfinished work of "full-frame-measurement" by:
- Renaming PerfTestRunner.forceLayoutOrFullFrame() to
  PerfTestRunner.forceLayout();
- Removing full-frame-measurement benchmarks requiring content_shell;
- Removing content_shell from perf bot build.

Future full-frame-measurement tests should use requestAnimationFrame().
(See third_party/WebKit/PerformanceTests/Paint/large-table*.html
created by jchaffraix@ for example.)

BUG=426599
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_10_10_perf_bisect;tryserver.chromium.perf:win_perf_bisect
==========

to

==========
Revert unfinished work of "full-frame-measurement"

I wanted to measure full-frame performance using the existing
performance tests, but used a method requiring internal API of
content_shell. I didn't finish the remaining work of setting up
reference build of content_shell etc. Also slimiming paint will
change how compositing update, paint invalidation and paint work.

This CL reverts the unfinished work of "full-frame-measurement" by:
- Renaming PerfTestRunner.forceLayoutOrFullFrame() to
  PerfTestRunner.forceLayout();
- Removing full-frame-measurement benchmarks requiring content_shell;
- Removing content_shell from perf bot build.

Future full-frame-measurement tests should use requestAnimationFrame().
(See third_party/WebKit/PerformanceTests/Paint/large-table*.html
created by jchaffraix@ for example.)

BUG=426599
R=jchaffraix@chromium.org,nednguyen@google.com
TBR=wangxianzhu@chromium.org (build/all.gyp)
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_10_10_perf_bisect;tryserver.chromium.perf:win_perf_bisect
==========

[Xianzhu, 2016-01-05 17:33:09]

The CQ bit was checked by wangxianzhu@chromium.org

[commit-bot: I haz the power, 2016-01-05 17:34:24]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1557953002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1557953002/1

[commit-bot: I haz the power, 2016-01-05 17:41:23]

Description was changed from

==========
Revert unfinished work of "full-frame-measurement"

I wanted to measure full-frame performance using the existing
performance tests, but used a method requiring internal API of
content_shell. I didn't finish the remaining work of setting up
reference build of content_shell etc. Also slimiming paint will
change how compositing update, paint invalidation and paint work.

This CL reverts the unfinished work of "full-frame-measurement" by:
- Renaming PerfTestRunner.forceLayoutOrFullFrame() to
  PerfTestRunner.forceLayout();
- Removing full-frame-measurement benchmarks requiring content_shell;
- Removing content_shell from perf bot build.

Future full-frame-measurement tests should use requestAnimationFrame().
(See third_party/WebKit/PerformanceTests/Paint/large-table*.html
created by jchaffraix@ for example.)

BUG=426599
R=jchaffraix@chromium.org,nednguyen@google.com
TBR=wangxianzhu@chromium.org (build/all.gyp)
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_10_10_perf_bisect;tryserver.chromium.perf:win_perf_bisect
==========

to

==========
Revert unfinished work of "full-frame-measurement"

I wanted to measure full-frame performance using the existing
performance tests, but used a method requiring internal API of
content_shell. I didn't finish the remaining work of setting up
reference build of content_shell etc. Also slimiming paint will
change how compositing update, paint invalidation and paint work.

This CL reverts the unfinished work of "full-frame-measurement" by:
- Renaming PerfTestRunner.forceLayoutOrFullFrame() to
  PerfTestRunner.forceLayout();
- Removing full-frame-measurement benchmarks requiring content_shell;
- Removing content_shell from perf bot build.

Future full-frame-measurement tests should use requestAnimationFrame().
(See third_party/WebKit/PerformanceTests/Paint/large-table*.html
created by jchaffraix@ for example.)

BUG=426599
R=jchaffraix@chromium.org,nednguyen@google.com
TBR=wangxianzhu@chromium.org (build/all.gyp)
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_10_10_perf_bisect;tryserver.chromium.perf:win_perf_bisect
==========

[commit-bot: I haz the power, 2016-01-05 17:41:24]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-01-05 17:42:37]

Description was changed from

==========
Revert unfinished work of "full-frame-measurement"

I wanted to measure full-frame performance using the existing
performance tests, but used a method requiring internal API of
content_shell. I didn't finish the remaining work of setting up
reference build of content_shell etc. Also slimiming paint will
change how compositing update, paint invalidation and paint work.

This CL reverts the unfinished work of "full-frame-measurement" by:
- Renaming PerfTestRunner.forceLayoutOrFullFrame() to
  PerfTestRunner.forceLayout();
- Removing full-frame-measurement benchmarks requiring content_shell;
- Removing content_shell from perf bot build.

Future full-frame-measurement tests should use requestAnimationFrame().
(See third_party/WebKit/PerformanceTests/Paint/large-table*.html
created by jchaffraix@ for example.)

BUG=426599
R=jchaffraix@chromium.org,nednguyen@google.com
TBR=wangxianzhu@chromium.org (build/all.gyp)
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_10_10_perf_bisect;tryserver.chromium.perf:win_perf_bisect
==========

to

==========
Revert unfinished work of "full-frame-measurement"

I wanted to measure full-frame performance using the existing
performance tests, but used a method requiring internal API of
content_shell. I didn't finish the remaining work of setting up
reference build of content_shell etc. Also slimiming paint will
change how compositing update, paint invalidation and paint work.

This CL reverts the unfinished work of "full-frame-measurement" by:
- Renaming PerfTestRunner.forceLayoutOrFullFrame() to
  PerfTestRunner.forceLayout();
- Removing full-frame-measurement benchmarks requiring content_shell;
- Removing content_shell from perf bot build.

Future full-frame-measurement tests should use requestAnimationFrame().
(See third_party/WebKit/PerformanceTests/Paint/large-table*.html
created by jchaffraix@ for example.)

BUG=426599
R=jchaffraix@chromium.org,nednguyen@google.com
TBR=wangxianzhu@chromium.org (build/all.gyp)
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_10_10_perf_bisect;tryserver.chromium.perf:win_perf_bisect

Committed: https://crrev.com/5cba1e2af6c1e29afbe088413bfbf6f94d6eb0f3
Cr-Commit-Position: refs/heads/master@{#367562}
==========

[commit-bot: I haz the power, 2016-01-05 17:42:37]

Patchset 1 (id:??) landed as
https://crrev.com/5cba1e2af6c1e29afbe088413bfbf6f94d6eb0f3
Cr-Commit-Position: refs/heads/master@{#367562}