QA » openQA Project » openQA Tests

Hello, was about to increase the timeout of assert_script_run "-n rm hello{1..9}"; by using zypper_call which has 700s instead of 90s timeout.

But then I came across this discussion https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14448#issuecomment-1063916360

Which leads to this bug https://bugzilla.opensuse.org/show_bug.cgi?id=1197134

Does it means there is nothing to do here and we should wait for the bug to be solved?
CC @szarate

Thanks!

Michael how about the script_run(zypper lr -d) part?

mgrifalconi wrote:

Hello, was about to increase the timeout of assert_script_run "-n rm hello{1..9}"; by using zypper_call which has 700s instead of 90s timeout.

But then I came across this discussion https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14448#issuecomment-1063916360

Which leads to this bug https://bugzilla.opensuse.org/show_bug.cgi?id=1197134

Does it means there is nothing to do here and we should wait for the bug to be solved?
CC @szarate

Looks like but leaves the question of the timeout with zypper lr

Thanks!

Here is the PR open for discussion https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14623

What I did was:

• use zypper_call whenever possible (that will use a big timeout: 700s, retries and other features)
• increase timeout from default of 90 to 180s on script_run when doing zypper calls that cannot use zypper_call

Did not change script_run to assert_script_run because:

• in "zypper lr -d | tee /dev/$serialdev" I thing it would be useless, getting the exit code of tee and not zypper
• in "$r = script_run 'zypper -n in --allow-unsigned-rpm ' . data_url('zypper/hello0.rpm')" would not make sense to me since it already have a different exit code handling in the test