this test is marked a timeout on all platforms. I ran it locally on windows 10 and I didn't see a timeout in the summary when the test ended, I did see many of these failed subtests:
Can wrap and unwrap ECDSA public key keys using spki and RSA-OAEP assert_unreached: Round trip for extractable key threw an error - NotSupportedError: "Operation is not supported" Reached unreachable code

testWrapping/</</</<@https://web-platform.test:8443/WebCryptoAPI/wrapKey_unwrapKey/wrapKey_unwrapKey.js:154:45
promise callbacktestWrapping/</</<@https://web-platform.test:8443/WebCryptoAPI/wrapKey_unwrapKey/wrapKey_unwrapKey.js:151:28
Test.prototype.step@https://web-platform.test:8443/resources/testharness.js:1958:25
promise_test/tests.promise_tests</<@https://web-platform.test:8443/resources/testharness.js:605:36
promise_test/tests.promise_tests<@https://web-platform.test:8443/resources/testharness.js:604:20
promise callbackpromise_test@https://web-platform.test:8443/resources/testharness.js:603:51
testWrapping/</<@https://web-platform.test:8443/WebCryptoAPI/wrapKey_unwrapKey/wrapKey_unwrapKey.js:144:33
promise callbacktestWrapping/<@https://web-platform.test:8443/WebCryptoAPI/wrapKey_unwrapKey/wrapKey_unwrapKey.js:141:54
testWrapping@https://web-platform.test:8443/WebCryptoAPI/wrapKey_unwrapKey/wrapKey_unwrapKey.js:139:36
run_test/</</<@https://web-platform.test:8443/WebCryptoAPI/wrapKey_unwrapKey/wrapKey_unwrapKey.js:17:31
run_test/</<@https://web-platform.test:8443/WebCryptoAPI/wrapKey_unwrapKey/wrapKey_unwrapKey.js:16:18
run_test/<@https://web-platform.test:8443/WebCryptoAPI/wrapKey_unwrapKey/wrapKey_unwrapKey.js:15:18
promise callbackrun_test@https://web-platform.test:8443/WebCryptoAPI/wrapKey_unwrapKey/wrapKey_unwrapKey.js:13:6
@https://web-platform.test:8443/WebCryptoAPI/wrapKey_unwrapKey/wrapKey_unwrapKey.https.worker.js:5:1

and from the command prompt, I see this output:
web-platform-tests CT,,

0:56.04 INFO Application command: c:/Users/elvis/mozilla-central/obj-x86_64-pc-mingw32\dist\bin\firefox.exe -marionette about:blank --wait-for-browser -profile c:\users\elvis\appdata\local\temp\tmpek9k85
0:56.07 INFO Starting runner
1:08.24 pid:19104 Full command: c:/Users/elvis/mozilla-central/obj-x86_64-pc-mingw32\dist\bin\firefox.exe -marionette about:blank --wait-for-browser -profile c:\users\elvis\appdata\local\temp\tmpek9k85
pid:19104 [Parent 5412, Gecko_IOThread] WARNING: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_win.cc, line 166
1:10.60 pid:19104 1587497398854 Marionette INFO Listening on port 54149
1:11.97 TEST_START: /WebCryptoAPI/wrapKey_unwrapKey/wrapKey_unwrapKey.https.worker.html
2:13.30 TEST_END: Test TIMEOUT. Subtests passed 160/223. Unexpected 0
2:13.31 INFO Pausing until the browser exits

I am not sure why we have a timeout, maybe this is something wrong in the web platform tests harness.

:ckerschb, this is probably like 1631882, maybe this is something you can figure out or know someone who can?

(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #1)

:ckerschb, this is probably like 1631882, maybe this is something you can figure out or know someone who can?

JC, can you guide provide some input on what to do with failing WebCrypto tests?

We have a contractor who will be working on WebCrypto web platform test compliance in the next quarter or so. Moving into that component. Thanks!

thanks :jcj, is the timeline to fix by end of June or sometime before the end of the year? I ask as I could move this to 'backlog' where it runs on all m-c pushes normally, but not by default on try and autoland- saving jobs from running tests that are blocked on a timeout.

run WebCryptoAPI/wrapKey_unwrapKey/wrapKey_unwrapKey.https.worker.js as backlog (tier-2).

The severity field is not set for this bug.
:jcj, could you have a look please?

For more information, please visit auto_nag documentation.

End of year, I think. Thanks, Joel!

https://hg.mozilla.org/mozilla-central/rev/549b3c1f2751