Project

General

Profile

Actions
Copy link

action #181328

closed

test fails in perf: serial console being inaccessible after perf list

Added by dimstar 3 days ago. Updated about 21 hours ago.

Status:
Resolved
Priority:
Normal
Assignee:
szarate
Category:
Bugs in existing tests
Target version:
-
Start date:
2025-04-23
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

This seems to be the cause for the recent incomplete observed. perf has increased runtime from ~ 1 minute to ~ 8 minutes. Apparently, perf list sw can happen to reach a 'pager' - which then blocks the serial console (despite timeout being used)

It can be observed that after the perf test run, almost all serial interactions end up 'failed' - and all subsequent test runs take forever (sysstat increased from 1 minute to 1.5 hours)

openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-extra@64bit_virtio-4G fails in
perf

Test suite description

Same as jeos, plus some more tests.

Reproducible

Fails since (at least) Build 20250331

Expected result

Last good: 20250329 (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by dimstar 3 days ago

To further confirm perf being the issue here, I have clone the job with EXCLUDE_MODULES=perf (i.e do not run the perf test module) - that's is currently running as https://openqa.opensuse.org/tests/5014401 - result pending

Actions
Copy link
 #2

Updated by favogt 3 days ago

It looks like timeout ... "foo | less" leaves echo in the console turned off.

Actions
Copy link
 #3

Updated by favogt 3 days ago ยท Edited

In a previous faster run it printed

WARNING: terminal is not fully functional
Press RETURN to continue xB4d_-124-

which is to be expected - it should have TERM=dumb set in the environment.

Actions
Copy link
 #4

Updated by szarate 2 days ago

favogt wrote in #note-3:

In a previous faster run it printed

WARNING: terminal is not fully functional
Press RETURN to continue xB4d_-124-

which is to be expected - it should have TERM=dumb set in the environment.

It can be as easy as passing --no-pager to perf, lets see: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/21869

Actions
Copy link
 #5

Updated by mloviska 2 days ago

The culprit was https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/21832 as PAGER was set to more when TERM=dumb is used. As of now the change was reverted.

Actions
Copy link

Also available in: Atom PDF