[Webkit-unassigned] [Bug 213678] New: [GLIB] WebCryptoAPI tests failing after WPT update in r263598

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jun 26 22:51:52 PDT 2020


https://bugs.webkit.org/show_bug.cgi?id=213678

            Bug ID: 213678
           Summary: [GLIB] WebCryptoAPI tests failing after WPT update in
                    r263598
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: New Bugs
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: dpino at igalia.com

The following tests are failing:

  * imported/w3c/web-platform-tests/WebCryptoAPI/derive_bits_keys/hkdf.https.worker.html [ Failure ]
  * imported/w3c/web-platform-tests/WebCryptoAPI/derive_bits_keys/pbkdf2.https.any.html [ Failure ]
  * imported/w3c/web-platform-tests/WebCryptoAPI/derive_bits_keys/pbkdf2.https.any.worker.html [ Failure ]

The last two tests were added in the update. These tests have many passes but they fail on certain hashes schemes under certain sizes. Excerpt:

 PASS Derived key of type name: AES-KW length: 192  using long password, empty salt, SHA-256, with 100000 iterations with bad hash name SHA256 
 PASS Derived key of type name: AES-KW length: 192  using long password, empty salt, SHA-256, with 100000 iterations with missing deriveKey usage 
 PASS Derived key of type name: AES-KW length: 192  using long password, empty salt, SHA-256, with 100000 iterations with wrong (ECDH) key 
-PASS Derived key of type name: AES-KW length: 256  using long password, empty salt, SHA-256, with 100000 iterations 
+FAIL Derived key of type name: AES-KW length: 256  using long password, empty salt, SHA-256, with 100000 iterations assert_unreached: deriveKey failed with error OperationError: The operation failed for an operation-specific reason Reached unreachable code
 PASS Derived key of type name: AES-KW length: 256  using long password, empty salt, SHA-256, with 100000 iterations with bad hash name SHA256 
 PASS Derived key of type name: AES-KW length: 256  using long password, empty salt, SHA-256, with 100000 iterations with missing deriveKey usage 
 PASS Derived key of type name: AES-KW length: 256  using long password, empty salt, SHA-256, with 100000 iterations with wrong (ECDH) key 
-PASS Derived key of type name: HMAC hash: SHA-1 length: 256  using long password, empty salt, SHA-256, with 100000 iterations 
+FAIL Derived key of type name: HMAC hash: SHA-1 length: 256  using long password, empty salt, SHA-256, with 100000 iterations assert_unreached: deriveKey failed with error OperationError: The operation failed f
or an operation-specific reason Reached unreachable code
 PASS Derived key of type name: HMAC hash: SHA-1 length: 256  using long password, empty salt, SHA-256, with 100000 iterations with bad hash name SHA256 
 PASS Derived key of type name: HMAC hash: SHA-1 length: 256  using long password, empty salt, SHA-256, with 100000 iterations with missing deriveKey usage 
 PASS Derived key of type name: HMAC hash: SHA-1 length: 256  using long password, empty salt, SHA-256, with 100000 iterations with wrong (ECDH) key 
-PASS Derived key of type name: HMAC hash: SHA-256 length: 256  using long password, empty salt, SHA-256, with 100000 iterations 
+FAIL Derived key of type name: HMAC hash: SHA-256 length: 256  using long password, empty salt, SHA-256, with 100000 iterations assert_unreached: deriveKey failed with error OperationError: The operation failed for an operation-specific reason Reached unreachable code
 PASS Derived key of type name: HMAC hash: SHA-256 length: 256  using long password, empty salt, SHA-256, with 100000 iterations with bad hash name SHA256 
 PASS Derived key of type name: HMAC hash: SHA-256 length: 256  using long password, empty salt, SHA-256, with 100000 iterations with missing deriveKey usage 
 PASS Derived key of type name: HMAC hash: SHA-256 length: 256  using long password, empty salt, SHA-256, with 100000 iterations with wrong (ECDH) key 
-PASS Derived key of type name: HMAC hash: SHA-384 length: 256  using long password, empty salt, SHA-256, with 100000 iterations 
+FAIL Derived key of type name: HMAC hash: SHA-384 length: 256  using long password, empty salt, SHA-256, with 100000 iterations assert_unreached: deriveKey failed with error OperationError: The operation failed
 for an operation-specific reason Reached unreachable code
 PASS Derived key of type name: HMAC hash: SHA-384 length: 256  using long password, empty salt, SHA-256, with 100000 iterations with bad hash name SHA256 
 PASS Derived key of type name: HMAC hash: SHA-384 length: 256  using long password, empty salt, SHA-256, with 100000 iterations with missing deriveKey usage 
 PASS Derived key of type name: HMAC hash: SHA-384 length: 256  using long password, empty salt, SHA-256, with 100000 iterations with wrong (ECDH) key 
-PASS Derived key of type name: HMAC hash: SHA-512 length: 256  using long password, empty salt, SHA-256, with 100000 iterations 
+FAIL Derived key of type name: HMAC hash: SHA-512 length: 256  using long password, empty salt, SHA-256, with 100000 iterations assert_unreached: deriveKey failed with error OperationError: The operation failed
 for an operation-specific reason Reached unreachable code
 PASS Derived key of type name: HMAC hash: SHA-512 length: 256  using long password, empty salt, SHA-256, with 100000 iterations with bad hash name SHA256 
 PASS Derived key of type name: HMAC hash: SHA-512 length: 256  using long password, empty salt, SHA-256, with 100000 iterations with missing deriveKey usage 
 PASS Derived key of type name: HMAC hash: SHA-512 length: 256  using long password, empty salt, SHA-256, with 100000 iterations with wrong (ECDH) key 

So to not hide these failures I prefer not to emit a baseline for those tests.

With regard to imported/w3c/web-platform-tests/WebCryptoAPI/derive_bits_keys/hkdf.https.worker.html, it had an own GLIB baseline with results better than the general baseline, but now is the opposite. It seems the test is not running properly:

Actual: https://build.webkit.org/results/GTK%20Linux%2064-bit%20Release%20(Tests)/r263609%20(14319)/imported/w3c/web-platform-tests/WebCryptoAPI/derive_bits_keys/hkdf.https.worker-actual.txt

layer at (0,0) size 800x600
  RenderView at (0,0) size 800x600
layer at (0,0) size 800x600
  RenderBlock {HTML} at (0,0) size 800x600
    RenderBody {BODY} at (8,8) size 784x579
      RenderBlock {PRE} at (0,0) size 784x15
        RenderText {#text} at (0,0) size 312x15
          text run at (0,0) width 312: "{\"error\": {\"message\": \"\", \"code\": 404}}"

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20200627/101fd5b5/attachment-0001.htm>


More information about the webkit-unassigned mailing list