New issue
Advanced search Search tips

Issue 721482 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Dec 2017
Cc:
seanmccullough@chromium.org
martiniss@chromium.org
zhangtiff@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

bot affinity failures are also getting reported as a test failures

Project Member Reported by charliea@chromium.org, May 11 2017 
See attached screenshots.

(Only device 0 was down on the bot.)
sheriff_o_matic.png
207 KB View Download
milo.png
131 KB View Download

Comment 1 by charliea@chromium.org, May 11 2017 

On further investigation, these test failures aren't instead getting reported as test failures: they're ALSO getting reported as test failures. There's also a *separate* failure for the device affinity failure affecting 10 tests, with the same start time. Any idea why these are getting double reported?
device_affinity.png
53.1 KB View Download

Comment 2 by charliea@chromium.org, May 11 2017

Summary: bot affinity failures are also getting reported as a test failures (was: bot affinity failure is instead getting reported as a test failure)

Comment 3 by zhangtiff@chromium.org, May 11 2017

Cc: seanmccullough@chromium.org
Labels: Milestone-Perf

Comment 4 by seanmccullough@chromium.org, Dec 14 2017

Status: Archived (was: Untriaged)
►

Sign in to add a comment