Cache API tests: prepopulate cache in deterministic order

Cache API tests: prepopulate cache in deterministic order

Chrome and Firefox differ in the order in which cache keys() are
returned. Chrome orders by according to when the put()s were issued.
Firefox orders by when the body is complete. The test helper
prepopulated_cache_test did not guarantee that these matched, leading
to the tests being flaky in Firefox. This change tweaks the helper so
that the put()s are processed serially so that the order is
deterministic for both.

Spec issue: https://github.com/w3c/ServiceWorker/issues/823
BUG=655479
Review-Url: https://codereview.chromium.org/2806793002
Cr-Commit-Position: refs/heads/master@{#463195}
Committed: https://chromium.googlesource.com/chromium/src/+/5136241948671b538965c783e8aee27e88037aa9

[jsbell, 2017-04-07 20:59:44]

Description was changed from

==========
Cache API tests: prepopulate cache in deterministic order

Chrome and Firefox differ in the order in which cache keys() are
returned. Chrome orders by according to when the put()s were issued.
Firefox orders by when the body is complete. The test helper
prepopulated_cache_test did not guarantee that these matched, leading
to the tests being flaky in Firefox. This change tweaks the helper so
that the put()s are processed serially so that the order is
deterministic for both.

Spec issue: https://github.com/w3c/ServiceWorker/issues/823
==========

to

==========
Cache API tests: prepopulate cache in deterministic order

Chrome and Firefox differ in the order in which cache keys() are
returned. Chrome orders by according to when the put()s were issued.
Firefox orders by when the body is complete. The test helper
prepopulated_cache_test did not guarantee that these matched, leading
to the tests being flaky in Firefox. This change tweaks the helper so
that the put()s are processed serially so that the order is
deterministic for both.

Spec issue: https://github.com/w3c/ServiceWorker/issues/823
BUG=655479
==========

[jsbell, 2017-04-07 20:59:51]

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

[commit-bot: I haz the power, 2017-04-07 21:00:28]

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

[jsbell, 2017-04-07 21:02:01]

jsbell@chromium.org changed reviewers:
+ foolip@chromium.org

[jsbell, 2017-04-07 21:02:01]

foolip@ - can you review? (and cq if lg?)

This should address the failure seen at:

https://travis-ci.org/w3c/web-platform-tests/jobs/219426158

... and unblock this PR:

https://github.com/w3c/web-platform-tests/pull/5413

[commit-bot: I haz the power, 2017-04-07 22:04:18]

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

[commit-bot: I haz the power, 2017-04-07 22:04:19]

Dry run: This issue passed the CQ dry run.

[foolip, 2017-04-10 07:26:16]

The CQ bit was checked by foolip@chromium.org

[foolip, 2017-04-10 07:26:16]

lgtm

[commit-bot: I haz the power, 2017-04-10 07:26:30]

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-04-10 08:25:30]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1491809176123000, "parent_rev":
"112094796a99ff35f551467912814d08935b6055", "commit_rev":
"5136241948671b538965c783e8aee27e88037aa9"}

[commit-bot: I haz the power, 2017-04-10 08:26:20]

Description was changed from

==========
Cache API tests: prepopulate cache in deterministic order

Chrome and Firefox differ in the order in which cache keys() are
returned. Chrome orders by according to when the put()s were issued.
Firefox orders by when the body is complete. The test helper
prepopulated_cache_test did not guarantee that these matched, leading
to the tests being flaky in Firefox. This change tweaks the helper so
that the put()s are processed serially so that the order is
deterministic for both.

Spec issue: https://github.com/w3c/ServiceWorker/issues/823
BUG=655479
==========

to

==========
Cache API tests: prepopulate cache in deterministic order

Chrome and Firefox differ in the order in which cache keys() are
returned. Chrome orders by according to when the put()s were issued.
Firefox orders by when the body is complete. The test helper
prepopulated_cache_test did not guarantee that these matched, leading
to the tests being flaky in Firefox. This change tweaks the helper so
that the put()s are processed serially so that the order is
deterministic for both.

Spec issue: https://github.com/w3c/ServiceWorker/issues/823
BUG=655479

Review-Url: https://codereview.chromium.org/2806793002
Cr-Commit-Position: refs/heads/master@{#463195}
Committed:
https://chromium.googlesource.com/chromium/src/+/5136241948671b538965c783e8ae...
==========

[commit-bot: I haz the power, 2017-04-10 08:26:21]

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