action #56087
closed
[sle][functional][u] test fails in shutdown - no candidate needle with tag(s) 'logoutdialog' matched, timeout issue
Added by zluo over 4 years ago.
Updated over 4 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 28
Description
It seems that 15 seconds is not enough on arrch64, suggest to increase a little bit for this.
Observation¶
openQA test in scenario sle-12-SP5-Server-DVD-aarch64-create_hdd_gnome@aarch64 fails in
shutdown
Test suite description¶
image creation job used as parent for other jobs testing based on existing installation. To be used as START_AFTER_TEST=create_hdd_gnome
Tasks¶
- Use WORKER_CLASS=$hostname to overload the machine.
- Try with and without VNC_TYPING_LIMIT
- Make sure that there are at least 4 runs of overloading.
- Get statistics
Reproducible¶
Fails since (at least) Build 0296 (current job)
Expected result¶
Last good: 0294 (or more recent)
Further details¶
Always latest result in this scenario: latest
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: create_hdd_gnome
https://openqa.suse.de/tests/3340468
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: create_hdd_gnome
https://openqa.suse.de/tests/3340468
- Priority changed from Normal to High
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: sdk+allpatterns
https://openqa.suse.de/tests/3506772
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
- Description updated (diff)
- Status changed from New to Workable
- Target version set to Milestone 28
- Estimated time set to 42.00 h
- Status changed from Workable to In Progress
- Assignee set to zluo
successful, Assigned worker:
openqaworker-arm-2:1
openqaworker-arm-1:5 with softfail
openqaworker-arm-1:7 with softfail
openqaworker-arm-1:6 with softfail
openqaworker-arm-1:2¶
imcomplete or not started, Assigned worker:
openqaworker-arm-2:14
openqaworker-arm-2:8
openqaworker-arm-2:28
openqaworker-arm-2:4
openqaworker-arm-2:12
openqaworker-arm-2:26
openqaworker-arm-2:15
openqaworker-arm-2:30
openqaworker-arm-2:5
openqaworker-arm-2:20
openqaworker-arm-2:24
--
failed, Assigned worker:
openqaworker-arm-1:11 first_boot failed because 'Stall was detected during assert_screen fail'
So this is quite clear now. We have performance issue with openqaworker-arm-1 and openqaworker-arm-2 needs to be investigated why workers are even not really started the job.
After we the rest of aarch64 workers have been ahutdown, it looks much better, but still we have issue with performance issue: Stall detected
for example:
https://openqa.suse.de/tests/3676004
So we should reduce workers further if we want get ride of these issue on openqaworker-arm-1 and openqaworker-arm-2
- Status changed from In Progress to Resolved
Also available in: Atom
PDF