action #23944

action #6660: [tools][tools][sprint 201709.1][easy hack] use mojo::log in the worker

Use Mojo::Log in isotovideo to improve logging.

Added by szarate over 2 years ago. Updated over 1 year ago.

Status:ResolvedStart date:06/09/2017
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:Feature requests
Target version:QA - future
Difficulty:
Duration:

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.


Related issues

Related to openQA Project - action #27112: [tools] os-autoinst with proper logging system Resolved 30/10/2017

History

#1 Updated by szarate over 2 years ago

  • Related to action #27112: [tools] os-autoinst with proper logging system added

#2 Updated by dasantiago over 2 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 100

#3 Updated by dasantiago over 2 years ago

  • Status changed from In Progress to Resolved

#4 Updated by okurz over 1 year ago

  • Target version changed from future to future

Also available in: Atom PDF