action #127976
closed
coordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5
Bump timeout for mediacheck in aarch64
Added by JERiveraMoya about 1 year ago.
Updated about 1 year ago.
Description
Motivation¶
aarch64 is slow and in this build for few seconds the timeout is short, we should bump it a bit
openQA test in scenario sle-15-SP5-Full-aarch64-mediacheck@aarch64 fails in
mediacheck
Acceptance criteria¶
AC1: Bump timeout for checking media ensuring it also works in aarch64
Additional information¶
330 or 360 might be ok and we don't need to put any extra condition to only increase it in aarch64.
Consider if 1 additional minute is ok or not without condition, but 30 seconds definitely will be ok.
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests)
- Target version set to Current
- Status changed from Workable to In Progress
- Assignee set to coolgw
Base following result the max timeout is 900-476=424
https://openqa.suse.de/tests/10952849/logfile?filename=autoinst-log.txt
[2023-04-20T02:47:32.903326+02:00] [debug] [pid:31009] <<< testapi::assert_screen(mustmatch=[
"mediacheck-select-device",
"mediacheck-ok",
"mediacheck-checksum-wrong"
], timeout=300)
[2023-04-20T02:47:33.412961+02:00] [debug] [pid:31169] no match: 899.5s, best candidate: mediacheck-ok-20150326 (0.34)
[2023-04-20T02:47:34.372468+02:00] [debug] [pid:31169] no change: 898.5s
[2023-04-20T02:47:34.411067+02:00] [debug] [pid:31169] no match: 898.5s, best candidate: mediacheck-ok-20150326 (0.34)
[2023-04-20T02:47:35.373748+02:00] [debug] [pid:31169] no change: 897.5s
...
[2023-04-20T02:54:35.870457+02:00] [debug] [pid:31169] no match: 477.0s, best candidate: mediacheck-ok-20150326 (0.00)
[2023-04-20T02:54:36.830427+02:00] [debug] [pid:31169] no change: 476.0s
[2023-04-20T02:54:36.870579+02:00] [debug] [pid:31169] no match: 476.0s, best candidate: mediacheck-ok-20150326 (0.00)
[2023-04-20T02:54:38.340576+02:00] [warn] [pid:31169] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 0.51 seconds for 2 candidate needles - make your needles more specific
- Status changed from In Progress to Resolved
Also available in: Atom
PDF