[webkit-dev] Why is HTMLHtmlElement.manifest exposed to the DOM?

On Tue, Dec 3, 2013 at 1:04 PM, Peter Beverloo pe...@chromium.org wrote: The HTMLHtmlElement.manifest property indeed doesn't seem to be defined anywhere. It was added by Darin Adler a few years ago http://src.chromium.org/viewvc/blink?view=revisionrevision=66327 Reading the change log it

[webkit-dev] Test flakiness.

Hey everyone, I've noticed the following build message: Unexpected flakiness: text-only failures (1) platform/mac/accessibility/search-predicate-element-count.html [ Failure Pass ] Oddly, when this test is run ALONE (locally of course), it always passes. Yet, sometimes when run with other

Re: [webkit-dev] Test flakiness.

On Dec 3, 2013, at 1:51 PM, Samuel White samuel_wh...@apple.com wrote: Hey everyone, I've noticed the following build message: Unexpected flakiness: text-only failures (1) platform/mac/accessibility/search-predicate-element-count.html [ Failure Pass ] Oddly, when this test is run

Re: [webkit-dev] Test flakiness.

03 дек. 2013 г., в 14:11, Tim Horton timothy_hor...@apple.com написал(а): It would be ideal if you could figure out *why* the test is flaky. What state are the tests that run before it setting that isn’t getting reset? Can you narrow it down to a pair of tests? One way to do this is to run

Re: [webkit-dev] Test flakiness.

Thanks for the tips Alexey. I suspected order was to blame and wrote a script to run all the LayoutTests/platform/mac/accessibility tests as tuples with the flaky test coming second. The winning combination that reproduces the flaky failure for me: Tools/Scripts/run-webkit-tests --debug