Issue metadata
Sign in to add a comment
|
"org.chromium.chrome.browser.printing.PrintingControllerTest#testNormalPrintingFlow" is flaky |
||||||||||||||||||||||||
Issue description"org.chromium.chrome.browser.printing.PrintingControllerTest#testNormalPrintingFlow" is flaky. This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label. We have detected 6 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyXQsSBUZsYWtlIlJvcmcuY2hyb21pdW0uY2hyb21lLmJyb3dzZXIucHJpbnRpbmcuUHJpbnRpbmdDb250cm9sbGVyVGVzdCN0ZXN0Tm9ybWFsUHJpbnRpbmdGbG93DA. Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs
,
Jun 13 2017
Disabling here https://chromium-review.googlesource.com/534656
,
Jun 13 2017
,
Jun 13 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/12a2797868d3c6eb531bf9321cc96b289530ec28 commit 12a2797868d3c6eb531bf9321cc96b289530ec28 Author: Dale Curtis <dalecurtis@chromium.org> Date: Tue Jun 13 23:39:18 2017 Disable flaky testNormalPrintingFlow test. BUG= 733002 TBR=tedchoc Change-Id: I049c8ce839eb05316f108835a17f0dc6d1c78bd6 Reviewed-on: https://chromium-review.googlesource.com/534656 Reviewed-by: Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#479205} [modify] https://crrev.com/12a2797868d3c6eb531bf9321cc96b289530ec28/chrome/android/javatests/src/org/chromium/chrome/browser/printing/PrintingControllerTest.java
,
Jun 13 2017
,
Jun 13 2017
thestig@, my CL got reverted due to this flaky test last night, see crbug/732698, does that mean even without my change, this is still happening?
,
Jun 14 2017
,
Jun 14 2017
thestig@, dalecurtis@, nvm, it should be my CL's issue, from https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyXQsSBUZsYWtlIlJvcmcuY2hyb21pdW0uY2hyb21lLmJyb3dzZXIucHJpbnRpbmcuUHJpbnRpbmdDb250cm9sbGVyVGVzdCN0ZXN0Tm9ybWFsUHJpbnRpbmdGbG93DA shows all flaky instances are many hours ago, don't know why this issue created just less than two hours ago.
,
Jun 14 2017
#8: chromium-try-flakes only recognizes a flake when it sees a failing run and a passing run on the same patchset. It may be that it took some of the authors a little while to re-CQ their patches after your CL was reverted. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dalecur...@chromium.org
, Jun 13 2017Labels: OS-Android