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

Issue 726049 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: May 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: ----
Type: ----

Blocked on:
issue 726713



Sign in to add a comment

power.typical_10_mobile flaky on internal.client.clank/health-plan-clankium-phone

Project Member Reported by wychen@chromium.org, May 24 2017

Issue description

bot affinity 1 is broken on internal.client.clank/health-plan-clankium-phone, affecting 1 tests

Builders failed on: 
- health-plan-clankium-phone: 
  http://master7.golo.chromium.org/i/internal.client.clank/builders/health-plan-clankium-phone

https://uberchromegw.corp.google.com/i/internal.client.clank/builders/health-plan-clankium-phone?numbuilds=200

power.typical_10_mobile looks flaky, and the failing sites were different each time. The failure rate became pretty high on 2017-05-23 and 24.

Observations from https://uberchromegw.corp.google.com/i/internal.client.clank/builders/health-plan-clankium-phone/builds/4609/steps/power.typical_10_mobile/logs/stdio :

For each test, error messages about Websocket not available would be there for a few seconds. It looks like this:
(INFO) 2017-05-24 08:09:16,435 devtools_client_backend._IsInspectorWebsocketAvailable:56  Websocket at port 41560 not yet available: [Errno 104] Connection reset by peer

In some cases, this error would last for a long time, and it would eventually time out after 60 seconds.
 

Comment 1 by fdoray@chromium.org, May 26 2017

Blockedon: 726713
Cc: perezju@chromium.org
Cc: -perezju@chromium.org
Owner: perezju@chromium.org
Status: Assigned (was: Available)
Assign to Juan for triaging/fixing since he's the owner of the benchmark.
Mergedinto: 726689
Status: Duplicate (was: Assigned)

Sign in to add a comment