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

Issue 834878 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
█ nednguyen@chromium.org
eyaich@chromium.org
sullivan@chromium.org
vhang@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

blink_perf.canvas failing on chromium.perf/Android Nexus6 WebView Perf

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Apr 19 2018 
Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of eyaich@google.com

blink_perf.canvas failing on chromium.perf/Android Nexus6 WebView Perf

Builders failed on: 
- Android Nexus6 WebView Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus6%20WebView%20Perf

Comment 1 by eyaich@chromium.org, Apr 19 2018

Cc: -eyaich@google.com vhang@chromium.org sullivan@chromium.org eyaich@chromium.org nednguyen@chromium.org
Components: Speed>Benchmarks>Waterfall
Looks like we have had some trouble reach these bots.

If you look at the logs from the failing builds: 

https://chromium-swarm.appspot.com/task?id=3cf591ca90b9e210&refresh=10&show_raw=1
I    0.004s _FindAdb  Downloading gs://chromium-telemetry/binary_dependencies/adb_8bd43e3930f6eec643d5dc64cab9e5bb4ddf4909 to /b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb
I    1.003s TimeoutThread-1-for-MainThread  condition '<lambda>' not met (1.0s)
I    3.494s TimeoutThread-1-for-MainThread  condition '<lambda>' not met (3.5s)
I    4.494s TimeoutThread-1-for-MainThread  condition '<lambda>' not met (4.5s)
I    5.494s TimeoutThread-1-for-MainThread  condition '<lambda>' not met (5.5s)
I    7.394s TimeoutThread-1-for-MainThread  condition '<lambda>' not met (7.4s)
I    8.394s TimeoutThread-1-for-MainThread  condition '<lambda>' not met (8.4s)
I    9.394s TimeoutThread-1-for-MainThread  condition '<lambda>' not met (9.4s)
I   11.158s TimeoutThread-1-for-MainThread  condition '<lambda>' not met (11.2s)
I   12.158s TimeoutThread-1-for-MainThread  condition '<lambda>' not met (12.2s)
I   13.159s TimeoutThread-1-for-MainThread  condition '<lambda>' not met (13.2s)
I   14.804s TimeoutThread-1-for-MainThread  condition '<lambda>' not met (14.8s)
I   15.804s TimeoutThread-1-for-MainThread  condition '<lambda>' not met (15.8s)
I   16.804s TimeoutThread-1-for-MainThread  condition '<lambda>' not met (16.8s)
I   18.847s TimeoutThread-1-for-MainThread  condition '<lambda>' not met (18.8s)
I   19.847s TimeoutThread-1-for-MainThread  condition '<lambda>' not met (19.8s)
I   20.848s TimeoutThread-1-for-MainThread  condition '<lambda>' not met (20.8s)
I   22.292s TimeoutThread-1-for-MainThread  condition '<lambda>' not met (22.3s)
I   23.292s TimeoutThread-1-for-MainThread  condition '<lambda>' not met (23.3s)
I   24.207s TimeoutThread-1-for-MainThread  condition '<lambda>' met (24.2s)
I   24.208s TimeoutThread-1-for-MainThread  [host]> /b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb devices
Traceback (most recent call last):
  File "../../third_party/catapult/devil/devil/android/tools/system_app.py", line 218, in <module>
    sys.exit(main(sys.argv[1:]))
  File "../../third_party/catapult/devil/devil/android/tools/system_app.py", line 208, in main
    devices = script_common.GetDevices(args.devices, args.blacklist_file)
  File "/b/swarming/w/ir/third_party/catapult/devil/devil/android/tools/script_common.py", line 47, in GetDevices
    raise device_errors.NoDevicesError()
devil.android.device_errors.NoDevicesError: No devices attached.


Bot seems to be quarantined quite a bit for cooldown.  

https://chromium-swarm.appspot.com/bot?id=build112-b1--device7&sort_stats=total%3Adesc

I wonder if this is another instance of Nexus6 devices that are failing.  Vince is this another Nexus6 device that has a swollen battery?
►

Sign in to add a comment