Project

General

Profile

Actions

action #117256

open

Run a command in the serial terminal producing a clear output

Added by JERiveraMoya over 1 year ago. Updated over 1 year ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2022-09-27
Due date:
% Done:

0%

Estimated time:

Description

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.

Actions #2

Updated by okurz over 1 year ago

  • Project changed from openQA Infrastructure to openQA Project
  • Category set to Feature requests
  • Priority changed from Normal to Low
  • Target version set to future

Thanks for your feature request. This should actually go into "openQA Project", not the infrastructure management per se.

Actions #3

Updated by JERiveraMoya over 1 year ago

  • Description updated (diff)
Actions #4

Updated by jstehlik over 1 year ago

When do you estimate we could have some progress with this? It is definitely not urgent, but until let's say February we should be able to demonstrate some progress to the Labs team.

Actions #5

Updated by okurz over 1 year ago

jstehlik wrote:

When do you estimate we could have some progress with this? It is definitely not urgent, but until let's say February we should be able to demonstrate some progress to the Labs team.

Speaking for the SUSE QE Tools team I see it highly unlikely we would work on this topic within the next months if not years unless we shift around big chunks of our backlog to other teams.

Actions #6

Updated by jstehlik over 1 year ago

We need clear requirements description which should be written by team, which uses the tests or their output e.g. suseLABS team.

Actions #7

Updated by livdywan over 1 year ago

jstehlik wrote:

We need clear requirements description which should be written by team, which uses the tests or their output e.g. suseLABS team.

https://suse.slack.com/archives/C02CANHLANP/p1668672874439519

Actions

Also available in: Atom PDF