Project

General

Profile

Actions

action #120723

closed

coordination #68794: [qe-core][functional][epic] rework postfail hooks

[qe-core] Guarantee `show_tasks_in_blocked_state` will always be called

Added by szarate about 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Refactor/Code Improvements
Target version:
QA (public, currently private due to #173521) - QE-Core: Ready
Start date:
2022-11-18
Due date:
% Done:

100%

Estimated time:
Difficulty:
Sprint:
QE-Core: January Sprint (Jan 11 - Feb 08)

Description

Currently we're not executing any post_fail_hooks if we're in serial-terminal and it shouldn't be the case, if possible we would like to trigger this from the serial terminal, however at this point it is known that sending special keys does not work, so we might need to resolve to switching to either root-console or log-console for this to work always.

While we're at it, also try to use logger if available, to tag it on the journal, so we can know easily where to look for

This will help us to collect valuable information in case the SUT is experiencing some unforseen load

Tasks

  • Ensure the show_tasks_in_blocked_state is always called, unless the SUT doesn't have a real console
  • If binary logger is available in the system, use it to create a tag so that we know when does the tasks_in_blocked_state start and when do they end

Acceptance Criteria

  1. AC1: show_tasks_in_blocked_state is called unconditionally, unless the SUT doesn't have a real console
  2. AC2: When logger is available, messages can be seen in the journal, signaling the beginning and the end of the trace

Related issues 2 (1 open1 closed)

Related to openQA Tests (public) - action #120720: [qe-core] Use Utils::Logging::save_ulog to redefine upload_logs in opensusebasetestNew2022-11-18

Actions
Copied to openQA Tests (public) - action #120729: [qe-core] *basetest::post_fail_hook: leave early if `NOLOGS` is setResolvedrfan12022-11-18

Actions
Actions

Also available in: Atom PDF