RESOLVED FIXED 188047
[WPE] crypto/workers/subtle/hrsa-postMessage-worker.html is flaky
https://bugs.webkit.org/show_bug.cgi?id=188047
Summary [WPE] crypto/workers/subtle/hrsa-postMessage-worker.html is flaky
Miguel Gomez
Reported 2018-07-26 07:06:47 PDT
crypto/workers/subtle/hrsa-postMessage-worker.html [ Failure Pass ] The test fails on the first run like once every 10-20 times, and always passes the second one. The diff when it fails is: --- /home/buildbot/wpe/wpe-linux-64-release-tests/build/layout-test-results/crypto/workers/subtle/hrsa-postMessage-worker-expected.txt +++ /home/buildbot/wpe/wpe-linux-64-release-tests/build/layout-test-results/crypto/workers/subtle/hrsa-postMessage-worker-actual.txt @@ -3,6 +3,14 @@ On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE". +PASS All checks passed in worker for public key +PASS publicKey.type is 'public' +PASS publicKey.extractable is true +PASS publicKey.algorithm.name is 'RSASSA-PKCS1-v1_5' +PASS publicKey.algorithm.modulusLength is 2048 +PASS bytesToHexString(publicKey.algorithm.publicExponent) is '010001' +PASS publicKey.algorithm.hash.name is 'SHA-256' +PASS publicKey.usages is ['verify'] PASS All checks passed in worker for private key PASS privateKey.type is 'private' PASS privateKey.extractable is false @@ -11,14 +19,6 @@ PASS bytesToHexString(privateKey.algorithm.publicExponent) is '010001' PASS privateKey.algorithm.hash.name is 'SHA-256' PASS privateKey.usages is ['sign'] -PASS All checks passed in worker for public key -PASS publicKey.type is 'public' -PASS publicKey.extractable is true -PASS publicKey.algorithm.name is 'RSASSA-PKCS1-v1_5' -PASS publicKey.algorithm.modulusLength is 2048 -PASS bytesToHexString(publicKey.algorithm.publicExponent) is '010001' -PASS publicKey.algorithm.hash.name is 'SHA-256' -PASS publicKey.usages is ['verify'] PASS successfullyParsed is true TEST COMPLETE
Attachments
Diego Pino
Comment 1 2024-01-12 22:43:43 PST
The test(s) filed under this bug ticket have consistently passed for the last 4000 revisions. Currently, there are no more tests in TestExpectations that refer to this bug. Therefore, I'm closing the bug.
Note You need to log in before you can comment on or make changes to this bug.