Use iframe in blink_perf.pywebsocket perf tests to remove --disable-web-security

Use iframe in blink_perf.pywebsocket perf tests to remove --disable-web-security

Previously:
(a) util_performance_test.js in Blink runs performance tests using
(b) pywebsocket's scripts,
but this required --disable-web-security for cross-origin workers
because (a) and (b) have different origins.

We change this so that:
(a) util_performance_test.js creates
(c) <iframe> with src=pywebsocket's example/*_iframe.html that runs
    the performance tests on the iframe using
(b) pywebsocket's scripts.
Because (b) and (c) have the same origin (but (a) has a different origin),
Tests are run in the same-origin while we have an cross-origin iframe.

This CL adds pywebsocket-side iframe HTML/JavaScript files for (b) and (c). and
updates DEPS to include pywebsocket-side changes [1].

[1] pywebsocket-side: https://github.com/google/pywebsocket/pull/147
[2] Chromium-side: This CL.
BUG=567533
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/76efe99397c323d99ba95a3eb0102207358aeb29
Cr-Commit-Position: refs/heads/master@{#365787}

[hiroshige, 2015-12-14 07:41:47]

Description was changed from

==========
Remove --disable-web-security from blink_perf.pywebsocket

BUG=567533
==========

to

==========
Remove --disable-web-security from blink_perf.pywebsocket

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

[hiroshige, 2015-12-14 09:24:32]

Description was changed from

==========
Remove --disable-web-security from blink_perf.pywebsocket

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

to

==========
Use iframe for Chromium performance tests to remove --disable-web-security

Previously:
(a) util_performance_test.js in Blink runs performance tests using
(b) pywebsocket's scripts,
but this required --disable-web-security for cross-origin workers
because (a) and (b) have different origins.

We change this so that:
(a) util_performance_test.js creates
(c) <iframe> with src=pywebsocket's example/*_iframe.html that runs
    the performance tests on the iframe using
(b) pywebsocket's scripts.
Because (b) and (c) have the same origin (but (a) has a different origin),
Tests are run in the same-origin while we have an cross-origin iframe.

This CL adds pywebsocket-side iframe HTML/JavaScript files for (b) and (c).

[1] pywebsocket-side: https://github.com/google/pywebsocket/pull/147
[2] Chromium-side: This CL.
BUG=567533
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_10_10_perf_bisect;tryserver.chromium.perf:win_perf_bisect
==========

[hiroshige, 2015-12-15 07:05:43]

hiroshige@chromium.org changed reviewers:
+ sullivan@chromium.org, tyoshino@chromium.org

[hiroshige, 2015-12-15 07:05:44]

tyoshino@, could you take a look also at this Chromium/Blink-side CL?

sullivan@, could you take a look at the change of:
tools/perf/benchmarks/blink_perf.py
as tools/perf OWNER?

[hiroshige, 2015-12-15 07:18:49]

Description was changed from

==========
Use iframe for Chromium performance tests to remove --disable-web-security

Previously:
(a) util_performance_test.js in Blink runs performance tests using
(b) pywebsocket's scripts,
but this required --disable-web-security for cross-origin workers
because (a) and (b) have different origins.

We change this so that:
(a) util_performance_test.js creates
(c) <iframe> with src=pywebsocket's example/*_iframe.html that runs
    the performance tests on the iframe using
(b) pywebsocket's scripts.
Because (b) and (c) have the same origin (but (a) has a different origin),
Tests are run in the same-origin while we have an cross-origin iframe.

This CL adds pywebsocket-side iframe HTML/JavaScript files for (b) and (c).

[1] pywebsocket-side: https://github.com/google/pywebsocket/pull/147
[2] Chromium-side: This CL.
BUG=567533
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_10_10_perf_bisect;tryserver.chromium.perf:win_perf_bisect
==========

to

==========
Use iframe for Chromium performance tests to remove --disable-web-security

Previously:
(a) util_performance_test.js in Blink runs performance tests using
(b) pywebsocket's scripts,
but this required --disable-web-security for cross-origin workers
because (a) and (b) have different origins.

We change this so that:
(a) util_performance_test.js creates
(c) <iframe> with src=pywebsocket's example/*_iframe.html that runs
    the performance tests on the iframe using
(b) pywebsocket's scripts.
Because (b) and (c) have the same origin (but (a) has a different origin),
Tests are run in the same-origin while we have an cross-origin iframe.

This CL adds pywebsocket-side iframe HTML/JavaScript files for (b) and (c). and
updates DEPS to include pywebsocket-side changes [1].

[1] pywebsocket-side: https://github.com/google/pywebsocket/pull/147
[2] Chromium-side: This CL.
BUG=567533
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_10_10_perf_bisect;tryserver.chromium.perf:win_perf_bisect
==========

[hiroshige, 2015-12-15 07:19:01]

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

[commit-bot: I haz the power, 2015-12-15 07:19:21]

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

[commit-bot: I haz the power, 2015-12-15 09:45:34]

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

[commit-bot: I haz the power, 2015-12-15 09:45:35]

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

[sullivan, 2015-12-15 22:13:22]

lgtm

Any idea if there is any work on iframe prioritization/throttling that could
affect the results of the test?

[hiroshige, 2015-12-16 07:19:44]

> Any idea if there is any work on iframe prioritization/throttling that could
> affect the results of the test?
I expect no such things (but not sure).

The performance values can be changed by this change, due to:
- use of iframes, or
- removing --disable-web-security.
According to trybot results, changes are small (perhaps within noise?) and
acceptable.
https://codereview.chromium.org/1524083002/
https://codereview.chromium.org/1530603002/
https://codereview.chromium.org/1525783003/

[sullivan, 2015-12-16 15:23:27]

On 2015/12/16 07:19:44, hiroshige wrote:
> > Any idea if there is any work on iframe prioritization/throttling that could
> > affect the results of the test?
> I expect no such things (but not sure).
> 
> The performance values can be changed by this change, due to:
> - use of iframes, or
> - removing --disable-web-security.
> According to trybot results, changes are small (perhaps within noise?) and
> acceptable.
> https://codereview.chromium.org/1524083002/
> https://codereview.chromium.org/1530603002/
> https://codereview.chromium.org/1525783003/

This is okay with me.

[tyoshino (SeeGerritForStatus), 2015-12-17 04:55:59]

lgtm

[hiroshige, 2015-12-17 06:34:59]

The CQ bit was checked by hiroshige@chromium.org

[commit-bot: I haz the power, 2015-12-17 06:35:23]

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

[hiroshige, 2015-12-17 06:38:23]

The CQ bit was unchecked by hiroshige@chromium.org

[hiroshige, 2015-12-17 06:38:56]

Description was changed from

==========
Use iframe for Chromium performance tests to remove --disable-web-security

Previously:
(a) util_performance_test.js in Blink runs performance tests using
(b) pywebsocket's scripts,
but this required --disable-web-security for cross-origin workers
because (a) and (b) have different origins.

We change this so that:
(a) util_performance_test.js creates
(c) <iframe> with src=pywebsocket's example/*_iframe.html that runs
    the performance tests on the iframe using
(b) pywebsocket's scripts.
Because (b) and (c) have the same origin (but (a) has a different origin),
Tests are run in the same-origin while we have an cross-origin iframe.

This CL adds pywebsocket-side iframe HTML/JavaScript files for (b) and (c). and
updates DEPS to include pywebsocket-side changes [1].

[1] pywebsocket-side: https://github.com/google/pywebsocket/pull/147
[2] Chromium-side: This CL.
BUG=567533
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_10_10_perf_bisect;tryserver.chromium.perf:win_perf_bisect
==========

to

==========
Use iframe in blink_perf.pywebsocket perf tests to remove --disable-web-security

Previously:
(a) util_performance_test.js in Blink runs performance tests using
(b) pywebsocket's scripts,
but this required --disable-web-security for cross-origin workers
because (a) and (b) have different origins.

We change this so that:
(a) util_performance_test.js creates
(c) <iframe> with src=pywebsocket's example/*_iframe.html that runs
    the performance tests on the iframe using
(b) pywebsocket's scripts.
Because (b) and (c) have the same origin (but (a) has a different origin),
Tests are run in the same-origin while we have an cross-origin iframe.

This CL adds pywebsocket-side iframe HTML/JavaScript files for (b) and (c). and
updates DEPS to include pywebsocket-side changes [1].

[1] pywebsocket-side: https://github.com/google/pywebsocket/pull/147
[2] Chromium-side: This CL.
BUG=567533
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_10_10_perf_bisect;tryserver.chromium.perf:win_perf_bisect
==========

[hiroshige, 2015-12-17 06:39:12]

The CQ bit was checked by hiroshige@chromium.org

[commit-bot: I haz the power, 2015-12-17 06:39:23]

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

[commit-bot: I haz the power, 2015-12-17 08:46:56]

Description was changed from

==========
Use iframe in blink_perf.pywebsocket perf tests to remove --disable-web-security

Previously:
(a) util_performance_test.js in Blink runs performance tests using
(b) pywebsocket's scripts,
but this required --disable-web-security for cross-origin workers
because (a) and (b) have different origins.

We change this so that:
(a) util_performance_test.js creates
(c) <iframe> with src=pywebsocket's example/*_iframe.html that runs
    the performance tests on the iframe using
(b) pywebsocket's scripts.
Because (b) and (c) have the same origin (but (a) has a different origin),
Tests are run in the same-origin while we have an cross-origin iframe.

This CL adds pywebsocket-side iframe HTML/JavaScript files for (b) and (c). and
updates DEPS to include pywebsocket-side changes [1].

[1] pywebsocket-side: https://github.com/google/pywebsocket/pull/147
[2] Chromium-side: This CL.
BUG=567533
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_10_10_perf_bisect;tryserver.chromium.perf:win_perf_bisect
==========

to

==========
Use iframe in blink_perf.pywebsocket perf tests to remove --disable-web-security

Previously:
(a) util_performance_test.js in Blink runs performance tests using
(b) pywebsocket's scripts,
but this required --disable-web-security for cross-origin workers
because (a) and (b) have different origins.

We change this so that:
(a) util_performance_test.js creates
(c) <iframe> with src=pywebsocket's example/*_iframe.html that runs
    the performance tests on the iframe using
(b) pywebsocket's scripts.
Because (b) and (c) have the same origin (but (a) has a different origin),
Tests are run in the same-origin while we have an cross-origin iframe.

This CL adds pywebsocket-side iframe HTML/JavaScript files for (b) and (c). and
updates DEPS to include pywebsocket-side changes [1].

[1] pywebsocket-side: https://github.com/google/pywebsocket/pull/147
[2] Chromium-side: This CL.
BUG=567533
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, 2015-12-17 08:46:58]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-12-17 08:47:48]

Description was changed from

==========
Use iframe in blink_perf.pywebsocket perf tests to remove --disable-web-security

Previously:
(a) util_performance_test.js in Blink runs performance tests using
(b) pywebsocket's scripts,
but this required --disable-web-security for cross-origin workers
because (a) and (b) have different origins.

We change this so that:
(a) util_performance_test.js creates
(c) <iframe> with src=pywebsocket's example/*_iframe.html that runs
    the performance tests on the iframe using
(b) pywebsocket's scripts.
Because (b) and (c) have the same origin (but (a) has a different origin),
Tests are run in the same-origin while we have an cross-origin iframe.

This CL adds pywebsocket-side iframe HTML/JavaScript files for (b) and (c). and
updates DEPS to include pywebsocket-side changes [1].

[1] pywebsocket-side: https://github.com/google/pywebsocket/pull/147
[2] Chromium-side: This CL.
BUG=567533
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_10_10_perf_bisect;tryserver.chromium.perf:win_perf_bisect
==========

to

==========
Use iframe in blink_perf.pywebsocket perf tests to remove --disable-web-security

Previously:
(a) util_performance_test.js in Blink runs performance tests using
(b) pywebsocket's scripts,
but this required --disable-web-security for cross-origin workers
because (a) and (b) have different origins.

We change this so that:
(a) util_performance_test.js creates
(c) <iframe> with src=pywebsocket's example/*_iframe.html that runs
    the performance tests on the iframe using
(b) pywebsocket's scripts.
Because (b) and (c) have the same origin (but (a) has a different origin),
Tests are run in the same-origin while we have an cross-origin iframe.

This CL adds pywebsocket-side iframe HTML/JavaScript files for (b) and (c). and
updates DEPS to include pywebsocket-side changes [1].

[1] pywebsocket-side: https://github.com/google/pywebsocket/pull/147
[2] Chromium-side: This CL.
BUG=567533
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/76efe99397c323d99ba95a3eb0102207358aeb29
Cr-Commit-Position: refs/heads/master@{#365787}
==========

[commit-bot: I haz the power, 2015-12-17 08:47:49]

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