BattOr tracing occasionally fails due to failure to open serial port |
||
Issue descriptionOriginally reported as: https://github.com/catapult-project/catapult/issues/4270 https://pinpoint-dot-chromeperf.appspot.com/job/13d3f97d840000 https://chromium-swarm.appspot.com/task?id=3bb27b6e5330d410 BattOrError: BattOr did not complete command 'StartTracing' correctly. Outputted: [0215/053306.180051:ERROR:serial_io_handler.cc(149)] Failed to open serial port: FILE_ERROR_ACCESS_DENIED This appears to be happening on Dockered Android bots, so the problem could be either with Linux itself or with the way that Docker interacts with the BattOr port mapping.
,
Feb 27 2018
Incidentally, that task you linked didn't run in docker. (Check the "inside_docker: 0" boolean in the bot's dimensions that ran that test.) So it's probably got something to do with the base linux. I recall there needing to be some system group modifications when deploying a battor to a linux box. Maybe that didn't happen/needs happening again?
,
Mar 1 2018
Thanks for thinking of that Ben - SSHing into the bot, it looks like you're absolutely right. I think that the underlying bug here is that puppet should really be the one managing the dialout groups, and instead we're relying on manual intervention by the labs team. I'm going to go ahead and write a quick puppet class that can manage this for us.
,
Mar 16 2018
|
||
►
Sign in to add a comment |
||
Comment 1 by charliea@chromium.org
, Feb 27 2018