Skip to content

test(browser): bump testTimeout for Windows runners#10566

Draft
jaxalo wants to merge 10 commits into
vitest-dev:mainfrom
jaxalo:fix/browser-windows-timeout
Draft

test(browser): bump testTimeout for Windows runners#10566
jaxalo wants to merge 10 commits into
vitest-dev:mainfrom
jaxalo:fix/browser-windows-timeout

Conversation

@jaxalo

@jaxalo jaxalo commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Windows runners (especially webkit) cold-start much slower than mac/linux. Bumping the wrapper testTimeout/hookTimeout from 360s to 600s on Windows to stop the parent killing legitimately-slow sub-vitest runs.

Description

Resolves #issue-number

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
  • Ideally, include a test that fails without this PR but passes with it.
  • Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.
  • Please check Allow edits by maintainers to make review process faster. Note that this option is not available for repositories that are owned by Github organizations.

Tests

  • Run the tests with pnpm test:ci.

Documentation

  • If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

  • Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.
jaxalo and others added 7 commits June 10, 2026 17:11
Windows runners (especially webkit) cold-start much slower than mac/linux.
Bumping the wrapper testTimeout/hookTimeout from 360s to 600s on Windows
to stop the parent killing legitimately-slow sub-vitest runs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The `timeout hooks` test in `test/browser/specs/runner.test.ts` was snapshotting
the ordered stderr output of a fixture that intentionally fails. Output order
varies across runs because:

- `onTestFailed > fails*` tests fire both an AssertionError (from
  `expect.unreachable()`) and a TimeoutError (from the deferred
  `page.getByTestId('non-existing').click()`), and their interleaving on stderr
  varies.
- Concurrent browsers (chromium/firefox/webkit) write to stderr in a
  nondeterministic order.

Replace the ordered snapshot with a set-membership assertion: for each
(browser, testName) combo expected from the fixture, assert at least one
matching FAIL header exists. Keep a source-map regression sample for
`click on non-existing element fails` (single error variant, stable line).

Drops 235 lines of brittle snapshot. Source-map coverage preserved via sample.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@netlify

netlify Bot commented Jun 11, 2026

Copy link
Copy Markdown

Deploy Preview for vitest-dev ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 56c91a0
🔍 Latest deploy log https://app.netlify.com/projects/vitest-dev/deploys/6a2c85e8a7e75c0008c3c57b
😎 Deploy Preview https://deploy-preview-10566--vitest-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

jaxalo and others added 3 commits June 11, 2026 11:04
- Tighten failHeaderRe/sourceRe to avoid regex/no-super-linear-backtracking
  (replace `\s+`/`\s*` with literal spaces — log format uses single spaces).
- Drop double blank line.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant