QA (public) » openQA Project (public)

Motivation¶

As a reviewer of openQA jobs I would like to be offered a clear output not only for clarity but also for being able to reproduce results manually.
Example:

$self->select_serial_terminal;
script_output "cat /etc/os-release";

In serial_terminal.txt is found:

# cat > /tmp/scriptoW~Qf.sh << 'EOT_oW~Qf'; echo oW~Qf-$?-
> cat /etc/os-release
> EOT_oW~Qf
oW~Qf-0-
# echo oW~Qf; bash -oe pipefail /tmp/scriptoW~Qf.sh ; echo SCRIPT_FINISHEDoW~Qf-$?-
oW~Qf
NAME="SLE_HPC"
VERSION="15-SP5"
VERSION_ID="15.5"
PRETTY_NAME="SUSE Linux Enterprise High Performance Computing 15 SP5"
...
DOCUMENTATION_URL="https://documentation.suse.com/"

When actually it would be more useful to show something like this:

> cat /etc/os-release

NAME="SLE_HPC"
VERSION="15-SP5"
VERSION_ID="15.5"
PRETTY_NAME="SUSE Linux Enterprise High Performance Computing 15 SP5"
...
DOCUMENTATION_URL="https://documentation.suse.com/"

0

Acceptance criteria¶

AC1: Running a command in the serial terminal produces a clear output with stdin, stdout, stderr and retcode in UI and in logs.
AC2: Suppress openQA debug output when selecting serial terminal

Additional information¶

Initial request from HPC is related primarily with how the UI displays the command and its output (in a box in openQA, let's say it like that)
and secondarily in the logs, due to user still needs to search.
This out seems to be related with openQA interacting with the serial at the same time (it is a guess)

# echo oW~Qf; bash -oe pipefail /tmp/scriptoW~Qf.sh ; echo SCRIPT_FINISHEDoW~Qf-$?-
oW~Qf

It might be useful for debugging the problem in some cases, but most of the time what is needed is a clear output.
Example in openQA about the above: https://openqa.suse.de/tests/9565580#step/check_os_release/1 where the logs are showing all these additional lines and the UI is representing too many boxes for each action not really interesting for the user reviewing the job. Of course the whole output might be needed to file a bug to the infrastructure, so this feature could be something to consider as default behavior or as special case.