Today when I run the auto-gardener I noticed no tests with failures but LOTS of timeouts, all allegedly from the same revision range (r235407-235410). I found no obvious responsible commit in the range, so I built the last commit of that range in my machine, run the tests... and they look fine, so I'm suspecting something is wrong in our bots.
*** This bug has been marked as a duplicate of bug 189063 ***
(In reply to Alicia Boya García from comment #0) > I built the last commit > of that range in my machine, run the tests... and they look fine, so I'm > suspecting something is wrong in our bots. I was able to reproduce when running the tests locally (see bug #189063). Not sure why you weren't.
[Release] (HEAD detached at 1b5109a8ae1) $ run-webkit-tests compositing/layer-creation/mismatched-rotated-transform-animation-overlap.html editing/style/set-backColor-with-color-filter.html No handlers could be found for logger "webkitpy.thirdparty.autoinstalled.keyring.backend" Using port 'gtk-wk2' Test configuration: <, x86, release> Placing test results in /webkit/WebKitBuild/Release/layout-test-results Baseline search path: platform/gtk -> platform/wk2 -> generic Using Release build Pixel tests disabled Regular timeout: 15000, slow test timeout: 75000 Command line: /webkit/Tools/jhbuild/jhbuild-wrapper --gtk run /webkit/WebKitBuild/Release/bin/WebKitTestRunner - Found 2 tests; running 2, skipping 0. Running 2 tests Running 2 WebKitTestRunners in parallel. All 2 tests ran as expected.
If you run all the tests together, the difference in results should become apparent.
(In reply to Michael Catanzaro from comment #4) > If you run all the tests together, the difference in results should become > apparent. I can confirm that it reproduces when running all the tests... although that takes hours.