"external/wpt/WebCryptoAPI/generateKey/test_successes_RSA-OAEP.https.html" is flaky |
|||||
Issue description"external/wpt/WebCryptoAPI/generateKey/test_successes_RSA-OAEP.https.html" is flaky. This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label. We have detected 10 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyUwsSBUZsYWtlIkhleHRlcm5hbC93cHQvV2ViQ3J5cHRvQVBJL2dlbmVyYXRlS2V5L3Rlc3Rfc3VjY2Vzc2VzX1JTQS1PQUVQLmh0dHBzLmh0bWwM. Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs
,
May 1 2017
Recently added Web Platform Test. Adding to TestExpectations https://codereview.chromium.org/2852923002
,
May 1 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/5cd4491a218e2a895253b33d45da1727e0d98176 commit 5cd4491a218e2a895253b33d45da1727e0d98176 Author: suzyh <suzyh@chromium.org> Date: Mon May 01 04:37:30 2017 Add flaky WebCryptoAPI in TestExpectations Recently imported external/wpt/WebCryptoAPI/generateKey/test_successes_RSA-OAEP.https.html is occasionally timing out, so adding to TestExpectations. TBR=eroman@chromium.org BUG=716729 Review-Url: https://codereview.chromium.org/2852923002 Cr-Commit-Position: refs/heads/master@{#468284} [modify] https://crrev.com/5cd4491a218e2a895253b33d45da1727e0d98176/third_party/WebKit/LayoutTests/TestExpectations
,
May 3 2017
The test in question generates a ton of RSA (2048-bit) keys, and is expected to take a long time (order of minutes even). So this sounds like it is working as intended. Is there any way to see a distribution of test run times? As far as resolution, I don't see any implementation problem to fix here. Possible solutions may be: (1) Change the upstream WPT test, so it is split into a number of smaller tests (so more likely to fit within the timeout window). (2) Increase the timeout for this particular test - how do we do that? The W3C test framework seems to have a mechanism for doing that, and in fact this test already sets something. Is there something missing? Is there a way to see the distribution of test run durations so we can see how much more timeout this needs?
,
May 3 2017
qyearsley: what would you advise?
,
Jun 13 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by chromium...@appspot.gserviceaccount.com
, Apr 30 2017