RawResourceTest: Use loadingTaskRunner to be balanced with Resource

RawResourceTest: Use loadingTaskRunner to be balanced with Resource

ResourceCallback::schedule() was changed to use loadingTaskRunner
instead of Timer, but RawResourceTest is still using a Timer to remove
a client from a Resource. Since tests expects tasks are scheduled
sequentially, we should use the same infrastructure to run asynchronous
tasks for both Resource and tests.

Tests work without task reordering at this point, but tests fail
due to reordering if this file is moved under platform and run with
TestingPlatformSupportWithMockScheduler.

TEST=webkit_unit_tests --ftest_filter=RawResourceTest.AddClientDuringCallback
BUG=655920
Review-Url: https://codereview.chromium.org/2631093004
Cr-Commit-Position: refs/heads/master@{#444022}
Committed: https://chromium.googlesource.com/chromium/src/+/2a568e5096fc65ebf8f338288000dac8fffadc84

[Takashi Toyoshima, 2017-01-17 08:19:08]

Description was changed from

==========
RawResourceTest: Use loadingTaskRunner to be balanced with Resource

ResourceCallback::schedule() was changed to use loadingTaskRunner
instead of Timer, but RawResourceTest is sill use a Timer to remove
a client from a Resource. Since tests expects tasks are scheduled
sequentially, we should use the same infrastructure to run asynchronous
tasks for both Resource and tests.

Tests work without task reordering at this point, but tests fail
due to reordering if this file is moved under platform and run with
TestingPlatformSupportWithMockScheduler.

TEST=webkit_unit_tests --ftest_filter=RawResourceTest.AddClientDuringCallback
BUG=655920
==========

to

==========
RawResourceTest: Use loadingTaskRunner to be balanced with Resource

ResourceCallback::schedule() was changed to use loadingTaskRunner
instead of Timer, but RawResourceTest is sill use a Timer to remove
a client from a Resource. Since tests expects tasks are scheduled
sequentially, we should use the same infrastructure to run asynchronous
tasks for both Resource and tests.

Tests work without task reordering at this point, but tests fail
due to reordering if this file is moved under platform and run with
TestingPlatformSupportWithMockScheduler.

TEST=webkit_unit_tests --ftest_filter=RawResourceTest.AddClientDuringCallback
BUG=655920
==========

[Takashi Toyoshima, 2017-01-17 08:19:08]

toyoshim@chromium.org changed reviewers:
+ yhirano@chromium.org

[Takashi Toyoshima, 2017-01-17 08:19:14]

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

[commit-bot: I haz the power, 2017-01-17 08:19:21]

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

[Takashi Toyoshima, 2017-01-17 08:19:42]

PTAL

[commit-bot: I haz the power, 2017-01-17 09:16:53]

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

[commit-bot: I haz the power, 2017-01-17 09:16:54]

Dry run: This issue passed the CQ dry run.

[yhirano, 2017-01-17 10:04:21]

On 2017/01/17 08:19:42, toyoshim wrote:
> PTAL

LGTM

s/is sill use/is still using/

[Takashi Toyoshima, 2017-01-17 10:58:10]

Description was changed from

==========
RawResourceTest: Use loadingTaskRunner to be balanced with Resource

ResourceCallback::schedule() was changed to use loadingTaskRunner
instead of Timer, but RawResourceTest is sill use a Timer to remove
a client from a Resource. Since tests expects tasks are scheduled
sequentially, we should use the same infrastructure to run asynchronous
tasks for both Resource and tests.

Tests work without task reordering at this point, but tests fail
due to reordering if this file is moved under platform and run with
TestingPlatformSupportWithMockScheduler.

TEST=webkit_unit_tests --ftest_filter=RawResourceTest.AddClientDuringCallback
BUG=655920
==========

to

==========
RawResourceTest: Use loadingTaskRunner to be balanced with Resource

ResourceCallback::schedule() was changed to use loadingTaskRunner
instead of Timer, but RawResourceTest is still using a Timer to remove
a client from a Resource. Since tests expects tasks are scheduled
sequentially, we should use the same infrastructure to run asynchronous
tasks for both Resource and tests.

Tests work without task reordering at this point, but tests fail
due to reordering if this file is moved under platform and run with
TestingPlatformSupportWithMockScheduler.

TEST=webkit_unit_tests --ftest_filter=RawResourceTest.AddClientDuringCallback
BUG=655920
==========

[Takashi Toyoshima, 2017-01-17 10:58:32]

The CQ bit was checked by toyoshim@chromium.org

[commit-bot: I haz the power, 2017-01-17 10:58:45]

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, 2017-01-17 11:08:03]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1484650712280190, "parent_rev":
"0401e95afc66f0b87733d04fad5d233c04d35aa3", "commit_rev":
"2a568e5096fc65ebf8f338288000dac8fffadc84"}

[commit-bot: I haz the power, 2017-01-17 11:08:37]

Description was changed from

==========
RawResourceTest: Use loadingTaskRunner to be balanced with Resource

ResourceCallback::schedule() was changed to use loadingTaskRunner
instead of Timer, but RawResourceTest is still using a Timer to remove
a client from a Resource. Since tests expects tasks are scheduled
sequentially, we should use the same infrastructure to run asynchronous
tasks for both Resource and tests.

Tests work without task reordering at this point, but tests fail
due to reordering if this file is moved under platform and run with
TestingPlatformSupportWithMockScheduler.

TEST=webkit_unit_tests --ftest_filter=RawResourceTest.AddClientDuringCallback
BUG=655920
==========

to

==========
RawResourceTest: Use loadingTaskRunner to be balanced with Resource

ResourceCallback::schedule() was changed to use loadingTaskRunner
instead of Timer, but RawResourceTest is still using a Timer to remove
a client from a Resource. Since tests expects tasks are scheduled
sequentially, we should use the same infrastructure to run asynchronous
tasks for both Resource and tests.

Tests work without task reordering at this point, but tests fail
due to reordering if this file is moved under platform and run with
TestingPlatformSupportWithMockScheduler.

TEST=webkit_unit_tests --ftest_filter=RawResourceTest.AddClientDuringCallback
BUG=655920

Review-Url: https://codereview.chromium.org/2631093004
Cr-Commit-Position: refs/heads/master@{#444022}
Committed:
https://chromium.googlesource.com/chromium/src/+/2a568e5096fc65ebf8f338288000...
==========

[commit-bot: I haz the power, 2017-01-17 11:08:38]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/2a568e5096fc65ebf8f338288000...