action #65366
closed[qe-core][qam] [sporadic] test fails with `mydie at /usr/lib/os-autoinst/lockapi.pm line 41.`
0%
Description
Observation¶
random test die sporadically with this message lately
example:
openQA test in scenario sle-15-Server-DVD-Updates-x86_64-qam-rsync-client@64bit fails in
rsync_client
Test suite description¶
Maintainer: klorenzova
Reproducible¶
Fails since (at least) Build 20200407-1 (current job)
Expected result¶
Last good: 20200406-1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by dzedro about 4 years ago
It's this issue https://progress.opensuse.org/issues/65118
Updated by okurz almost 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: qam-vsftpd-client
https://openqa.suse.de/tests/4158832
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by tjyrinki_suse almost 4 years ago
Still happened again a few days ago, rare but happens: https://openqa.suse.de/tests/4270829#step/rsync_client/10
Updated by apappas almost 4 years ago
- Related to coordination #65118: [epic] multimachine test fails with symptoms "websocket refusing connection" and other unclear reasons added
Updated by tjyrinki_suse almost 4 years ago
- Subject changed from [qam] test fails with `mydie at /usr/lib/os-autoinst/lockapi.pm line 41.` to [qam] [sporadic] test fails with `mydie at /usr/lib/os-autoinst/lockapi.pm line 41.`
Updated by tjyrinki_suse over 3 years ago
- Subject changed from [qam] [sporadic] test fails with `mydie at /usr/lib/os-autoinst/lockapi.pm line 41.` to [qe-core][qam] [sporadic] test fails with `mydie at /usr/lib/os-autoinst/lockapi.pm line 41.`
Updated by tjyrinki_suse over 3 years ago
- Status changed from Workable to Resolved
The last 20 runs have succeeded and the related issue is also resolved, maybe this is now properly fixed? Reopen if it fails again.