Fix timeouts in backup tests

[aesteve-rh]

These tests run a real vm, and github does not support hardware acceleration, so
we run with emulation (tcg). This is very slow, so the host running the test is
overloaded, it can time out.

Fails in test_incremental_backup_guest take ~20 seconds, using 60 seconds timeout.
Using 120 seconds will likely eliminate these random failures

If not, maybe this is a bug in the code communicating with the vms using serial port:

ovirt-imageio/test/qemu.py

Line 100 in e189066

class Guest:

Ideally, we need to log what we see on the wire in debug level, so when this code fails,
we can understand if the issue was unexpected input from the guest or too slow guest.

[sri-srikanth]

Hey!
I am a Computer Science student at the University of Texas at Austin taking a Virtualization course. My two groupmates and I were wondering if we could contribute to resolving this issue. Please let me know if this would be possible and we can get started.

[aesteve-rh]

Hello @sri-srikanth ,

I think this may not be a good first issue as it is a timeout that happened some time ago in one CI test.
It is not easy to catch or verify. IIRC the issue was more meant to track it in case we saw it failing again.

But you can pick any other issue in the good first issue tag: https://github.com/oVirt/ovirt-imageio/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22

I would be more than happy to help in any of them :)

[sri-srikanth]

Hello @sri-srikanth ,

I think this may not be a good first issue as it is a timeout that happened some time ago in one CI test. It is not easy to catch or verify. IIRC the issue was more meant to track it in case we saw it failing again.

But you can pick any other issue in the good first issue tag: https://github.com/oVirt/ovirt-imageio/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22

I would be more than happy to help in any of them :)

Ah, makes sense. Thank you for informing me. I'll reach out if I have any questions about other issues!