Skip to content

docs(ci): recommend globalTimeout instead of a CI job timeout - #42563

Merged
Dmitry Gozman (dgozman) merged 1 commit into
microsoft:mainfrom
dgozman:fix-42533
Sep 4, 2026
Merged

docs(ci): recommend globalTimeout instead of a CI job timeout#42563
Dmitry Gozman (dgozman) merged 1 commit into
microsoft:mainfrom
dgozman:fix-42533

Conversation

@dgozman

@dgozman Dmitry Gozman (dgozman) commented Sep 4, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Add a "Global timeout" section to ci.md and a note in ci-intro.md: a job-level timeout kills the run mid-flight, so the job reads as cancelled and no report is produced.
  • Drop timeout-minutes from all workflow examples in ci.md, ci-intro.md and test-sharding-js.md.
  • Add globalTimeout to the full config example and the options table in test-configuration-js.md.

create-playwright is updated to match in microsoft/create-playwright#181.

Fixes #42533

@holistis

Copy link
Copy Markdown

Just noticed this landed, along with create-playwright#181. I asked for a note in the docs and you fixed the scaffolding itself, which is the version of this that actually matters, since it means every new project gets the safe default without anyone having to read the note in the first place. Thanks for going further than the issue asked for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs: ci.md recommends a job timeout with no globalTimeout, so an over-running suite is cancelled with no report

3 participants