action #122851
closed
coordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5
Increase timeout in yast2_clone_system for aarch64
Added by JERiveraMoya over 1 year ago.
Updated over 1 year ago.
Description
Observation¶
openQA test in scenario sle-15-SP5-Online-aarch64-clone_system@aarch64 fails in
yast2_clone_system
Despite there was a recent bug for s390x that might put some confusion on this, this last failure seems related only with timeout specially because is running on aarch64.
Acceptance criteria¶
AC1: Bump slightly the timeout to get a successful cloned profile or file a bug if it is not possible.
- Tags set to qe-yast-refinement
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests)
- Target version set to Current
- Parent task set to #121876
- Tags changed from qe-yast-refinement to qe-yam-refinement
- Tags deleted (
qe-yam-refinement)
- Status changed from Workable to In Progress
- Assignee set to syrianidou_sofia
- Status changed from In Progress to Resolved
Increasing the timeout to 500 didn't do the trick. It was expected as the failures are constant since build 38.1. I have opened bug#1207132
syrianidou_sofia wrote:
Increasing the timeout to 500 didn't do the trick. It was expected as the failures are constant since build 38.1. I have opened bug#1207132
Good choice, could you please link your openQA result with 500 timeout in the bug and here?
Also available in: Atom
PDF