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

Add timeouts to evergreen lint tasks.

    • Fully Compatible
    • DAG 2019-09-23
    • 1

      The lint task in evergreen normally takes around 15 - 20 minutes to complete. Over the last 6 months, the highest runtimes we have seen have been around 35 minutes. About a week ago, however, we saw the lint task get hung and didn't exit until the task timed out. The lint task just uses the default timeouts, so it took over 3 hours before the task actually ended.

      Since the lint task is included as part of the commit queue, hangs like this are problematic. They would block the entire queue for a number of hours. To avoid this issue, we should add a more aggressive timeout to the lint task. Something around 40 minutes should be acceptable.


      As a server engineer,
      I want to lint task to timeout if it runs for too long,
      So that I am not waiting on a hung task.


      AC

      • Lint tasks in evergreen time out if running for more than 40 minutes.

            Assignee:
            alexander.costas@mongodb.com Alexander Costas (Inactive)
            Reporter:
            david.bradford@mongodb.com David Bradford (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: