Project

General

Profile

Actions

action #90692

closed

[sporadic] script_output getting wrong output on aarch64

Added by syrianidou_sofia over 3 years ago. Updated over 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2021-04-06
Due date:
% Done:

0%

Estimated time:

Description

Only for aarch64, the following command:
script_output("cat /proc/sys/kernel/sysrq");
should return the content of the sysrq file, but 10% of the times it returns the character [, which seemt to be taken mistakenly by the serial console.
Failure:
https://openqa.suse.de/tests/5754960#step/yast2_system_settings/51

Actions #1

Updated by coolo over 3 years ago

This has nothing to do with the infrastructure. The serial console gets debug output from the journal. If you don't expect this on the serial console, I guess this is a product bug (if not configured this way in some earlier test)

Actions #2

Updated by syrianidou_sofia over 3 years ago

coolo wrote:

If you don't expect this on the serial console, I guess this is a product bug

The problem here is that the actual output of the command doesn't contain this character at all. See output here: https://openqa.suse.de/tests/5754960#step/yast2_system_settings/50

Actions #3

Updated by coolo over 3 years ago

The output of the command not, but the serial console at the same time - see /49

Actions #4

Updated by syrianidou_sofia over 3 years ago

Ok, but isn't script_output designed to return only the command output?

Actions #5

Updated by coolo over 3 years ago

Not really. it returns whatever the script outputs to the serial console - and everything else the serial console captures at the time.

Actions #6

Updated by syrianidou_sofia over 3 years ago

And why 9 out of 10 times it doesn't capture anything out of the command output for aarch64 and 10/10 for the other architectures. This doesn't seem right to me. There is a function that is not acting in a predictable way. How should I make sure for my test that it will return only the command output?

Actions #7

Updated by coolo over 3 years ago

It's not acting in a predictable way because the system in the background is not predictably generating debug output on the console.

Actions #8

Updated by syrianidou_sofia over 3 years ago

  • Status changed from New to Rejected
Actions

Also available in: Atom PDF