Allow reservation time up to 99 hours
The fix from !52 (merged) doesn't work (or no longer works). For example, if the reservation is set to 2880 minutes (= 48 hours), the timeout is still reached after 12 hours as before. See:
Maximum test time '12h' exceeded.
Adjust the test 'duration' attribute if necessary.
Can we hardcode sufficient value as a solution? (If we set it to 99 hours maximum, we also as a side effect match the Beaker reservation policy which is set to 99 hours as maximum value.) This change is well tested, as I used this fix for my own jobs (just with different value).
Example of the job using hardcoded value:
- https://artifacts.osci.redhat.com/testing-farm/aa8e1351-9487-494c-baae-3b6bf2366b64/
- https://artifacts.osci.redhat.com/testing-farm/aa8e1351-9487-494c-baae-3b6bf2366b64/work-gating_stage_test_ovmfneeu0zoi/plans/rhel/kar/test-ci-maint/stage/gating_stage_test_ovmf/execute/data/guest/main/default-0/testing-farm/reserve-system-4/output.txt
Signed-off-by: Lukas Kotek lkotek@redhat.com