Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-34412

powercycle* tasks set timeout_secs in wrong location of task definition

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.6.5, 3.7.4
    • Testing Infrastructure
    • 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
      

      https://evergreen.mongodb.com/task/mongodb_mongo_master_ubuntu1404_powercycle_84762192d91d5f892fe88f2b060a3f2030ab237c_18_04_10_14_44_04

      Attachments

        Issue Links

          Activity

            People

              max.hirschhorn@mongodb.com Max Hirschhorn
              max.hirschhorn@mongodb.com Max Hirschhorn
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: