action #99000
closedtest fails in firstboot_finish_setup due to different timeout with libyui-rest-api
0%
Description
Observation¶
openQA test in scenario sle-15-SP4-Online-x86_64-yast2_firstboot_custom@64bit fails in
firstboot_finish_setup
We should bump the timeout at least to 1 minutes for firstboot, due to we are using here the default one 30 seconds, when in the interactive installation we have even bigger timeout than 1 minute, but we should find a reasonable one, and according to bugs reports, 10-20 seconds to create an user is acceptable, so to have 30 is too closed, and for being safe 1 minutes should not hide any performance bug.
Updated by JERiveraMoya over 2 years ago
- Tags set to qe-yast-refinement
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests) - Priority changed from Normal to High
- Target version set to Current
Updated by JERiveraMoya over 2 years ago
- Tags deleted (
qe-yast-refinement) - Status changed from New to Workable
Updated by JERiveraMoya over 2 years ago
- Status changed from Workable to In Progress
Updated by syrianidou_sofia over 2 years ago
Is this related as well https://openqa.suse.de/tests/7219556#step/firstboot_finish_setup/2 ?
Should I reject https://progress.opensuse.org/issues/99351 ?
Updated by JERiveraMoya over 2 years ago
yes, same story, I will provide VRs for that one too. Thanks.
Wondering what we could do here to improve the error, basically is the typical openQA problem when after failure there is some postfail hook that shows the right screen because it was reached afterward and some press keys even produce the right result... :( Maybe you can rephrase that ticket and use it for that improvement.
Updated by JERiveraMoya over 2 years ago
- Status changed from In Progress to Feedback
Updated by JERiveraMoya over 2 years ago
- Status changed from Feedback to Closed