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

Issue 631874 link

Starred by 2 users

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android
Pri: 3
Type: Bug



Sign in to add a comment

[Telemetry] All BattOr benchmarks are failing on the new Android FYI bots

Project Member Reported by aschulman@chromium.org, Jul 27 2016

Issue description

The BattOr benchmarks on the new N5X Android bots are all failing. The reason is the Linux user account does not have permission to use the serial device. Assuming the OS running on the bot is Ubuntu, the Telemetry user needs to be added to the "dialout" group. Users in this group can access serial devices without superuser credentials.

This is the error that they are failing with:

Traceback (most recent call last):
  File "/b/rr/tmpGnHCB0/w/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 77, in _RunStoryAndProcessErrorIfNeeded
    test.WillRunStory(state.platform)
  File "/b/rr/tmpGnHCB0/w/src/third_party/catapult/telemetry/telemetry/web_perf/timeline_based_measurement.py", line 276, in WillRunStory
    platform.tracing_controller.StartTracing(self._tbm_options.config)
  File "/b/rr/tmpGnHCB0/w/src/third_party/catapult/telemetry/telemetry/core/tracing_controller.py", line 43, in StartTracing
    self._tracing_controller_backend.StartTracing(tracing_config, timeout)
  File "/b/rr/tmpGnHCB0/w/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py", line 91, in StartTracing
    if agent.StartAgentTracing(config, timeout):
  File "/b/rr/tmpGnHCB0/w/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/battor_tracing_agent.py", line 71, in StartAgentTracing
    self._battor.StartTracing()
  File "/b/rr/tmpGnHCB0/w/src/third_party/catapult/common/battor/battor/battor_wrapper.py", line 129, in StartTracing
    self._SendBattorCommand(self._START_TRACING_CMD)
  File "/b/rr/tmpGnHCB0/w/src/third_party/catapult/common/battor/battor/battor_wrapper.py", line 226, in _SendBattorCommand
    'Outputted: %s' % (cmd, status))
BattorError: BattOr did not complete command 'StartTracing' correctly.
Outputted: [0726/185610:ERROR:serial_io_handler.cc(168)] Failed to open serial port: FILE_ERROR_ACCESS_DENIED

 
Cc: dtu@chromium.org
Components: Infra>Labs
Owner: vhang@chromium.org
Assigning to vhang to help us triage. Vince, does adding the telemetry user to the dialout group make sense? We'd want to do this on build110-b1 to start, and eventually all the linux hosts for N5/N5X/S5 on chromium.perf and tryserver.chromium.perf.

Comment 3 by vhang@chromium.org, Jul 27 2016

Owner: pschmidt@chromium.org
Status: Assigned (was: Untriaged)

Comment 4 by pschm...@google.com, Jul 27 2016

Status: Started (was: Assigned)
Just added chrome-bot to the dialout group on build110-b1

chrome-bot@build110-b1:(Linux 14.04):~$ groups
chrome-bot dialout audio video
Thanks! Is this something that will be okay to require on more hosts in the future?
Yes, we can easily add this to any bots requiring it.

Comment 7 by dtu@chromium.org, Sep 13 2017

Status: Archived (was: Started)

Sign in to add a comment