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

Issue 918676 link

Starred by 2 users
Status: Assigned
Owner:
jbudorick@chromium.org
Cc:
█ kbr@chromium.org
estaab@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug

Blocked on:
issue 844230


Sign in to add a comment

CQ flakiness caused by WebGL test failures on Android [adb related]

Project Member Reported by erikc...@chromium.org, Jan 2 
Build: https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-marshmallow-arm64-rel/159026

Task: https://chromium-swarm.appspot.com/task?id=422464d89963a210&refresh=10&show_raw=1

Problem looks adb-related:
"""
[0101/224149.862234:ERROR:host_forwarder_main.cc(150)] ERROR: could not get adb port for device. You might need to add 'adb' to your PATH or provide the device serial id.
"""

This would likely have been mitigated by stgao's suggestion at issue 917122.

Comment 1 by kbr@chromium.org, Jan 2

Blockedon: 844230
Components: Internals>GPU>Testing Infra>Client>Chrome
Labels: OS-Android
Higher up in the log:
---
INFO:devil.android.forwarder:    [0101/224149.862194:ERROR:host_controllers_manager.cc(295)] forward tcp:55702 localabstract:chrome_device_forwarder failed. output: error: cannot bind to socket: Address already in use
INFO:devil.android.forwarder:    error: cannot bind to socket: Address already in use
---

Retrying only failed shards would be an improvement in this case.

Have seen similar problems in Issue 844230. Our team hopes to try the Skia team's Raspberry Pi based hosting solution for Android devices in order to mitigate these connectivity problems.

Comment 2 by gbeaty@chromium.org, Jan 2

Status: Available (was: Untriaged)

Comment 3 by jbudorick@chromium.org, Jan 7

Owner: jbudorick@chromium.org
Status: Assigned (was: Available)
►

Sign in to add a comment