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

Issue 603196 link

Starred by 2 users
Status: WontFix
Owner:
charliea@chromium.org
Closed: Jun 2016
Cc:
█ nednguyen@chromium.org
█ alexandermont@chromium.org
dtu@chromium.org
sullivan@chromium.org
█ rnep...@chromium.org
█ aschulman@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

BattOr trace sometimes fails to dump

Project Member Reported by charliea@chromium.org, Apr 13 2016 
aschulman@ has encountered a bug a few times where, after we record a power trace (which we know happens because the light blinks red), the trace doesn't dump: it just goes back to a blinking yellow afterwards. This needs investigating.

Comment 1 by nedngu...@google.com, Apr 13 2016

Cc: dtu@chromium.org sullivan@chromium.org
Without a continuous integration testing for battor, it probably hard to try reproduce these problem.

I think we should prioritize adding battor integration test to catapult CQ.

Comment 2 by charliea@chromium.org, Jun 20 2016 

Has anyone encountered this recently? If not, I propose that we close this bug.

Comment 3 by charliea@chromium.org, Jun 28 2016

Status: WontFix (was: Assigned)
Unable to repro this: if we see it again, we'll reopen.
►

Sign in to add a comment