Detected 3 new flakes for test/step "screenshot_sync_tests (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyLQsSBUZsYWtlIiJzY3JlZW5zaG90X3N5bmNfdGVzdHMgKHdpdGggcGF0Y2gpDA. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).

Detected 3 new flakes for test/step "screenshot_sync_tests (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyLQsSBUZsYWtlIiJzY3JlZW5zaG90X3N5bmNfdGVzdHMgKHdpdGggcGF0Y2gpDA. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).

Failures are
ScreenshotSync.WithCanvas
ScreenshotSync.WithDivs

The timing of this latest stretch of flakiness lines up with  issue 614393 .

The patchset attached to the first in this stretch is https://codereview.chromium.org/2005853003/ which added debugging. This was reverted in https://codereview.chromium.org/2015983002/ which approximately lines up with the end of the stretch of flakiness, so that may be all it is.

erikchen: can you investigate/confirm?

Detected 3 new flakes for test/step "screenshot_sync_tests (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyLQsSBUZsYWtlIiJzY3JlZW5zaG90X3N5bmNfdGVzdHMgKHdpdGggcGF0Y2gpDA. This message was posted automatically by the chromium-try-flakes app.

If my debugging CL is causing flakiness in *screenshot_sync_tests*, then something is /very/ broken with screenshot_sync_tests. 

My CLs only affect Windows, and one of the flakes was on Mac? I suggest you try looking at other possible culprits.

The symptom on mac_chromium_rel_ng is that the browser fails to start. This is what breaks ScreenshotSync.WithCanvas. ScreenshotSync.WithDivs then fails because the browser is wedged, and wasn't restarted after the first test timed out. This is similar to  Issue 571456 , which was on slower hardware, and also to  Issue 615178 , which seems to be happening on multiple bots.

Also: the Windows failures are caused by the Swarming pool being overloaded, which is being worked on in Issue 614526.

The detail in comment 6 and 7 is helpful.  Marking this as specific to Mac, as bug 614526 covers Windows.

As a sheriff it's not clear to me who should own this.  It seems like we've got some similar past/present bugs, but it's not quite clear what's going on or whose responsibility it is.  Ken, I'm pretty sure you're not the right owner here, but given that you have the clearest insight so far, can you triage to an appropriate person to take this on?

 Issue 614393  has been merged into this issue.

Yes, I can own this. I've had to email chromium-dev to ask if anyone's touched browser startup recently. I have a feeling that something was broken there recently and that these are all legitimate failures that affect the product.

The Screenshot timeout is showing up in several tests including screenshot_sync, pixel_test, and gpu_rasterization_tests.

Example logs attached.

Deleted: Mac_2010_10_Retina_Release_AMD_screenshot_sync.txt 54.9 KB

Mac_2010_10_Retina_Release_AMD_screenshot_sync.txt 54.9 KB View Download

Deleted: Mac_2010_10_Retina_Release_AMD_pixel_test.txt 183 KB

Mac_2010_10_Retina_Release_AMD_pixel_test.txt 183 KB View Download

There was a thread about browser crash upon startup on Mac a while ago due to Roger's CL, and we have to revert it. Then the crash disappear mysteriously with his CL so he just went ahead & relanded it.

His CL was: https://codereview.chromium.org/1746993002/

The diagnosis in #6 is that the browser failed to start.  Does this look like the case with the attached logs?  My assumption is that by the time we run the 'tab.Screenshot(5)' code, the browser should already be running.

Detected 7 new flakes for test/step "screenshot_sync_tests (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyLQsSBUZsYWtlIiJzY3JlZW5zaG90X3N5bmNfdGVzdHMgKHdpdGggcGF0Y2gpDA. This message was posted automatically by the chromium-try-flakes app.

FWIW, I remember seeing a startup crash on Mac due to some checks in profile. If I use something like --user-data-dir=/tmp/ajsdalkj the crash disappears.

Detected 17 new flakes for test/step "gpu_rasterization_tests (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyLwsSBUZsYWtlIiRncHVfcmFzdGVyaXphdGlvbl90ZXN0cyAod2l0aCBwYXRjaCkM. This message was posted automatically by the chromium-try-flakes app.

Detected 33 new flakes for test/step "gpu_rasterization_tests (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyLwsSBUZsYWtlIiRncHVfcmFzdGVyaXphdGlvbl90ZXN0cyAod2l0aCBwYXRjaCkM. This message was posted automatically by the chromium-try-flakes app.

Being investigated actively under  Issue 599776 .

Detected 8 new flakes for test/step "screenshot_sync_tests (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyLQsSBUZsYWtlIiJzY3JlZW5zaG90X3N5bmNfdGVzdHMgKHdpdGggcGF0Y2gpDA. This message was posted automatically by the chromium-try-flakes app.

Detected 5 new flakes for test/step "gpu_rasterization_tests (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyLwsSBUZsYWtlIiRncHVfcmFzdGVyaXphdGlvbl90ZXN0cyAod2l0aCBwYXRjaCkM. This message was posted automatically by the chromium-try-flakes app.

Detected 3 new flakes for test/step "gpu_rasterization_tests (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyLwsSBUZsYWtlIiRncHVfcmFzdGVyaXphdGlvbl90ZXN0cyAod2l0aCBwYXRjaCkM. This message was posted automatically by the chromium-try-flakes app.

Duplicating all screenshot-related timeouts on the AMD based Retina MacBook Pros into  Issue 599776 . The root cause is known and a fix / workaround is underway.