Mark flaky WebXR tests as slow #17277
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wpt-pr-bot
approved these changes
Jun 12, 2019
The chromium flakiness dashboard reports that these tests are flaky with the longest running test taking 6 seconds (or always timing out), and guidance appears to be that if it takes longer than two seconds on release that it should be tagged as a "slow" test. Unfortunately, local machines appear to have no problem with the tests. The first step here is to see if increasing these test timeouts will cause these tests to become less flaky. Bug:961015 Change-Id: I17c2960f3420501b6ff7b381f72845d0432d3004
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-1653603
branch
from
09e06c1
to
27741a0
Compare
|
Close this PR because the Chromium CL has been abandoned. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The chromium flakiness dashboard reports that these tests are flaky with
the longest running test taking 6 seconds (or always timing out), and
guidance appears to be that if it takes longer than two seconds on
release that it should be tagged as a "slow" test. Unfortunately,
local machines appear to have no problem with the tests. The first
step here is to see if increasing these test timeouts will cause these
tests to become less flaky.
Bug:961015
Change-Id: I17c2960f3420501b6ff7b381f72845d0432d3004
Reviewed-on: https://chromium-review.googlesource.com/1653603
WPT-Export-Revision: 6516bfd33cfb8fc0ae4e2946bb59efe5ebd2d766