Add 6 Kevin PVT2 to pool:cts |
|||
Issue descriptionWe used to have 5 DVT2, but that was reduced to 1 during the transition to PVT2. We need 7 now, please help with add 6 more Kevins in lab to pool:cts Thank you!
,
Sep 29 2016
+don - who set this up last time who might be able to help and DVT2 request for reference: https://bugs.chromium.org/p/chromium/issues/detail?id=640715#c1
,
Sep 29 2016
Now the cts has 7 working DUTs I did the following steps: $balance_pool cts kevin -t 7 Balancing kevin cts pool: Total 1 DUTs, 1 working, 0 broken, 0 reserved. Target is 7 working DUTs; grow pool by 6 DUTs. kevin cts pool has 39 spares available. kevin cts pool will return 0 broken DUTs, leaving 0 still in the pool. Transferring 6 DUTs from suites to cts. Updating host: chromeos2-row6-rack5-host7. Removing labels ['pool:suites'] from host chromeos2-row6-rack5-host7 Adding labels ['pool:cts'] to host chromeos2-row6-rack5-host7 Updating host: chromeos2-row6-rack5-host8. Removing labels ['pool:suites'] from host chromeos2-row6-rack5-host8 Adding labels ['pool:cts'] to host chromeos2-row6-rack5-host8 Updating host: chromeos2-row6-rack5-host9. Removing labels ['pool:suites'] from host chromeos2-row6-rack5-host9 Adding labels ['pool:cts'] to host chromeos2-row6-rack5-host9 Updating host: chromeos2-row6-rack5-host10. Removing labels ['pool:suites'] from host chromeos2-row6-rack5-host10 Adding labels ['pool:cts'] to host chromeos2-row6-rack5-host10 Updating host: chromeos2-row6-rack5-host11. Removing labels ['pool:suites'] from host chromeos2-row6-rack5-host11 Adding labels ['pool:cts'] to host chromeos2-row6-rack5-host11 Updating host: chromeos2-row6-rack5-host12. Removing labels ['pool:suites'] from host chromeos2-row6-rack5-host12 Adding labels ['pool:cts'] to host chromeos2-row6-rack5-host12 $dut-status -b kevin -p cts hostname S last checked URL chromeos2-row6-rack6-host22 OK 2016-09-29 12:01:44 http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row6-rack6-host22/58414190-reset/ chromeos2-row6-rack5-host7 OK 2016-09-29 01:40:47 http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row6-rack5-host7/58411526-provision/ chromeos2-row6-rack5-host8 OK 2016-09-29 01:45:04 http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row6-rack5-host8/58411557-repair/ chromeos2-row6-rack5-host9 OK 2016-09-29 12:01:44 http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row6-rack5-host9/58414191-reset/ chromeos2-row6-rack5-host10 OK 2016-09-29 12:01:45 http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row6-rack5-host10/58414194-reset/ chromeos2-row6-rack5-host11 OK 2016-09-29 12:01:44 http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row6-rack5-host11/58414192-reset/ chromeos2-row6-rack5-host12 OK 2016-09-29 12:01:45 http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row6-rack5-host12/58414196-reset/ I'll leave this bug open, in case I did something wrong.
,
Oct 3 2016
|
|||
►
Sign in to add a comment |
|||
Comment 1 by shuqianz@chromium.org
, Sep 29 2016