Win Power Perf (DELL) (build85-b1) needs BattOr USB cable unplugged / replugged in |
||||
Issue descriptionLink to buildbot status page: https://uberchromegw.corp.google.com/i/chromium.perf.fyi/builders/Win%20Power%20Perf%20(DELL) It looks like the BattOr perf tests have been failing since Friday due with a failure message of "RECEIVE_ERROR" (https://uberchromegw.corp.google.com/i/chromium.perf.fyi/builders/Win%20Power%20Perf%20%28DELL%29/builds/65/steps/BattOr.BattOrCases/logs/stdio). Generally, this is a pretty good indication that there's data stuck on the wire, and the USB cable needs to be replugged into the machine. aschulman@ has a fix pending that will fix this "data stuck on the wire" issue (https://codereview.chromium.org/1991403002/). As a temporary fix for now, could Infra-labs unplug and replug in the BattOr cable to the machine?
,
Jun 13 2016
Thanks Peter! I'll assign this back to myself and mark it as fixed once it's passing again.
,
Jun 13 2016
,
Jun 13 2016
Daily ping from sheriff. Charlie, should this be monitored by perf bot health sheriff?
,
Jun 13 2016
The issue here was actually not bytes stuck on the wire, but a longstanding bug in the BattOr firmware where the capacity of SD cards over 8gb were incorrectly assumed to be only 100mb. This lead the firmware to think that the SD card was full, so it was not allowing the BattOr to run. More information can be found here: https://github.com/aschulm/battor/issues/38. I fixed this bug in the firmware and updated the firmware on the FYI bot BattOrs. Things should be fairly stable now (I'm still waiting for another commit to execute), but they will be even stable once the "data on the wire" issue lands (https://codereview.chromium.org/1991403002/) |
||||
►
Sign in to add a comment |
||||
Comment 1 by pschm...@google.com
, Jun 13 2016Status: Assigned (was: Untriaged)