Project

General

Profile

action #109202

Updated by szarate over 2 years ago

## Observation 

 Possibly it's a matter of load on the machine, but increasing the timeout to something like 5 to 10 minutes should be safe. 

 ``` 
 # Test died: command 'zypper -n rm hello{1..9}' timed out at /usr/lib/os-autoinst/testapi.pm line 950. 
 # Test died: command 'zypper lr -d | tee /dev/hvc0' timed out at /usr/lib/os-autoinst/testapi.pm line 1039. (different job) 
 ``` 

 So in the end, that zypper_call needs an increased timeout: `assert_script_run "zypper -n rm hello{1..9}";` and for the `script_run(zypper lr -d)` (which should be `assert_script_run` imo) 

 I'm having the suspicion that memory matters a lot somehow: 

 - https://openqa.suse.de/tests/8420822#step/zypper_in/4 
 - https://openqa.suse.de/tests/8429517/modules/zypper_in/steps/26 

 openQA test in scenario sle-15-SP4-Online-ppc64le-gnome+proxy_SCC+allmodules@ppc64le-2g fails in 
 [zypper_in](https://openqa.suse.de/tests/8429517/modules/zypper_in/steps/26) 

 ## Test suite description 
 Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Maintainers: QE Core, jrauch 
 Install all module which are available through ProxySCC 
 Install as patterns during installation. 

 ## Reproducible 

 Fails since (at least) Build [116.4](https://openqa.suse.de/tests/8375600) 


 ## Expected result 

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


 ## Further details 

 Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=ppc64le&distri=sle&flavor=Online&machine=ppc64le-2g&test=gnome%2Bproxy_SCC%2Ballmodules&version=15-SP4) 

Back