df9de3debb
Seems builds in CI have been timing out with the 90s limit and with the shared concurrency of the limited CPUs additional time may be needed to avoid retrying un-necessarily. x-ref: https://github.com/vercel/next.js/actions/runs/4620023451/jobs/8170530943 x-ref: https://github.com/vercel/next.js/actions/runs/4619675493/jobs/8168849370
6 lines
236 B
TypeScript
6 lines
236 B
TypeScript
import * as matchers from 'jest-extended'
|
|
expect.extend(matchers)
|
|
|
|
// A default max-timeout of 90 seconds is allowed
|
|
// per test we should aim to bring this down though
|
|
jest.setTimeout((process.platform === 'win32' ? 180 : 120) * 1000)
|