Project

General

Profile

Actions
Copy link

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.

Status:
Resolved
Priority:
Normal
Assignee:
dasantiago
Category:
Feature requests
Target version:
QA - future
Start date:
2017-09-06
Due date:
% Done:

100%

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.

Subtasks 3 (0 open — 3 closed)

action #23944: Use Mojo::Log in isotovideo to improve logging. Resolved2017-09-06

Actions
action #25294: [tools] Changes to --verbose flag and logging levels on the workerResolveddasantiago2017-09-14

Actions
action #25296: [tools] Bookmarking of worker log: Have the worker log show what job was it working in the logs.Rejecteddasantiago2017-09-15

Actions
Actions
Copy link
 #1

Updated by lnussel about 9 years ago

  • Estimated time set to 2.00 h
Actions
Copy link
 #2

Updated by okurz over 8 years ago

  • Category set to Feature requests
  • Priority changed from Normal to Low
Actions
Copy link
 #3

Updated by okurz almost 8 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.

Actions
Copy link
 #4

Updated by okurz over 7 years ago

  • 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

Actions
Copy link
 #5

Updated by okurz over 7 years ago

  • Subject changed from use mojo::log in the worker to [easy hack] use mojo::log in the worker
Actions
Copy link
 #6

Updated by dasantiago over 6 years ago

  • Assignee set to dasantiago
Actions
Copy link
 #7

Updated by szarate over 6 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

Actions
Copy link
 #8

Updated by szarate over 6 years ago

  • Description updated (diff)
Actions
Copy link
 #9

Updated by dasantiago over 6 years ago

  • Status changed from New to In Progress
Actions
Copy link
 #10

Updated by dasantiago over 6 years ago

  • Status changed from In Progress to Resolved
Actions
Copy link
 #11

Updated by szarate over 6 years ago

  • 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
Actions
Copy link
 #12

Updated by okurz almost 6 years ago

  • Target version changed from future to future
Actions
Copy link

Also available in: Atom PDF