action #61925
closed
[functional][u] test fails in user_defined_snapshot - Timeout because system takes longer to shutdown
Added by SLindoMansilla over 4 years ago.
Updated about 4 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 30
Description
Observation¶
The system is rebooting twice. The second time, it takes longer than expected to shutdown, causing the needle match "grub2" to timeout.
Tasks¶
- Improve the test by sending key 'esc' to close plymouth and show what is happening in the console.
- Improve the test with shutdown check or increase the timeout.
Reproducible¶
- In scenario sle-15-SP2-Online-x86_64-extra_tests_on_gnome@64bit
- Fails since Build 120.1
Expected result¶
Last good: 108.1
Further details¶
Always latest result in this scenario: latest
This Testcase fails twice in osd. Could we get that fixed until beta2 in two weeks?
- Description updated (diff)
- Status changed from New to Workable
- Priority changed from Normal to High
- Target version set to Milestone 30
- Estimated time set to 42.00 h
- Status changed from Workable to In Progress
- Assignee set to zluo
- Status changed from In Progress to Resolved
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: extra_tests_on_gnome@svirt-xen-hvm
https://openqa.suse.de/tests/3963816
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
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: extra_tests_on_gnome@svirt-xen-hvm
https://openqa.suse.de/tests/4038464
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
Also available in: Atom
PDF