New issue
Advanced search Search tips

Issue 783093 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
jbudorick@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

test steps with timed out tasks are marked failure

Project Member Reported by no...@chromium.org, Nov 9 2017 
https://ci.chromium.org/buildbot/chromium.mac/Mac10.9%20Tests%20%28dbg%29/46977
has step telemetry_unittests with a timed out swarming task.

the step is marked as failure, like tests failed, but actually we cannot judge tests by this result. Such step should be marked as infra failure

this will improve monitoring because we track infra failure rates

Comment 1 by jbudorick@chromium.org, Jan 4 2018

Labels: -Pri-2 Pri-3
Status: Available (was: Untriaged)
#0: why do we think that timed-out tests are infra failures? If a developer adds something to src that drastically increases the execution time of one or more tests, is that an infra failure?

Comment 2 by jbudorick@chromium.org, Jan 4 2018

Cc: jbudorick@chromium.org

Comment 3 by no...@chromium.org, Jan 4 2018

Status: WontFix (was: Available)
correct, a slow test is not an infra failure. OK, let's conservatively close this.
►

Sign in to add a comment