chore(NODE-7765): add default timeouts

[PavelSafronov]

Description

Summary of Changes

This PR adds a default timeout_secs: 300 to all tasks, which means that if the task produces no stdout/stderr output for 5 minutes, the task will be killed.

Notes for Reviewers

Changes:

• set a global 5 minute timeout
• remove existing 5 minute timeouts
• set timeout to be 10 minutes for benchmarks
• when timeout is triggered, log diagnostics data, so we can identify what caused the timeout

What is the motivation for this change?

Timeouts weren't correctly set in evergreen config, so tasks only timed out after 2 hours (default timeout value).

Double check the following

• Lint is passing (npm run check:lint)
• Self-review completed using the steps outlined here
• PR title follows the correct format: type(NODE-xxxx)[!]: description
  • Example: feat(NODE-1234)!: rewriting everything in coffeescript
• Changes are covered by tests
• New TODOs have a related JIRA ticket

[Copilot]

Pull request overview

This PR updates the Evergreen configuration for the MongoDB Node.js driver CI to enforce a consistent default idle timeout across tasks and to collect diagnostic information when timeouts occur, aiming to reduce long-running stalled builds.

Changes:

• Set a global default timeout_secs: 300 (idle timeout) and remove redundant per-command 300s timeouts.
• Replace the timeout handler with a diagnostic shell.exec script to capture directory/process/socket state on timeout.
• Increase benchmark idle timeout to timeout_secs: 600 to accommodate longer silent benchmark runs.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
.evergreen/config.yml	Applies the generated Evergreen config updates: global idle timeout, updated timeout diagnostics handler, and per-command overrides (including benchmarks).
.evergreen/config.in.yml	Source template for Evergreen config: documents and defines the global timeout policy, diagnostics on timeout, and command-specific timeout overrides.

Suppressed comments (2)

.evergreen/config.in.yml:293

• timeout_secs: 60 makes the compile step fail if it is silent for 60s. In run-typescript.sh, npm run build:ts can be quiet while tsc works, and compilation can exceed 60s on slower/contended hosts, leading to flaky CI timeouts. Consider using the 300s default (or adding periodic output).

  "compile driver":
    - command: subprocess.exec
      type: test
      timeout_secs: 60
      params:

.evergreen/config.in.yml:250

• timeout_secs: 60 makes the TypeScript type-check command fail if it is silent for 60s. run-typescript.sh runs node $TSC mongodb.d.ts ... which can be silent until completion and may exceed 60s on slower machines, causing intermittent timeouts. Consider using the 300s default (or adding periodic output).

  "check types":
    - command: subprocess.exec
      type: test
      timeout_secs: 60
      params:

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[PavelSafronov]

Updated comment.

[PavelSafronov]

The tasks resolve in under 15 seconds most of the time, this isn't an issue.