Project

General

Profile

action #56255

Updated by riafarov over 4 years ago

## 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](https://openqa.suse.de/tests/3312919/modules/yast2_snapper/steps/47) 


 ## Reproducible 

 Fails since (at least) Build [0301](https://openqa.suse.de/tests/3312919) (current job) 


 ## Expected result 

 Last good: [0296](https://openqa.suse.de/tests/3299305) (or more recent) 


 ## Further details 

 Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=ppc64le&distri=sle&flavor=Server-DVD&machine=ppc64le&test=sdk%2Ballpatterns&version=12-SP5) 

Back