Failure "shard #0 timed out, took too much time to complete" should be considered infra failures |
|||||
Issue descriptionChrome on iOS randomly fails with "shard #0 timed out, took too much time to complete". AFAICT from the log, the bot never started the app, thus I think this correspond to infra failures. Those failures still appear as red in sheriff-o-matic, instead of purple like other infra failures.
,
Feb 13 2018
,
Jul 6
Bumping this thread as I'm currently the sheriff and this happened to me: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac10.12%20Tests/14254 As far as I can tell this is just an infra issue.
,
Aug 2
This seems to not be Sheriff-o-Matic specific. Sending this issue to Infra>Platofrm to triage appropriately.
,
Aug 3
This looks like it might be something that needs to be changed in the chromium recipe so forwarding to CCI.
,
Aug 3
In general, these should not be infra failures (see e.g. https://bugs.chromium.org/p/chromium/issues/detail?id=813404). If your task is timing out, the task is typically at fault. e.g. #3: the layout test runner appears to be hanging. the bot is invoking the command appropriately. #0: that might be in the ios test runner, though 8 months on from the original issue, it's hard to be certain. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by sdefresne@chromium.org
, Dec 4 2017