New issue
Advanced search Search tips

Issue 728935 link

Starred by 1 user
Status: Fixed
Owner:
estaab@chromium.org
Closed: Jun 2017
Cc:
yoichio@chromium.org
chrome-trooper-bugs@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"webkit_lint (with patch)" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Jun 2 2017 
"webkit_lint (with patch)" 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 9 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyIwsSBUZsYWtlIhh3ZWJraXRfbGludCAod2l0aCBwYXRjaCkM.

The chromium-try-flakes app is able to file bugs for individual tests when the test launcher is uploading results to the Test Results Server. If recent flakes above are caused by failing tests and you would like to have them filed as invidual bugs, please read more at https://goo.gl/QJKXV4.

This flaky test/step was previously tracked in  issue 624170 .

Comment 1 by yoichio@chromium.org, Jun 2 2017

Labels: -Sheriff-Chromium Infra-Troopers
Many patch are not landed and we should not count flaky by not landed patches.
Also https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_ng 
 is useless because it mixes ToT build and try build.

Comment 2 by estaab@chromium.org, Jun 2 2017

Cc: yoichio@chromium.org
Owner: estaab@chromium.org
Status: Fixed (was: Untriaged)
Yoichi, the flakiness pipeline compares results of identical patchsets and when they produce different results (across retries) at a high rate then these bugs are filed. These are not useless and need to be examined by sheriffs. Please don't dismiss them next time.

I investigate the issue and it was caused by an infrastructure change that was reverted (issue 670990), so no further action is needed.
►

Sign in to add a comment