action #6660
closed
[tools][tools][sprint 201709.1][easy hack] use mojo::log in the worker
Added by lnussel about 9 years ago.
Updated almost 6 years ago.
Category:
Feature requests
Estimated time:
(Total: 0.00 h)
Description
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.
- Estimated time set to 2.00 h
- Category set to Feature requests
- Priority changed from Normal to Low
- 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.
- Target version changed from Easy hacks to future
as mentioned on irc os-fctry: [Wednesday, 30 November 2016] [15:34:56 CET] anyone minds if I replace the milestone "easy hacks" with a keyword in subject line? IMHO it's not a proper milestone and not at all useful for the roadmap
- Subject changed from use mojo::log in the worker to [easy hack] use mojo::log in the worker
- Assignee set to dasantiago
- Description updated (diff)
- Status changed from New to In Progress
- Status changed from In Progress to Resolved
- Subject changed from [easy hack] use mojo::log in the worker to [tools][tools][sprint 201709.1][easy hack] use mojo::log in the worker
- Target version changed from future to future
Also available in: Atom
PDF