New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 713416 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: ----



Sign in to add a comment

bot affinity 3, 6 is broken on chromium.perf/Android Nexus6 WebView Perf (1), affecting 18 tests

Project Member Reported by oysteine@chromium.org, Apr 19 2017

Issue description

bot affinity 3, 6 is broken on chromium.perf/Android Nexus6 WebView Perf (1), affecting 18 tests

Builders failed on: 
- Android Nexus6 WebView Perf (1): 
  https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus6%20WebView%20Perf%20%281%29



 

Comment 1 by pschm...@google.com, Apr 19 2017

Cc: benhenry@chromium.org vhang@chromium.org
Same thing here.   There are only 5 N6's attached and no spares.

Comment 2 by iannu...@google.com, Apr 19 2017

Cc: jbudorick@chromium.org martiniss@chromium.org
+ some maybe people?
Possible dupe of issue 712677?
The device was pulled off the host in t/26399922 to let it charge to 100%

Please see go/cit-device-ticket-queue for a list of automatically-filed device tickets.

Comment 5 by iannu...@google.com, Apr 20 2017

Labels: -Infra-Troopers
Owner: bpastene@chromium.org
Perf(1) seems to only have six devices and has been like this for some time, is it still supposed to have 7 online or is the documentation out of date at this point?
Bump on this, this bot is still purple.
Cc: bpastene@chromium.org
Owner: ----
This bot and its devices are a regular on the auto-filed device tickets: t/27405767
I'm not sure what else I can do here, so unassigning myself.

FYI, benchmark-health-alerts@ should be cc'ed on all the tickets, so if the steps taken there aren't sufficient, speed folks can work with the techs to ensure it's resolved.
Project Member

Comment 9 by sheriffbot@chromium.org, Jun 27 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)

Sign in to add a comment