New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 873460 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

Device 'build201-b7--device2' unreachable, causing many failures on chromium.perf/Android Nexus5 Perf

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Aug 11

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of nednguyen@chromium.org

...... too many results, data snipped.... and 40 other(s) in performance_test_suite failing on chromium.perf/Android Nexus5 Perf

Builders failed on: 
- Android Nexus5 Perf: 
  https://ci.chromium.org/buildbot/chromium.perf/Android%20Nexus5%20Perf

This is because of "DeviceUnreachableError: 06a9b365003beeb1"

https://chrome-swarming.appspot.com/task?id=3f4145c38d3a1610&refresh=10&show_raw=1

Can lab take a look at build201-b7--device2?


 
Components: Infra>Labs
Summary: Device 'build201-b7--device2' unreachable, causing many failures on chromium.perf/Android Nexus5 Perf (was: ...... too many results, data snipped.... and 40 other(s) in performance_test_suite failing on chromium.perf/Android Nexus5 Perf)
Owner: vhang@chromium.org
Status: Assigned (was: Available)
build201-b7--device2 seems fine to me.  It responds to touch.  Do you want me to reboot?
Cc: vhang@chromium.org bpastene@chromium.org jbudorick@chromium.org
Components: -Infra>Labs Speed>Benchmarks>Waterfall
Labels: -Pri-1 Pri-2
Owner: ----
Status: Available (was: Assigned)
Thanks Vince, I guess this is just same flaky issue with adb 

Sign in to add a comment