"isolate" is flaky |
||
Issue description"isolate" 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 4 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyEgsSBUZsYWtlIgdpc29sYXRlDA. This flaky test/step was previously tracked in issue 607928 .
,
Oct 14 2016
Example debug output: 09:40:28.416720 Task failed, retrying after a sleep of 100ms: http request failed: Internal Server Error (HTTP 500) 09:41:01.064985 Task failed, retrying after a sleep of 100ms: http request failed: Internal Server Error (HTTP 500) 09:41:32.250103 Task failed, retrying after a sleep of 100ms: http request failed: Service Unavailable (HTTP 503) 09:42:03.437221 Task failed, retrying after a sleep of 100ms: http request failed: Internal Server Error (HTTP 500) 09:42:25.574435 Task failed, retrying after a sleep of 100ms: http request failed: Internal Server Error (HTTP 500) 09:43:07.118589 Task failed, retrying after a sleep of 100ms: http request failed: Service Unavailable (HTTP 503) 09:43:38.328709 Task failed, retrying after a sleep of 100ms: http request failed: Service Unavailable (HTTP 503) 09:44:09.532830 Task failed, retrying after a sleep of 100ms: http request failed: Service Unavailable (HTTP 503) Robert (Trooper)_ looked into this earlier and it seemed like spurious failures on the backend. I haven't seen any additional failures since then. Resolving 'not repro', will re-activate if we start seeing this again. |
||
►
Sign in to add a comment |
||
Comment 1 by joedow@chromium.org
, Oct 14 2016