Actions
action #120723
closedcoordination #68794: [qe-core][functional][epic] rework postfail hooks
[qe-core] Guarantee `show_tasks_in_blocked_state` will always be called
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 thetasks_in_blocked_state
start and when do they end
Acceptance Criteria¶
- AC1:
show_tasks_in_blocked_state
is called unconditionally, unless the SUT doesn't have a real console - AC2: When
logger
is available, messages can be seen in the journal, signaling the beginning and the end of the trace
Actions