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

Issue 695927 link

Starred by 3 users
Status: Fixed
Owner:
█ rnep...@chromium.org
Last visit > 30 days ago
Closed: Mar 2017
Cc:
charliea@chromium.org
█ aschulman@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

BattOr Agent cannot connect to BattOrs on new Nexus 5x bots

Project Member Reported by rnep...@chromium.org, Feb 24 2017 
I ssh'd into the new bot with BattOrs to attempt to run the battors to confirm they are working properly. I get errors when trying to communicate with them.

./battor_agent --battor-path=/dev/ttyUSB[0-6]
GetFirmwareGitHash
[0224/093937.078497:ERROR:serial_io_handler.cc(152)] Failed to open serial port: FILE_ERROR_ACCESS_DENIED
[0224/093937.078549:FATAL:battor_agent_bin.cc(89)] Fatal error when communicating with the BattOr: CONNECTION FAILED
#0 0x00000043ffce base::debug::StackTrace::StackTrace()
#1 0x00000042361b logging::LogMessage::~LogMessage()
#2 0x00000040a27c battor::(anonymous namespace)::HandleError()
#3 0x00000040a0b9 battor::BattOrAgentBin::OnGetFirmwareGitHashComplete()
#4 0x00000044051e base::debug::TaskAnnotator::RunTask()
#5 0x0000004250ad base::MessageLoop::RunTask()
#6 0x0000004257f5 base::MessageLoop::DoWork()
#7 0x0000004277e9 base::MessagePumpLibevent::Run()
#8 0x000000424dd7 base::MessageLoop::RunHandler()
#9 0x00000042818e base::RunLoop::Run()
#10 0x000000434d87 base::Thread::ThreadMain()
#11 0x000000431713 base::(anonymous namespace)::ThreadFunc()
#12 0x7f1a4d92e184 start_thread
#13 0x7f1a4c93d37d clone

Comment 1 by aschulman@chromium.org, Feb 24 2017 

Looks like someone needs to add the bot user to the 'dialout' group so the bot user can access the tty interfaces without root permissions.

Comment 2 by rnep...@chromium.org, Feb 24 2017

Cc: aschulman@chromium.org
I tried to run it on a bot and it still doesn't seem to be working.


chrome-bot@build75-b1:(Linux 14.04):/b/c/b/Android_Nexus5X_Perf__3_/src/third_party/catapult/common/battor/bin/linux2/x86_64$ sudo usermod -a -G dialout chrome-bot
chrome-bot@build75-b1:(Linux 14.04):/b/c/b/Android_Nexus5X_Perf__3_/src/third_party/catapult/common/battor/bin/linux2/x86_64$ ./battor_agent --battor-path=/dev/ttyUSB0
StartTracing
[0224/154159.551984:ERROR:serial_io_handler.cc(152)] Failed to open serial port: FILE_ERROR_ACCESS_DENIED
[0224/154159.552035:FATAL:battor_agent_bin.cc(89)] Fatal error when communicating with the BattOr: CONNECTION FAILED
#0 0x00000043ffce base::debug::StackTrace::StackTrace()
#1 0x00000042361b logging::LogMessage::~LogMessage()
#2 0x00000040a27c battor::(anonymous namespace)::HandleError()
#3 0x000000409d39 battor::BattOrAgentBin::OnStartTracingComplete()
#4 0x00000044051e base::debug::TaskAnnotator::RunTask()
#5 0x0000004250ad base::MessageLoop::RunTask()
#6 0x0000004257f5 base::MessageLoop::DoWork()
#7 0x0000004277e9 base::MessagePumpLibevent::Run()
#8 0x000000424dd7 base::MessageLoop::RunHandler()
#9 0x00000042818e base::RunLoop::Run()
#10 0x000000434d87 base::Thread::ThreadMain()
#11 0x000000431713 base::(anonymous namespace)::ThreadFunc()
#12 0x7fdc752ac184 start_thread
#13 0x7fdc742bb37d clone

Aborted

Comment 3 by aschulman@chromium.org, Feb 24 2017 

You may want to run 'groups' to see if the groups took hold immediately. I think you need to log out and back in.

Comment 4 by rnep...@chromium.org, Feb 24 2017 

Relogging worked. I'll run this command on the other 2 bots and then we can see if the tests run properly.

Comment 5 by rnep...@chromium.org, Mar 1 2017

Owner: rnep...@chromium.org
Status: Fixed (was: Untriaged)
►

Sign in to add a comment