Closed Bug 1364258 Opened 5 years ago Closed 4 years ago

Intermittent test_ecdsa.https.html | importVectorKeys step: ECDSA P-521 with SHA-256 using privateKey to verify - assert_unreached: importVectorKeys failed for ECDSA P-521 with SHA-256. Message: ''Operation is not supported'' Reached unreachable code

Categories

(Core :: DOM: Security, defect, P3)

Product:
Core
Component:
DOM: Security
Type:
defect

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [stockwell disabled],[domsecurity-intermittent])

Attachments

(1 file)

disable test
680 bytes, patch
jmaher
: review+
Details | Diff | Splinter Review 
This seems to have started with the test update in bug 1363982.
Blocks: 1363982
this is a perma fail on linux64 code coverage, likewise a frequent failure on linux64 debug (both non-e10s and e10s).
Component: web-platform-tests → DOM: Security
Product: Testing → Core
Whiteboard: [stockwell needswork]
Version: Version 3 → unspecified
I see this was added to web-platform-tests:
https://github.com/w3c/web-platform-tests/commit/ea527511d7f742f5ad939339df3bad2619382a00

Philip, do you have ideas on how to resolve issues seen in this log:
https://queue.taskcluster.net/v1/task/QOWHguPmR_GqQ6PwJeuWCQ/runs/0/artifacts/public/logs/live_backing.log

specifically this error:
[task 2017-05-18T18:59:47.578247Z] 18:59:47     INFO - PID 1143 | ++DOMWINDOW == 30 (0x5708140) [pid = 1143] [serial = 30] [outer = 0x55fc4d0]
[task 2017-05-18T18:59:47.901520Z] 18:59:47     INFO - PID 1143 | ++DOCSHELL 0x2f10d80 == 11 [pid = 1143] [id = {121e3946-3626-496e-8d04-c3553baa3fe8}]
[task 2017-05-18T18:59:47.901980Z] 18:59:47     INFO - PID 1143 | ++DOMWINDOW == 31 (0x7781fc0) [pid = 1143] [serial = 31] [outer = (nil)]
[task 2017-05-18T18:59:47.937642Z] 18:59:47     INFO - PID 1143 | ++DOMWINDOW == 32 (0x33d7aa0) [pid = 1143] [serial = 32] [outer = 0x7781fc0]
[task 2017-05-18T18:59:48.086518Z] 18:59:48     INFO - PID 1143 | ++DOMWINDOW == 33 (0x38b68c0) [pid = 1143] [serial = 33] [outer = 0x7781fc0]
[task 2017-05-18T18:59:48.411575Z] 18:59:48     INFO - PID 1143 | JavaScript warning: https://web-platform.test:8443/WebCryptoAPI/sign_verify/ecdsa.js, line 478: unreachable code after return statement
[task 2017-05-18T18:59:48.414830Z] 18:59:48     INFO - PID 1143 | JavaScript warning: https://web-platform.test:8443/WebCryptoAPI/sign_verify/ecdsa.js, line 478: unreachable code after return statement
[task 2017-05-18T18:59:49.264570Z] 18:59:49     INFO - 
[task 2017-05-18T18:59:49.265041Z] 18:59:49     INFO - TEST-FAIL | /WebCryptoAPI/sign_verify/test_ecdsa.https.html | importVectorKeys step: ECDSA P-521 with SHA-512 with altered plaintext after call - assert_unreached: importVectorKeys failed for ECDSA P-521 with SHA-512. Message: ''Operation is not supported'' Reached unreachable code
[task 2017-05-18T18:59:49.265319Z] 18:59:49     INFO - run_test/</promise</<@https://web-platform.test:8443/WebCryptoAPI/sign_verify/ecdsa.js:84:17
[task 2017-05-18T18:59:49.265924Z] 18:59:49     INFO - Test.prototype.step@https://web-platform.test:8443/resources/testharness.js:1405:20
[task 2017-05-18T18:59:49.266318Z] 18:59:49     INFO - promise_test/tests.promise_tests<@https://web-platform.test:8443/resources/testharness.js:529:27
[task 2017-05-18T18:59:49.266583Z] 18:59:49     INFO - promise callback*promise_test@https://web-platform.test:8443/resources/testharness.js:525:31
[task 2017-05-18T18:59:49.266984Z] 18:59:49     INFO - run_test/</promise<@https://web-platform.test:8443/WebCryptoAPI/sign_verify/ecdsa.js:83:13
[task 2017-05-18T18:59:49.267326Z] 18:59:49     INFO - promise callback*run_test/<@https://web-platform.test:8443/WebCryptoAPI/sign_verify/ecdsa.js:67:23
[task 2017-05-18T18:59:49.267627Z] 18:59:49     INFO - run_test@https://web-platform.test:8443/WebCryptoAPI/sign_verify/ecdsa.js:66:5
[task 2017-05-18T18:59:49.267878Z] 18:59:49     INFO - @https://web-platform.test:8443/WebCryptoAPI/sign_verify/test_ecdsa.https.html:18:1
[task 2017-05-18T18:59:49.268231Z] 18:59:49     INFO - TEST-FAIL | /WebCryptoAPI/sign_verify/test_ecdsa.https.html | importVectorKeys step: ECDSA P-256 with SHA-1 using privateKey to verify - assert_unreached: importVectorKeys failed for ECDSA P-256 with SHA-1. Message: ''Operation is not supported'' Reached unreachable code


Keep in mind when we run this test on a build with gcov enabled this is a permanent failure, otherwise this shows up about one out of 20 times in normal automation.
Flags: needinfo?(philip)
Priority: -- → P3
Whiteboard: [stockwell needswork] → [stockwell needswork],[domsecurity-intermittent]
Attached patch disable test — — Splinter Review
Attachment #8872700 - Flags: review?(jmaher)
Comment on attachment 8872700 [details] [diff] [review]
disable test

Review of attachment 8872700 [details] [diff] [review]:
-----------------------------------------------------------------

thanks!
Attachment #8872700 - Flags: review?(jmaher) → review+
Pushed by gbrown@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/1f21438018cb
Disable wpt test_ecdsa.https.html; r=jmaher
Keywords: leave-open
Whiteboard: [stockwell needswork],[domsecurity-intermittent] → [stockwell disabled],[domsecurity-intermittent]
Oops, I didn't notice the needinfo request in comment 6 until now. I don't know much about the Web Crypoto API, but is this test still flaky?

Handing over to James Graham as a better generic wpt contact for Gecko.
Flags: needinfo?(philip) → needinfo?(james)
This got disabled.
Flags: needinfo?(james)
The leave-open keyword is there and there is no activity for 6 months.
:ckerschb, maybe it's time to close this bug?
Flags: needinfo?(ckerschb)
(In reply to Release mgmt bot [:sylvestre / :calixte] from comment #15)
> The leave-open keyword is there and there is no activity for 6 months.
> :ckerschb, maybe it's time to close this bug?

Yeah, given that the test has been disabled I guess we can mark this one as invalid.
Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(ckerschb)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.