Project

General

Profile

Actions

action #13276

closed

[tools]'assert_screen fails, but we detected a timeout in the process, so we abort' aka. "stall detected"

Added by okurz over 8 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Infrastructure
Target version:
-
Start date:
2016-08-19
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

observation

There are problems in the testing infrastructure with stalls of the monitoring process for some seconds.

Initially referenced:
https://openqa.suse.de/tests/523174/file/autoinst-log.txt

but there have been corresponding tickets in before

reproducible

sometimes, seem to appear especially when SUT produce a lot of I/O, e.g. install_and_reboot.

expected result

No timeouts in the test, no screens missed.

problem

os-autoinst already detects this

09:39:27.4559 34353 WARNING: There is some problem with your environment, we detected a stall for 12.8205699920654 seconds

and as a consequence already aborts the test

09:39:30.5158 34353 <<< bmwqemu::mydie(cause_of_death='assert_screen fails, but we detected a timeout in the process, so we abort')
DIE mydie at /usr/lib/os-autoinst/backend/baseclass.pm line 853.

but this appears often enough that we should care about to fix the underlying issue and also improve the feedback on detection.


Related issues 3 (0 open3 closed)

Related to openQA Project (public) - coordination #14972: [tools][epic] Improvements on backend to improve better handling of stallsResolvedokurz2016-11-24

Actions
Has duplicate openQA Tests (public) - action #13644: test dies with "timeout in the process"Rejected2016-09-09

Actions
Has duplicate openQA Tests (public) - action #18782: test fails in login_test: stall detectedRejectedokurz2017-04-25

Actions
Actions

Also available in: Atom PDF