| Summary: | [GTK] imported/w3c/web-platform-tests/WebCryptoAPI/derive_bits_keys/pbkdf2.worker.html is flaky | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Miguel Gomez <magomez> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW --- | ||
| Severity: | Normal | CC: | bugs-noreply, clopez, mcatanzaro |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
|
Description
Miguel Gomez
2018-02-08 07:04:19 PST
Please do post the backtrace for the crash from the bots. Crash reports are not very useful without a backtrace. 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?) |