Unverified Commit df9de3de authored by JJ Kasper's avatar JJ Kasper Committed by GitHub

Increase CI test timeout (#47973)

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
parent 3f75387b
......@@ -3,4 +3,4 @@ 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 : 90) * 1000)
jest.setTimeout((process.platform === 'win32' ? 180 : 120) * 1000)
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment