Bug 182604 - [GTK] imported/w3c/web-platform-tests/WebCryptoAPI/derive_bits_keys/pbkdf2.worker.html is flaky
Summary: [GTK] imported/w3c/web-platform-tests/WebCryptoAPI/derive_bits_keys/pbkdf2.wo...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-08 07:04 PST by Miguel Gomez
Modified: 2018-02-13 20:16 PST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Miguel Gomez 2018-02-08 07:04:19 PST
Varies between pass and crash.
Comment 1 Michael Catanzaro 2018-02-08 08:34:53 PST
Please do post the backtrace for the crash from the bots. Crash reports are not very useful without a backtrace.
Comment 2 Michael Catanzaro 2018-02-13 20:16:39 PST
It started failing when you added the crash expectation, because that overrode the toplevel expectations. You didn't do anything wrong there IMO, it was just bad luck; I think it's a waste of time to check the toplevel expectations for every change. I've changed our expectation to [ Pass Failure Slow Crash ].

(In reply to Michael Catanzaro from comment #1)
> Please do post the backtrace for the crash from the bots. Crash reports are
> not very useful without a backtrace.

There is never any backtrace:

https://build.webkit.org/results/GTK%20Linux%2064-bit%20Release%20(Tests)/r228270%20(5404)/imported/w3c/web-platform-tests/WebCryptoAPI/derive_bits_keys/pbkdf2.worker-crash-log.txt

https://build.webkit.org/results/GTK%20Linux%2064-bit%20Release%20(Tests)/r228257%20(5397)/imported/w3c/web-platform-tests/WebCryptoAPI/derive_bits_keys/pbkdf2.worker-crash-log.txt

https://build.webkit.org/results/GTK%20Linux%2064-bit%20Release%20(Tests)/r228237%20(5390)/imported/w3c/web-platform-tests/WebCryptoAPI/derive_bits_keys/pbkdf2.worker-crash-log.txt

It's not the only test this happens to. Something is wrong with the bots. (Perhaps it is missing network process crashes, or UI process crashes?)