New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 694603 link

Starred by 5 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: 7
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocked on:
issue 524758



Sign in to add a comment

experiment with 10x testing for layout tests

Project Member Reported by estaab@chromium.org, Feb 21 2017

Issue description

Test flakiness is being masked by retries at different layers. There is a proposal to instead require tests to pass multiple times, preventing flakiness from ever getting committed in the repo: https://docs.google.com/document/d/1CR0pKaC1bZ8Mk2-tbmrKJlqMH8UNwvATlUJ-56qVrjI/edit#heading=h.fdobmxs62fu

Thoughts on prototyping this idea:
* Add a src/third_party/WebKit/LayoutTests/10xTestExpectations of all existing flaky layout tests
* Add a 10x mode to layout tests runner. Blacklisted tests won't be run but existing good tests and all new tests will
* Add an experimental builder to tryserver.chromium.linux (or tryserver.chromium.fyi if the split happens first) that runs layout tests, passing in a property to run in 10x mode
 

Comment 1 by kbr@chromium.org, Feb 21 2017

Cc: kbr@chromium.org
Cc: serg...@chromium.org

Comment 3 by w...@chromium.org, Jul 11 2017

See also 697215, filed for removing the retries from the standard bot test runs, except for explicitly-annotated tests.

FWIW I've spent a few days debugging  issue 740692 , which boiled down to raciness in some threaded tests - I'm not sure that running them 10x would necessarily spot the issues, which only showed up for me due to platform thread scheduling differences, though.

Sign in to add a comment