New issue
Advanced search Search tips

Issue 850676 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 848034



Sign in to add a comment

Clean up pinpoint bots that are no longer needed

Project Member Reported by nednguyen@chromium.org, Jun 7 2018

Issue description

I notice we have many obsolete bots in the pinpoint pool (chromium-swarm) that no longer match the perf waterfall. We should clean them up before asking lab team to do the migration.

The current bots in pinpoint are:

Android:
  bot_id: "build{42..45}-b4" # Android Nexus 5X
  bot_id: "build99-b4"  # Android Nexus 5
  bot_id: "build106-b4" # Android Nexus 5
  bot_id: "build114-b4" # Android Nexus 5
  bot_id: "build{107..109}-b4" # Android Nexus 6
  bot_id: "build{101..103}-b4" # Android Nexus 7
  bot_id: "build98-b4" # Android One
  bot_id: "build{110..111}-b4" # Android One
  bot_id: "build225-b4" # Android Webview Arm64 AOSP
  bot_id: "build185-b4" # Android Webview Nexus 6

Desktop:
  bot_id: "build{1..6}-a4" # Linux
  bot_id: "build{305..314}-a9" # Linux
  bot_id: "build{192..196}-b4" # Mac Air 10.11
  bot_id: "build{197..201}-b4" # Mac Pro 10.11
  bot_id: "build{224..226}-m4" # Mac 10.12
  bot_id: "build{230..245}-a9"  # Mac 10.12 Low end

  bot_id: "build{240..242}-m4" # Win
  bot_id: "build{172..174}-m4" # Win 8
  bot_id: "build{170..171}-m4" # Win x64
  bot_id: "build18-m4" # Win x64
  bot_id: "build{184..188}-a9" # Win x64 10
  bot_id: "build{102..104}-m4" # Win x64 ATI
  bot_id: "build{181..184}-b4" # Win x64 High DPI
  bot_id: "build{227..229}-m4" # Win x64 Intel
  bot_id: "build{96..98}-m4" # Win x64 Nvidia
  bot_id: "build157-m4" # Win x64 Nvidia



The builders on perf waterfall today are:
Android Nexus 5
Android Nexus 5X Perf
Android One Perf
Android Nexus 5X Webview Perf
Android Nexus 6 Webview Perf
Win 10 HighDPI Perf
Win 10 Perf
Win 7 Perf
Win 7 Nvidia GPU Perf
mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf
linux-perf


Assign to Dave to triage
 

Comment 1 by dtu@chromium.org, Jun 11 2018

Status: Assigned (was: Untriaged)
Was chromium-rel-win7-x64-dual renamed to chromium-rel-win7-dual?
What are the expected CPU and GPU for Win 7 Perf?
Emily: can you answer Dave's question in #1?

Comment 4 by dtu@chromium.org, Jun 12 2018

Hmm, I think these two configs have been swapped since the recipe bisect days.
The bots labeled "Win x64" more closely match the above bot.
https://chrome-internal.googlesource.com/infradata/config/+/master/configs/chromium-swarm/bots.cfg#867
https://chromium-swarm.appspot.com/bot?id=build18-m4

Comment 5 by dtu@chromium.org, Jun 12 2018

CL is up to remove them from Swarming.
https://chrome-internal-review.googlesource.com/c/infradata/config/+/639310

These are the configs we will be removing.

android-nexus6
build107-b4 build108-b4 build109-b4

android-nexus7v2
build101-b4 build102-b4 build103-b4

chromium-rel-mac11-air
build192-b4 build193-b4 build194-b4 build195-b4 build196-b4

chromium-rel-mac11-pro
build197-b4 build199-b4 build200-b4 build201-b4

chromium-rel-mac12
build224-m4 build225-m4 build226-m4

chromium-rel-win7-gpu-ati
build102-m4 build103-m4 build104-m4

chromium-rel-win7-gpu-intel
build227-m4 build228-m4 build229-m4

chromium-rel-win7-x64-dual
build240-m4 build241-m4 build242-m4

chromium-rel-win8-dual
build172-m4 build173-m4 build174-m4

Project Member

Comment 6 by bugdroid1@chromium.org, Jun 12 2018

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

commit 43c2db26fe85f4a64afc47a85c99174a160b3359
Author: David Tu <dtu@google.com>
Date: Tue Jun 12 20:35:49 2018

Comment 7 by dtu@chromium.org, Jun 12 2018

Cc: dtu@chromium.org
Components: Infra>Labs
Owner: vhang@chromium.org
Assigning to labs for the rest of the cleanup.

Comment 8 by vhang@chromium.org, Jun 15 2018

Are you saying that you no longer need the bots in comment #5?

Comment 9 by dtu@chromium.org, Jun 18 2018

Yes, that's right.

Comment 10 by jo...@google.com, Jun 20 2018

Owner: jo...@chromium.org
Project Member

Comment 11 by bugdroid1@chromium.org, Jun 20 2018

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

commit bbf881fc193b7295c52247fc510e02d230c1da48
Author: John Weathersby <johnw@google.com>
Date: Wed Jun 20 19:00:12 2018

Comment 12 by jo...@chromium.org, Jun 20 2018

Cc: vhang@chromium.org
For the labs: 

Un-racked 6x legacy R2{1,2}0 platforms -> scrap-heap
Removed mobile devices and put them back into inventory or recycle (bulging batteries)
Left the mac-hardware racked and set as free/available status

Will work on golo shortly.

Project Member

Comment 13 by bugdroid1@chromium.org, Jun 20 2018

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

commit 57bd1c2bda26814e5ef231143e36e18530aa7675
Author: John Weathersby <johnw@google.com>
Date: Wed Jun 20 20:56:43 2018

Project Member

Comment 14 by bugdroid1@chromium.org, Jun 20 2018

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

commit 6ec921a98c6daca5a5d4e3c67ccc7f02f6f73d48
Author: John Weathersby <johnw@google.com>
Date: Wed Jun 20 23:19:09 2018

Comment 15 by jo...@chromium.org, Jun 21 2018

30 bare-metal lab/golo hosts in c#5 have been reclaimed.

Comment 16 by jo...@chromium.org, Jun 21 2018

Status: Fixed (was: Assigned)

Sign in to add a comment