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

Issue 762140 link

Starred by 1 user
Status: Assigned
Owner:
█ jintao@chromium.org
Last visit > 30 days ago
Cc:
█ renyi@chromium.org
█ mtyin@chromium.org
█ sduvvuri@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

jetstream_BluetoothBeaconing failure in CQ

Reported by jrbarnette@chromium.org, Sep 5 2017 
This gale-paladin run failed:
    https://luci-milo.appspot.com/buildbot/chromeos/gale-paladin/3723

Logs for the failure can be found here:
    http://cautotest/tko/retrieve_logs.cgi?job=/results/139203913-chromeos-test/

The gale-paladin run had no relevant CLs:  No CL could have
caused the failure, so there's something wrong with the test,
or else there's a bug in jetstream ToT.

Leaving at P3 for now; this failure has only happened once, so it's not
yet urgent to find a fix.

Comment 1 by jrbarnette@chromium.org, Sep 5 2017

Owner: jintao@chromium.org
Status: Assigned (was: Untriaged)
Assigning to a sheriff to triage and find a proper owner.

Comment 2 by jintao@chromium.org, Sep 5 2017

Cc: renyi@chromium.org sduvvuri@chromium.org mtyin@chromium.org
Mingtian and Yi, could you please check if this auto test failure could be caused by recent ble changes?

Comment 3 by jintao@chromium.org, Sep 6 2017 

So far this failure happened only once, we have created a ticket at internal buganizer https://b.corp.google.com/issues/65406740 for tracking purpose.  Will revisit this issue when it happens again
►

Sign in to add a comment