Skip to content

ci: give every Windows CI job the 70 minute timeout - #340816

Open
Michael Lively (Yoyokrazy) wants to merge 1 commit into
mainfrom
agents/windows-ci-timeout-70
Open

Michael Lively (Yoyokrazy) wants to merge 1 commit into
mainfrom
agents/windows-ci-timeout-70

Conversation

@Yoyokrazy

Copy link
Copy Markdown
Collaborator

Refs microsoft/vscode-engineering#2896. Follow-up to #340808.

#340808 raised Windows Unit Tests to 70 minutes. Browser & Remote and Integration (Electron) also time out at 50 minutes when the node_modules cache misses, because the clean install takes about 14–16 minutes on Windows. This PR gives every Windows CI job 70 minutes. The timeout is only an upper bound, so runs with a warm cache don't get slower.

Main CI, Sep 30–Oct 9 (247 builds, 35 with a cold Windows cache):

Windows job Timeout before Cold-cache timeouts at 50m Cold runs within 3 min of 50 Slowest cold run
Unit Tests 70 (#340808) 13 11 53.1m
Browser & Remote 50 3 (481525, 481690, 482239) 7 (482906: 47.3m) 50.9m
Integration (Electron) 50 1 (481097) 6 (482462: 49.0m) 50.9m
Smoke (Electron) 70 0 4 53.7m

Every timeout was on a cold cache. With a warm cache, no Windows job went above 36.2m.

How to test

Command Result
node --test build/lib/test/testCheckpointTemplates.test.ts build/lib/test/testCheckpoint.test.ts ✅ 30 passed (the #340808 template test is updated to expect an unconditional 70)
eslint build/lib/test/testCheckpointTemplates.test.ts ✅ passed

#340808 raised only Unit Tests to 70 minutes. Browser & Remote and
Integration (Electron) also time out at 50 minutes after a node_modules
cache miss: since Sep 30, 3 and 1 of 35 cold Windows builds timed out,
and another 7 and 6 finished within 3 minutes of the limit.

Refs: microsoft/vscode-engineering#2896

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI balanced review requested due to automatic review settings October 9, 2026 22:58
Michael Lively (Yoyokrazy) added a commit that referenced this pull request Oct 9, 2026
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The focused pipeline and test changes correctly implement the stated timeout policy without affecting other platforms or product-build jobs.

0 open findings

What changed in this PR

Extends all Windows x64 CI test jobs to a 70-minute timeout for cold dependency installs.

Changes:

  • Replaces conditional 50/70-minute limits with an unconditional 70-minute limit.
  • Updates the regression test while preserving the 10-minute cancellation timeout.
File Description
build/​azure-pipelines/​win32/​product-build-win32-ci.yml Sets every Windows CI test job to 70 minutes.
build/​lib/​test/​testCheckpointTemplates.test.ts Verifies the unconditional timeout and cancellation limit.

🧠 Review effort: Balanced


💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@Yoyokrazy

Copy link
Copy Markdown
Collaborator Author

cc Bryan Chen (@bryanchen-d): follow-up to #340808. Browser & Remote and Integration (Electron) still time out at 50 minutes on cold-cache builds: 3 and 1 timeouts since Sep 30 (481525, 481690, 482239; 481097), and 482906 today hit 47.3m on Browser & Remote. This gives every Windows CI job 70 minutes. Auto-merge is on.

@vs-code-engineering

Copy link
Copy Markdown
Contributor

📬 CODENOTIFY

The following users are being notified based on files changed in this PR:

Ladislau Szomoru (@lszomoru)

Matched files:

  • build/azure-pipelines/win32/product-build-win32-ci.yml

This branch has not been deployed

No deployments
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.

2 participants