action #43676
closed
[functional][u][sporadic] - test fails in reboot_gnome - Encrypted setups is taking longer in comparison to previous builds
Added by szarate over 5 years ago.
Updated about 5 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 23
Description
Observation¶
It seems that encrypted scenarios are starting to take longer (Which I would call a peformance regression).
openQA test in scenario sle-15-SP1-Installer-DVD-x86_64-cryptlvm@uefi fails in
reboot_gnome
Reproducible¶
Fails since (at least) Build 91.1 (current job)
Expected result¶
Last good: 88.6 (or more recent)
Suggestions¶
0 - Bugzilla ticket
1 - Do manual validation of the bug, and handle a workaround (that softfails if it takes longer than the mean of 10 runs)
Further details¶
Always latest result in this scenario: latest
- Target version set to Milestone 22
- Status changed from New to Workable
- Priority changed from Normal to Low
- Priority changed from Low to Normal
- Subject changed from [functional][u] - test fails in reboot_gnome - Encrypted setups is taking longer in comparison to previous builds to [functional][u][sporadic] - test fails in reboot_gnome - Encrypted setups is taking longer in comparison to previous builds
- Target version changed from Milestone 22 to Milestone 23
- Blocks action #47855: [functional][u] test fails in reboot_gnome - catch too many tries of send_key_until_needle_match added
- Status changed from Workable to In Progress
- Assignee set to zluo
http://f40.suse.de/tests/1598#step/reboot_gnome/12
I can reproduce this issue. I started 4 workers to overload server a little bit. I see that $bootloader_timeout 300 is not enough because grub2 menu got showed up a little bit later.
It depends sometimes really on server performance.
2 failures of 100 test runs.
So trying with increasing bootloader_timeout: 350
- Status changed from In Progress to Feedback
- Status changed from Feedback to In Progress
updating PR:
increase bootloader_timeout only for installation which has encrypted boot partition and aarch64 as before.
adding a new function 'is_boot_encrypted' to utils so that can be called in reboot_gnome test module.
run verification tests.
- Status changed from In Progress to Feedback
100 verification tests are going. Till now everything looks good.
PR merged. Please, verify on OSD before resolving.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF