Coming from https://github.com/rancher/distros-test-framework/pull/74/files#r1540032497
The first job timed out after an hour. The second job completed successfully after 9 minutes. The only difference between the two was a sleep 20. This isn't the only time this has happened, but this is a good case for this.
We need to improve timeouts to:
Have shorter times. If in fact 20 seconds is enough in this case, then that test/function/etc. should timeout after 20 seconds, not an hour.
Give better information; show what/where/why it is timing out. The timed out test failure here doesn't give any useful information. It just shows the test itself that was running, not where in the test exactly it timed out and why (see below).
Coming from https://github.com/rancher/distros-test-framework/pull/74/files#r1540032497 The first job timed out after an hour. The second job completed successfully after 9 minutes. The only difference between the two was a
sleep 20
. This isn't the only time this has happened, but this is a good case for this.We need to improve timeouts to:
Give better information; show what/where/why it is timing out. The timed out test failure here doesn't give any useful information. It just shows the test itself that was running, not where in the test exactly it timed out and why (see below).