action #56255
closed
[functional][y] redesign yast2_snapper test to make it stable
Added by SLindoMansilla over 4 years ago.
Updated over 4 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 29
Description
Observation¶
We see a lot of sporadic failures in the test module because we fail to select last leave in the tree.
We need better approach to handle this case.
To make it stable, we should have control over snapshot, and take one after modifying single file, so have strict expectations what we will have in snapshot diff.
On top we could use separate filesystem, as root is polluted with different artifact of running services and separate fs won't have such issue.
We also consider moving this test to yast job group.
openQA test in scenario sle-12-SP5-Server-DVD-ppc64le-sdk+allpatterns@ppc64le fails in
yast2_snapper
Reproducible¶
Fails since (at least) Build 0301 (current job)
Expected result¶
Last good: 0296 (or more recent)
Further details¶
Always latest result in this scenario: latest
- Target version set to Milestone 28
this is flaky test, I do not see a reason to invest any time on it, we already have wasted enough. I would move it from your job group, so you don't have to file these tickets about sporadic issues which we reject in the end...
- Subject changed from [functional][y] test fails in yast2_snapper - Tests needs adaption to GUI changes, maybe just new needles to [functional][y] redesign yast2_snapper test to make it stable
- Description updated (diff)
- Due date set to 2019-11-05
- Target version changed from Milestone 28 to Milestone 29
- Related to action #57749: [functional][y] apply solution for yast2_snapper_ncurses as it does for Tumbleweed added
- Description updated (diff)
- Status changed from New to Workable
- Estimated time set to 8.00 h
- Assignee set to JERiveraMoya
- Status changed from Workable to Feedback
- Status changed from Feedback to In Progress
- Status changed from In Progress to Feedback
- Status changed from Feedback to In Progress
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
- Due date changed from 2019-11-05 to 2019-11-19
- Status changed from Resolved to In Progress
- Status changed from In Progress to Feedback
- Status changed from Feedback to In Progress
There are still a couple of failures in textmode:
- Status changed from In Progress to Feedback
- Related to action #58631: [functional][y][fast] test fails in yast2_snapper added
- Status changed from Feedback 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: yast2_ncurses
https://openqa.suse.de/tests/3576426
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