action #127736
closed[qe-core][functonal]test fail in zypper_in [sporadic issue]
100%
Description
Observation¶
openQA test in scenario sle-15-SP5-Full-aarch64-Build93.1-minimal+proxy_SCC-postreg_SUSEconnect@aarch64 fails in
zypper_in
Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Maintainers: riafarov. Register modules after a system is installed using SUSEconnect.
Reproducible¶
Fails since (at least) Build 93.1 (current job)
Expected result¶
Last good: 90.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by mgrifalconi about 1 year ago
I see in the job history that it happened only twice, doing some investigation to see how often it may happen using https://progress.opensuse.org/projects/openqatests/wiki/Wiki#Statistical-investigation
https://openqa.suse.de/tests/overview?build=mgrifalconi_poo127736_investigation
Updated by mgrifalconi about 1 year ago
Tried out long timeout but still sporadically happens. I would rather use a retry in the test (script_retry does not work since it does not retry on timeout events https://openqa.suse.de/tests/overview?build=mgrifalconi_poo127736_fix3 ) or retry the entire test which is simpler.
Updated by mgrifalconi about 1 year ago
If no one is against it, I would like to find a good place to set RETRY=1 for all functional tests, to also be somewhat consistent with maintenance test (where RETRY 1-3 are set)
Updated by mgrifalconi 12 months ago
RETRY=1 set on medium type SLE 15-SP5 Full (all arch)
Updated by mgrifalconi 12 months ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
retry set and working