action #64523
openopenQA Project (public) - coordination #154768: [saga][epic][ux] State-of-art user experience for openQA
openQA Project (public) - coordination #157510: [epic] Up-to-date JavaScript stack
[openqa-in-openqa][sporadic] test fails in sometimes openqa_webui waiting for output from nohup.out, potential race condition?
0%
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