Since this is the first windows bot to go through this type of migration, going to test with build117-b1 first, followed by the rest if everything works out.

Thanks.

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

commit 80d5318326bd2ea59017a1a8519b8bdadbb063bf
Author: John Weathersby <johnw@google.com>
Date: Thu Apr 26 01:44:40 2018

Ok test subject build117-b1 is now build194-b7.

https://chrome-swarming.appspot.com/bot?id=build194-b7&sort_stats=total%3Adesc

If that looks good to you, we can move the rest tomorrow.

Hi John, we can't really test a single bot on private swarming server & the rest of public server in our waterfall. So I think we should just move forward with migrating the rest tomorrow

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

commit 26b47e335fe54033bead93d27fab3166d33f04cb
Author: John Weathersby <johnw@google.com>
Date: Thu Apr 26 18:00:31 2018

Discovered an issue with build194-b7. Looking into that before proceeding.

 Issue 837849  has been merged into this issue.

Discovered/fixed some token issues on build194-b7 (replacement for build117-b1). Going to verify stability tomorrow and then proceed with migrating the rest of these machines. 

Thanks

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

commit b54aafcd70b127f98b9005fe59bc9e92ec9819fb
Author: John Weathersby <johnw@google.com>
Date: Wed May 02 00:31:15 2018

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

commit c42fb3f7b12317f45f8245e6fc1e887763ed2f62
Author: John Weathersby <johnw@google.com>
Date: Wed May 02 02:04:45 2018

build{194..198}-b7 (respectively) are the migrated bots and are currently in unassigned pool.


Thanks.

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

commit 088213c85341c2bbcd5edfa680d5fc3e87e271fb
Author: nednguyen <nednguyen@google.com>
Date: Thu May 03 17:16:23 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/6ab87aefdc11c930dbfd1a711015a6763dfa918c

commit 6ab87aefdc11c930dbfd1a711015a6763dfa918c
Author: nednguyen <nednguyen@google.com>
Date: Thu May 03 17:18:41 2018

Migrate Win 10 High-DPI builder to use private swarming server

Bug:836446
Change-Id: I54a323577f69cd9cd9a1d1ba5d09357ce0b6b3d1
Reviewed-on: https://chromium-review.googlesource.com/1042269
Reviewed-by: Emily Hanley <eyaich@chromium.org>
Commit-Queue: Ned Nguyen <nednguyen@google.com>

[modify] https://crrev.com/6ab87aefdc11c930dbfd1a711015a6763dfa918c/scripts/slave/recipe_modules/chromium_tests/chromium_perf.py

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/47a7df2b529f9695cbc1902e689086fa42834177

commit 47a7df2b529f9695cbc1902e689086fa42834177
Author: nednguyen <nednguyen@google.com>
Date: Thu May 03 18:10:57 2018

Update swarming dimension of steps on 'Win 10 High-DPI Perf' builer

NOTRY=true  # tests are covered by CQ

Bug:  836446 
Change-Id: I65548078aa4c280fa0be6f29ed236e41b4194ee3
Reviewed-on: https://chromium-review.googlesource.com/1042275
Reviewed-by: Emily Hanley <eyaich@chromium.org>
Commit-Queue: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#555809}
[modify] https://crrev.com/47a7df2b529f9695cbc1902e689086fa42834177/testing/buildbot/chromium.perf.json
[modify] https://crrev.com/47a7df2b529f9695cbc1902e689086fa42834177/tools/perf/core/benchmark_sharding_map.json
[modify] https://crrev.com/47a7df2b529f9695cbc1902e689086fa42834177/tools/perf/core/perf_data_generator.py

Hmhh, the build is failing at swarming task trigger step: 
https://ci.chromium.org/buildbot/chromium.perf/Win%2010%20High-DPI%20Perf/1887

8384 2018-05-04 10:33:07.832 E: Request to https://chrome-swarming.appspot.com/api/swarming/v1/tasks/new failed with HTTP status code 403: Can't submit tasks to pool "chrome.test.perf" not defined in pools.cfg
8384 2018-05-04 10:33:07.832 E: Use auth.py to login if haven't done so already:
    python auth.py login --service=https://chrome-swarming.appspot.com
Sending the report ... done.
Report URL: https://chrome-swarming.appspot.com/restricted/ereporter2/errors/5893034575134720
Failed to trigger task blink_perf.bindings on Intel GPU on Windows/Windows-10/40ff854eb5/Win 10 High-DPI Perf/1887



Does any one know what is configured wrong? :-(

https://codesearch.chromium.org/chromium/src/tools/perf/core/perf_data_generator.py?rcl=856d84ec75756bfec8d93f8f9b4ef971c93d840e&l=254 should be chrome.tests.perf

Arggg, silly mistake. Thanks John!

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/00eb06c3827b91f6b9221fa566a891b01fb7e92b

commit 00eb06c3827b91f6b9221fa566a891b01fb7e92b
Author: Ned Nguyen <nednguyen@google.com>
Date: Fri May 04 14:04:56 2018

Fix pool dimension of 'Win 10 High-DPI Perf'

NOTRY=true
TBR=eyaich@chromium.org

Bug:  836446 
Change-Id: Id47c16c1231fac76cf7f07bf8aa4f9bd7b5a1067
Reviewed-on: https://chromium-review.googlesource.com/1044307
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#556041}
[modify] https://crrev.com/00eb06c3827b91f6b9221fa566a891b01fb7e92b/testing/buildbot/chromium.perf.json
[modify] https://crrev.com/00eb06c3827b91f6b9221fa566a891b01fb7e92b/tools/perf/core/perf_data_generator.py

This is working now: https://ci.chromium.org/buildbot/chromium.perf/Win%2010%20High-DPI%20Perf/1908

 Issue 840778  has been merged into this issue.

Reopening this issue. build180-b4 is still down and causing purpleness on win-high-dpi, so there remains _something_ to fix

Woops, reopened the wrong issue. This one should remain closed because the bot is in fact migrated. Meant to reopen bug 840894

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/1edf611677e36dce74f279a58b0387fb991a5169

commit 1edf611677e36dce74f279a58b0387fb991a5169
Author: Ned Nguyen <nednguyen@google.com>
Date: Thu May 10 19:51:35 2018

Update bot id of device build180-b4 to build198-b7

TBR=eyaich@chromium.org
NOTRY=true  # test covered by PRESUBMIT

Bug: 840894, 836446 
Change-Id: Ie3c81037287b67781f39b058eb5303f17ed896d9
Reviewed-on: https://chromium-review.googlesource.com/1054412
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#557633}
[modify] https://crrev.com/1edf611677e36dce74f279a58b0387fb991a5169/testing/buildbot/chromium.perf.json
[modify] https://crrev.com/1edf611677e36dce74f279a58b0387fb991a5169/tools/perf/core/benchmark_sharding_map.json
[modify] https://crrev.com/1edf611677e36dce74f279a58b0387fb991a5169/tools/perf/core/perf_data_generator.py