Issue metadata
Sign in to add a comment
|
Android Galaxy S5 Perf (1) red - possibly device problems? |
||||||||||||||||||||||
Issue descriptionLink to builds: https://build.chromium.org/p/chromium.perf/builders/Android%20Galaxy%20S5%20Perf%20%281%29?numbuilds=100 Bot turned red following an (apparently) no-op check in: https://chromium.googlesource.com/chromium/src/+/e39f7570eb72a6c3bdc6b236ccb1843eff8052b5%5E%21/#F0 Changing build number from 2675 to 2676. All subsequent provisioning steps fail with blacklisting errors: W 0.009s Main Device 3208e0600bb251f3 is blacklisted. W 0.009s Main Device 32081377735c51e5 is blacklisted. Subsequent tests fail with an unreachable error: DeviceUnreachableError: Unable to determine bus or device for device (error) and complaints about black listed devices: Device (error) blacklisted Device 320861234c117165 blacklisted Device 32082067745c515f blacklisted
,
Mar 14 2016
The unknown device is 320861234c117165.
The blacklisted devices are 32081377735c51e5 & 3208851faca351f3
All seem to react fine via adb but I went ahead and rebooted them anyway.
Cleaned up /b/build/site_config/.known_devices /b/build/slave/Android_Galaxy_S5_Perf__1_/build/src/out/{.last_devices,bad_devices.json)
I think that these android devices come and go based on external influences (e.g neighboring device get's wedged taking out other devices on the bus, host usb hang which gets reset on reboot, etc). So recording device failure during a build is valuable, flagging it as being bad going forward does more harm than good? Just a thought.
,
Mar 14 2016
I talked with Randy a few weeks back about revisiting device recovery / blacklisting for the perf bots. The model we use with the functional test bots doesn't make as much sense here.
,
Mar 14 2016
There was a roadblock stopping me from splitting them that I have since finished, so I should have time to look at this after Perf.
,
Mar 18 2016
It seems that this issue has been fixed for a couple of days now (last failure: https://build.chromium.org/p/chromium.perf/builders/Android%20Galaxy%20S5%20Perf%20%281%29/builds/1906 ). Should we marked it as fixed?
,
Mar 18 2016
Is there a deeper issue here, as alluded to in #3? Is there a separate bug for revisiting device recovery / blacklisting for the perf bots?
,
Apr 27 2016
,
Apr 27 2016
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by sullivan@chromium.org
, Mar 14 2016