Cache Storage API tests: Fix WPT test bugs, remove redundant local copies

Cache Storage API tests: Fix WPT test bugs, remove redundant local copies

* Use promise_rejects consistently and fix parameters.
* Don't use .php in upstreamed tests.
* Add additional test cases from blink's copies.
* Tightened up assertions about result array ordering.
* Remove blink's redundant copies of tests.

I left the credentials tests alone since Blink is mid-deprecation.

BUG=655479
R=jkarlin@chromium.org

Review-Url: https://codereview.chromium.org/2790143003
Cr-Commit-Position: refs/heads/master@{#462593}
Committed: https://chromium.googlesource.com/chromium/src/+/44c004f971b6a204a8802b0fad4cac0401b17771

[jsbell, 2017-04-04 00:00:03]

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

[commit-bot: I haz the power, 2017-04-04 00:00:41]

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-04 00:07:13]

jkarlin@ - can you take a look?

[commit-bot: I haz the power, 2017-04-04 01:01:42]

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

[commit-bot: I haz the power, 2017-04-04 01:01:45]

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_...)

[jkarlin, 2017-04-05 18:10:17]

lgtm!

[jsbell, 2017-04-06 18:18:14]

The CQ bit was checked by jsbell@chromium.org

[commit-bot: I haz the power, 2017-04-06 18:19: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, 2017-04-06 19:52:10]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1491502694905730, "parent_rev":
"a1597ec0c31e6d96f3fdba7c34c4d1b28dc52b4f", "commit_rev":
"44c004f971b6a204a8802b0fad4cac0401b17771"}

[commit-bot: I haz the power, 2017-04-06 19:52:59]

Description was changed from

==========
Cache Storage API tests: Fix WPT test bugs, remove redundant local copies

* Use promise_rejects consistently and fix parameters.
* Don't use .php in upstreamed tests.
* Add additional test cases from blink's copies.
* Tightened up assertions about result array ordering.
* Remove blink's redundant copies of tests.

I left the credentials tests alone since Blink is mid-deprecation.

BUG=655479
R=jkarlin@chromium.org
==========

to

==========
Cache Storage API tests: Fix WPT test bugs, remove redundant local copies

* Use promise_rejects consistently and fix parameters.
* Don't use .php in upstreamed tests.
* Add additional test cases from blink's copies.
* Tightened up assertions about result array ordering.
* Remove blink's redundant copies of tests.

I left the credentials tests alone since Blink is mid-deprecation.

BUG=655479
R=jkarlin@chromium.org

Review-Url: https://codereview.chromium.org/2790143003
Cr-Commit-Position: refs/heads/master@{#462593}
Committed:
https://chromium.googlesource.com/chromium/src/+/44c004f971b6a204a8802b0fad4c...
==========

[commit-bot: I haz the power, 2017-04-06 19:53:01]

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

[jeffcarp, 2017-04-06 21:54:55]

On 2017/04/06 at 19:53:01, commit-bot wrote:
> Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/44c004f971b6a204a8802b0fad4c...

A WPT PR was created on GitHub but the results came back unstable, keeping this
from being exported:
https://github.com/w3c/web-platform-tests/pull/5413

[jsbell, 2017-04-07 16:56:20]

On 2017/04/06 21:54:55, jeffcarp wrote:
> On 2017/04/06 at 19:53:01, commit-bot wrote:
> > Committed patchset #1 (id:1) as
>
https://chromium.googlesource.com/chromium/src/+/44c004f971b6a204a8802b0fad4c...
> 
> A WPT PR was created on GitHub but the results came back unstable, keeping
this
> from being exported:
> https://github.com/w3c/web-platform-tests/pull/5413

Looks like all the failures are c/o cache-keys.js (all the variants).

I'll see if I can repro the flakiness in FF and if the test can be fixed.

[jsbell, 2017-04-07 19:13:10]

On 2017/04/07 16:56:20, jsbell wrote:
> Looks like all the failures are c/o cache-keys.js (all the variants).
> 
> I'll see if I can repro the flakiness in FF and if the test can be fixed.

My dev box is offline at the moment; the failures look like FF not returning
keys in insertion order. I haven't found a bug for that yet, though...