Device offline on chromium.perf |
||||
Issue descriptionLink to buildbot status page: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus5X%20Perf%20%283%29/builds/1638 Device 00b2b9cb898332e1 BuildSlave build57-b1
,
Aug 24 2016
,
Aug 24 2016
John: Would it be easier if I made one bug for all of the currently blacklisted bots instead of a bug for each buildslave?
,
Aug 24 2016
+bpastene The best long term solution is to work with bpastene@ on getting an auto generated bug for Hwops to fix these phones. We currently have a bug that's generated every Monday. I understand that you want your phones back online sooner. We've talked with Hwops and they are willing to get a separate bug for high priority phones like the Perf phones. These bugs would be generated every 2 days and have a link to a spreadsheet that's dynamically updated with all the offline phones. For now, just create individual individual bugs until bpastene@ has implemented the new bug creating process.
,
Aug 24 2016
The devices appeared fine/detected at first. Decided to try and reboot it, and sure enough it went into a reboot-loop. Going to re-flash this one.
,
Aug 24 2016
/s/devices/device
,
Aug 24 2016
device is rebooting itself during the flashing process now, that's not good. going to replace it.
,
Aug 25 2016
Swapped 00b2b9cb898332e1 with 00b3512549c11418 Cleared known/bad json files. List of devices attached 00706ba5898326e4 device 00497c1989bb1ee6 device 00e2164b278fb20b device 00b2ea7a27b7aa05 device 00b88e248060cd28 device 00b675f2273fbc0b device 00b3512549c11418 device Thanks. |
||||
►
Sign in to add a comment |
||||
Comment 1 by aiolos@chromium.org
, Aug 24 2016