Project

General

Profile

action #64523

[openqa-in-openqa][sporadic] test fails in sometimes openqa_webui waiting for output from nohup.out, potential race condition?

Added by okurz about 3 years ago. Updated 9 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2020-03-16
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario openqa-Tumbleweed-dev-x86_64-openqa_from_git@64bit-2G fails in
openqa_webui
waiting for output in the file nohup.out. Looking at the intermangled output from nohup and the assert_script_run there might be a race condition when the followup command tries to wait for output in nohup.out which not even be properly created at the time.

Test suite description

Maintainer: okurz@suse.de Test for running openQA itself from git. To be used with "openqa" distri.

Reproducible

Seems to have failed some times, partially reproducible.

Expected result

Last good: :TW.4289 (or more recent)

Suggestion

Maybe better to wait until the file nohup.out exists and only then try to look for output in there.

Further details

Always latest result in this scenario: latest

History

#1 Updated by okurz over 1 year ago

This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . Please consider picking up this ticket within the next 365 days or just set the ticket to the next lower priority of "Low" (no SLO related time period). This update was done as agreed within the SUSE QE Sync call 2021-09-01

#2 Updated by slo-gin 9 months ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Also available in: Atom PDF