Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
Fully Compatible
-
ALL
-
v3.6
-
TIG 2018-04-23
-
19
Description
While exec_timeout_secs is defined as a top-level field of the task's definition, timeout_secs is defined as a field on an individual function invocation or command. Evergreen doesn't report any errors or warnings for specifying the field in the wrong location, but it ultimately has no effect on the idle timeout used by the agent. This can be verified by the "agent logs" for one of the powercycle tasks.
[2018/04/10 16:32:32.976] Current command set to ''shell.exec' in "run powercycle test"' (system)
|
[2018/04/10 16:32:32.976] Set command timeout for ''shell.exec' in "run powercycle test"' (system) to 2h0m0s
|
...
|
[2018/04/10 16:32:33.562] Current command set to ''shell.exec' in "run powercycle test"' (test)
|
[2018/04/10 16:32:33.562] Set command timeout for ''shell.exec' in "run powercycle test"' (test) to 2h0m0s
|
Attachments
Issue Links
- is caused by
-
SERVER-33696 Set timeout_secs for powercycle* task to restrict the duration of a single powercycle loop
-
- Closed
-