[tools][tools][sprint 201709.1][easy hack] use mojo::log in the worker
|Target version:||QA - future|
The worker app should use Mojo::Log by setting up a mojo fake app, to ensure that the logging facility is the same across all parts of openQA.
mudler | log_* calls are checking if there is an app and route the messages to Mojo::Log mudler | https://github.com/os-autoinst/openQA/blob/master/lib/OpenQA/Utils.pm#L101 && mudler | https://github.com/os-autoinst/openQA/blob/master/lib/OpenQA/Utils.pm#L212
Using these different calls, leaves us with a bit of inconsistency when reading log output from different parts.
#3 Updated by okurz almost 4 years ago
- Priority changed from Low to Normal
I don't know why I lowered priority and I should not without giving a reason ;-)
I don't really understand the benefit of the ticket as described but coolo said it would help us to gather logs of the worker which we could store with the test, e.g. store "ps axf" output every two minutes to see if SUT is under load when wait_serial or assert_screen times out.
#4 Updated by okurz over 3 years ago
- Target version changed from Easy hacks to future
as mentioned on irc os-fctry: [Wednesday, 30 November 2016] [15:34:56 CET]
#7 Updated by szarate over 2 years ago
A while ago, I was working on a similar thing but using log4perl instead of Mojo::Log. While is not the best approach, here was part of the idea... https://github.com/os-autoinst/os-autoinst/pull/691