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

Issue 657660 link

Starred by 1 user
Status: Fixed
Owner:
█ rnep...@chromium.org
Last visit > 30 days ago
Closed: Oct 2016
Cc:
sullivan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Mac Retina Perf (2) failing battor step

Project Member Reported by martiniss@chromium.org, Oct 19 2016 
No tools/build changes landed between the two builds that started failing.

https://uberchromegw.corp.google.com/i/chromium.perf/builders/Mac%20Retina%20Perf%20%282%29/builds/4473 (last passing build)
https://uberchromegw.corp.google.com/i/chromium.perf/builders/Mac%20Retina%20Perf%20%282%29/builds/4474 (first failing build)

Looks like something broke in the hardware?

https://uberchromegw.corp.google.com/i/chromium.perf/builders/Mac%20Retina%20Perf%20%282%29/builds/4479/steps/battor.trivial_pages/logs/stdio has the following:
Traceback (most recent call last):
  File "/b/c/b/Mac_Retina_Perf__2_/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 78, in _RunStoryAndProcessErrorIfNeeded
    test.WillRunStory(state.platform)
  File "/b/c/b/Mac_Retina_Perf__2_/src/third_party/catapult/telemetry/telemetry/web_perf/timeline_based_measurement.py", line 282, in WillRunStory
    platform.tracing_controller.StartTracing(self._tbm_options.config)
  File "/b/c/b/Mac_Retina_Perf__2_/src/third_party/catapult/telemetry/telemetry/core/tracing_controller.py", line 43, in StartTracing
    self._tracing_controller_backend.StartTracing(tracing_config, timeout)
  File "/b/c/b/Mac_Retina_Perf__2_/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py", line 91, in StartTracing
    if agent.StartAgentTracing(config, timeout):
  File "/b/c/b/Mac_Retina_Perf__2_/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/battor_tracing_agent.py", line 73, in StartAgentTracing
    self._battor.StartTracing()
  File "/b/c/b/Mac_Retina_Perf__2_/src/third_party/catapult/common/battor/battor/battor_wrapper.py", line 155, in StartTracing
    self._SendBattOrCommand(self._START_TRACING_CMD)
  File "/b/c/b/Mac_Retina_Perf__2_/src/third_party/catapult/common/battor/battor/battor_wrapper.py", line 270, in _SendBattOrCommand
    'Outputted: %s' % (cmd, status))
BattOrError: BattOr did not complete command 'StartTracing' correctly.
Outputted: [1019/104731:FATAL:battor_agent_bin.cc(88)] Fatal error when communicating with the BattOr: TIMEOUT

Comment 1 by sullivan@chromium.org, Oct 20 2016

Owner: charliea@chromium.org
Charlie, can you triage?

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

Owner: rnep...@chromium.org
Reassigning to rnephew@. Quoting our offline conversation:

"It looks like the BattOr is resetting when we tell it to start sampling, which is consistent with what happens when we have a bad SD card in the BattOr. I went ahead and filed a bug about this here: Randy, do you think you could check the firmware version of the BattOr that's misbehaving? I'd definitely be interested to see whether we forgot to flash that one. If we did indeed flash it, we probably just need to replace the SD card.

I went ahead and ordered 10 more Sandisk 32GB SD cards to your desk in MTV, Randy. It seems like, no matter what, it's a good idea for us to keep a bunch of extra SD cards on hand. Could you keep an eye out for them? They're likely to arrive on Monday."

Comment 3 by rnep...@chromium.org, Oct 21 2016

Status: Fixed (was: Assigned)
►

Sign in to add a comment