Closed Bug 1461325 Opened 7 years ago Closed 7 years ago

[wpt-sync] Sync PR 10984 - WebCryptoAPI: Use .any.js for generateKey tests and split up slow tests

Categories

(Core :: DOM: Security, enhancement, P4)

Product:
Core
Component:
DOM: Security
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla62
Tracking Flags:
Tracking Status
firefox62 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream][domsecurity-backlog])

Sync web-platform-tests PR 10984 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/w3c/web-platform-tests/pull/10984 Details from upstream follow. Simon Pieters <zcorpan@gmail.com> wrote: > WebCryptoAPI: Use .any.js for generateKey tests and split up slow tests > > Slow tests test 10 subtests at a time, using the `// META: variant=...` > feature. > > Fixes #10794.
Component: web-platform-tests → DOM: Security
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream error][domsecurity-backlog]
Whiteboard: [wptsync downstream error][domsecurity-backlog] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream][domsecurity-backlog]
Ran 82 tests and 6711 subtests OK : 82 PASS : 1422 FAIL : 5289 (truncated for maximum comment length)
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/0b965b2fbe32 [wpt PR 10984] - WebCryptoAPI: Use .any.js for generateKey tests and split up slow tests, a=testonly https://hg.mozilla.org/integration/mozilla-inbound/rev/f213eb537df6 [wpt PR 10984] - Update wpt metadata, a=testonly
https://hg.mozilla.org/mozilla-central/rev/0b965b2fbe32 https://hg.mozilla.org/mozilla-central/rev/f213eb537df6
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox62: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
You need to log in before you can comment on or make changes to this bug.