New issue
Advanced search Search tips

Issue 703711 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Mar 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"preprocess_for_goma.upload_goma_start_failed_logs" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Mar 21 2017

Issue description

"preprocess_for_goma.upload_goma_start_failed_logs" 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 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyPAsSBUZsYWtlIjFwcmVwcm9jZXNzX2Zvcl9nb21hLnVwbG9hZF9nb21hX3N0YXJ0X2ZhaWxlZF9sb2dzDA.



This flaky test/step was previously tracked in issue 697681.
 
Owner: yyanagisawa@chromium.org
Status: Assigned (was: Untriaged)
Yanagisawa-san, is this  Issue 694885 ?
Status: WontFix (was: Assigned)
I do not think so.  I think it caused by temporary network flakiness, and goma just gives up after retrying 1 minute.

If this situation continues for the same builder for long time, that might be a P1 issue but if you only see it few times on different builder, I guess it something possibly occur.  As far as I checked the flakiness dashboard, it seems to be the latter.  Let me mark this won't fix.

Sign in to add a comment