vm-tests: every test's globalTimeout stays under the one-hour job limit
full-setup 7200 -> 2400, semi-spread 10800 -> 3000, and 1800 on the four tests that used the driver's one-hour default. The runner kills a job at one hour and reports nothing, so a longer test timeout could never fire.
This commit is contained in:
parent
2fd1b7b61a
commit
cead194b2a
1 changed files with 18 additions and 3 deletions
|
|
@ -62,8 +62,9 @@ let
|
|||
name = "full-setup";
|
||||
|
||||
# Boot of fourteen containers and the setup steps, with the waits' own
|
||||
# bounds well inside.
|
||||
globalTimeout = 7200;
|
||||
# bounds well inside. Below the runner's one-hour job limit, which also
|
||||
# covers the build before the test starts.
|
||||
globalTimeout = 2400;
|
||||
|
||||
nodes.machine =
|
||||
{ config, ... }:
|
||||
|
|
|
|||
Loading…
Reference in a new issue