New issue
Advanced search Search tips

Issue 867595 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Aug 2
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug

Blocking:
issue 847252



Sign in to add a comment

Nexus 5X bots down in chrome.tests.pinpoint pool

Project Member Reported by skobes@chromium.org, Jul 25

Issue description

I started two Pinpoint jobs that have been running for over 24 hours:

https://pinpoint-dot-chromeperf.appspot.com/job/1629d4b5a40000
https://pinpoint-dot-chromeperf.appspot.com/job/165aa2b3a40000

It looks like they finished building, but haven't started the "test" steps.
 
Components: Infra>Labs
Labels: Infra-Troopers
You're right, looks like the bots are down. All 7 devices are connected to the same host, so must be the host.

https://chrome-swarming.appspot.com/botlist?f=pool%3Achrome.tests.pinpoint&f=device_type%3ANexus%205X%20(bullhead)&f=device_os%3AMMB29Q
Cc: mar...@chromium.org
+maruel, should Swarming give NO_RESOURCE in this scenario?

Sample Swarming task:
https://chrome-swarming.appspot.com/task?id=3ee6acb761e2c010
Labels: -Pri-3 Pri-1
Yes, it's a false negative.
Cc: -mar...@chromium.org vhang@chromium.org dtu@chromium.org simonhatch@chromium.org
Labels: OS-Android
Owner: ----
Status: Available (was: Assigned)
Summary: Nexus 5X bots down in chrome.tests.pinpoint pool (was: Android Nexus5X Perf bot broken?)
Owner: vhang@chromium.org
Status: Assigned (was: Available)
Cc: friedman@chromium.org jo...@chromium.org
I believe these were caught by the auto device tickets:
https://gutsv3.corp.google.com/#ticket/34075155

BTW, this looks to be a bot on the -b4 vlan connected to the internal swarming server:
https://chrome-swarming.appspot.com/bot?id=build128-b4--device1

That's probably not good, right? (If that's harmless, then ignore me.)
Owner: jo...@chromium.org
Device #6 needed to be replaced.  rebooting and flashing of the phone didn't bring it back.  

Device #3 was rebooted and looks healthy. 

Passing this bug on to johnw to reinstall and move this bot from b4 to b7
Blocking: 847252
I can look into migrating this today.

Thanks.

Apologies, need to push this to tomorrow.

Thanks.

Project Member

Comment 12 by bugdroid1@chromium.org, Aug 1

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome-golo/chrome-golo/+/88dc7261e299034cef816966508681477a5756e6

commit 88dc7261e299034cef816966508681477a5756e6
Author: John Weathersby <johnw@google.com>
Date: Wed Aug 01 23:38:55 2018

Project Member

Comment 13 by bugdroid1@chromium.org, Aug 2

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infra/puppet/+/10a68cf828b7098ca1415107479d005142c13be0

commit 10a68cf828b7098ca1415107479d005142c13be0
Author: John Weathersby <johnw@google.com>
Date: Thu Aug 02 00:33:02 2018

Project Member

Comment 14 by bugdroid1@chromium.org, Aug 2

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/config/+/141b1ecdbbdaea1a080c7f998a4944248f7a853c

commit 141b1ecdbbdaea1a080c7f998a4944248f7a853c
Author: John Weathersby <johnw@google.com>
Date: Thu Aug 02 00:34:10 2018

build128-b4 -> build235-b7

Docker and pools have been migrated and the devices are in swarming.

Thanks.
Project Member

Comment 16 by bugdroid1@chromium.org, Aug 2

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome-golo/chrome-golo/+/425931aff85185d74e5fd573a676f98e6a90718f

commit 425931aff85185d74e5fd573a676f98e6a90718f
Author: John Weathersby <johnw@google.com>
Date: Thu Aug 02 01:28:12 2018

Status: Fixed (was: Assigned)

Sign in to add a comment