action #32524
closed
[sle][functional][fast][sporadic][yast][medium] test fails in installation_overview_before due to pop-up evaluating package selection is taking longer
Added by JERiveraMoya about 6 years ago.
Updated about 6 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-15-Installer-DVD-x86_64-minimal+base@svirt-hyperv fails in
installation_overview_before
We need to adapt the test as the popup seems taking more time than before.
Acceptance criteria¶
- AC1: check if increasing the timeout is already sufficient
- AC2: try if you can get good results with e.g. wait_screen_change
- AC3: Test is working reliable on o.s.d
Reproducible¶
Fails since (at least) Build 486.4 (current job)
Expected result¶
Last good: https://openqa.suse.de/tests/1506022#step/user_settings_root/3
Further details¶
Always latest result in this scenario: latest
- Subject changed from [sle][functional][easy] test fails in installation_overview_before due to pop-up evaluating package selection is taking longer to [sle][functional][fast][easy] test fails in installation_overview_before due to pop-up evaluating package selection is taking longer
- Due date set to 2018-03-13
- Target version set to Milestone 14
- Description updated (diff)
- Status changed from New to Workable
- Subject changed from [sle][functional][fast][easy] test fails in installation_overview_before due to pop-up evaluating package selection is taking longer to [sle][functional][fast][easy][yast] test fails in installation_overview_before due to pop-up evaluating package selection is taking longer
- Subject changed from [sle][functional][fast][easy][yast] test fails in installation_overview_before due to pop-up evaluating package selection is taking longer to [sle][functional][fast][sporadic][yast][medium] test fails in installation_overview_before due to pop-up evaluating package selection is taking longer
Is sporadic issue, so may not be easy.
- Status changed from Workable to Feedback
- Assignee set to JERiveraMoya
- Status changed from Feedback to Blocked
I guess we need to wait for a build or two to ensure it helped. I set to block to not forget to check later.
Please use "Blocked" only when we are blocked by an external reference. I think "Feedback" is correct here.
- Status changed from Blocked to Resolved
I was not sure about that due to it is someone external to our team triggering the builds, but it is ok, make sense. I set the ticket to resolved as it seems that increasing the timeout helped.
Also available in: Atom
PDF