CaptureScreenshotTest.CaptureScreenshotArea in content_browsertests failing on chromium.win/Win7 Tests (dbg)(1) |
|||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of fhorschig@google.com CaptureScreenshotTest.CaptureScreenshotArea in content_browsertests failing on chromium.win/Win7 Tests (dbg)(1) Builders failed on: - Win7 Tests (dbg)(1): https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29 There are two consecutive failures but no obvious cuplrit: https://uberchromegw.corp.google.com/i/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29/builds/65725 https://uberchromegw.corp.google.com/i/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29/builds/65726 dgozman@, Can you help investigating and triaging?
,
Jan 11 2018
Apparently, this CL caused flakes on Linux as well (3 months ago) so I will do the same as back then and disable it for this platform: https://crrev.com/c/860406
,
Jan 11 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/bf2382b7822ce0b17165899891875e752674c033 commit bf2382b7822ce0b17165899891875e752674c033 Author: Friedrich Horschig <fhorschig@chromium.org> Date: Thu Jan 11 15:03:07 2018 Disable flaky CaptureScreenshotArea on Windows This test is had some recent flakes without easily identifiable cause. It is already disabled for Android (with reason in a comment) and for Linux (3 months ago; for flakiness: https://crrev.com/c/690994). TBR=dgozman@chromium.org Bug: 801173 Change-Id: I06682aee46c8652ba40ce4cddbf921857704780b Reviewed-on: https://chromium-review.googlesource.com/860406 Reviewed-by: Friedrich Horschig <fhorschig@chromium.org> Commit-Queue: Friedrich Horschig <fhorschig@chromium.org> Cr-Commit-Position: refs/heads/master@{#528623} [modify] https://crrev.com/bf2382b7822ce0b17165899891875e752674c033/content/browser/devtools/protocol/devtools_protocol_browsertest.cc
,
Dec 4
Will get addressed during the test fixit. |
|||
►
Sign in to add a comment |
|||
Comment 1 by fhorschig@chromium.org
, Jan 11 2018Labels: OS-Windows Type-Bug