Dne 5.1.2018 v 08:23 Akshay Kaushik napsal(a): > Hi, > > I am trying to add a feature to capture console logging information in > Avocado like Autotest. > Checked Autotest code and found that Conmux is being used to capture > console logging. > > Planning to implement the same feature in Avocado. > > Would like to know your suggestions if something in similar line has been > explored. > If it is not explored yet. Please let me know if you have any concerns if I > implement this by integrating Conmux. > > Regards, > Akshay Kaushik >
Hello Mr. Kaushik, I'm sorry for late response, there were some PTOs etc. Yes, this feature sounds useful. About the implementation, can you be more specific on your use cases? Ideally what is the workflow and whether it should be part of a test, or Avocado feature eg. to capture serial consoles throughout the job execution? I'm asking because there is "aexpect" package living under "avocado-framework" umbrella, which allows to execute a command and forward the messages, or even interact in a ShellSession manner. Perhaps it'd be simple to use `aexpect.Tail` resp. `aexpect.ShellSession` to allow read resp. read-write access to `conmux` process. Depending on how much "extra" interaction and tweaks you require it could be used directly, or the "aexpect" can be extended to support "ConmuxSession", or new library in `avocado.utils` could be created to serve as generic serial-console listener but without your workflow I can't tell which would be the best. Once we have a utility to initiate and interact with the serial console, we can use that directly in tests, or we can create pre/post job/test plugin(s) to automatically establish connection and log the output based on params/configuration. Kind regards, Lukáš
signature.asc
Description: OpenPGP digital signature
