Actions
action #23944
closedaction #6660: [tools][tools][sprint 201709.1][easy hack] use mojo::log in the worker
Use Mojo::Log in isotovideo to improve logging.
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2017-09-06
Due date:
% Done:
100%
Estimated time:
Description
Currently logging in isotovideo is done by calling diag, fctinfo, fctwarn, print_possibly_colored and log_call, all of which use directly print, and the output is piped to os-autoinst-log.txt which is then later uploaded as part of the assets.
While this situation has been working for now, we can't use log analyzers or have different levels to see the information of these logs other than downloading the file, grepping et al; It is also not the same logging we use in other parts of openQA (Mojo::Log)
A proposal was made a while ago, to use log4perl which was sane, but the idea had no progress for a while.
Updated by szarate about 7 years ago
- Related to action #27112: [tools] os-autoinst with proper logging system added
Updated by dasantiago about 7 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 100
Updated by dasantiago about 7 years ago
- Status changed from In Progress to Resolved
Actions