doc/coding-conventions: Increase passthru test timeout 3s -> 60s
3s is too small a margin for a loaded slow system to start a bloated program. This leads to problems when tests are written on decent dev hardware but later run on build farms of potentially slower hardware, particularly in the case of non x86. The chance of needing the timeout is actually very small, so those rare 57s are a reasonable price to pay for fewer timeouts on build farms, each of which should be investigated and usually fixed by increasing the timeout.
This commit is contained in:
parent
b141a58ff2
commit
840fd0a4f8
2 changed files with 2 additions and 2 deletions
|
@ -568,7 +568,7 @@ let
|
||||||
inherit (phoronix-test-suite) pname version;
|
inherit (phoronix-test-suite) pname version;
|
||||||
in
|
in
|
||||||
|
|
||||||
runCommand "${pname}-tests" { meta.timeout = 3; }
|
runCommand "${pname}-tests" { meta.timeout = 60; }
|
||||||
''
|
''
|
||||||
# automatic initial setup to prevent interactive questions
|
# automatic initial setup to prevent interactive questions
|
||||||
${phoronix-test-suite}/bin/phoronix-test-suite enterprise-setup >/dev/null
|
${phoronix-test-suite}/bin/phoronix-test-suite enterprise-setup >/dev/null
|
||||||
|
|
|
@ -4,7 +4,7 @@ let
|
||||||
inherit (phoronix-test-suite) pname version;
|
inherit (phoronix-test-suite) pname version;
|
||||||
in
|
in
|
||||||
|
|
||||||
runCommand "${pname}-tests" { meta.timeout = 3; }
|
runCommand "${pname}-tests" { meta.timeout = 60; }
|
||||||
''
|
''
|
||||||
# automatic initial setup to prevent interactive questions
|
# automatic initial setup to prevent interactive questions
|
||||||
${phoronix-test-suite}/bin/phoronix-test-suite enterprise-setup >/dev/null
|
${phoronix-test-suite}/bin/phoronix-test-suite enterprise-setup >/dev/null
|
||||||
|
|
Loading…
Reference in a new issue