Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase default Jest timeout on long-running tests in CI #1881

Closed
Kaladin13 opened this issue Feb 18, 2025 · 2 comments · Fixed by #1897
Closed

Increase default Jest timeout on long-running tests in CI #1881

Kaladin13 opened this issue Feb 18, 2025 · 2 comments · Fixed by #1897
Assignees
Labels
kind: testing Tests (*.spec.ts) scope: ci Continuous Integration: GitHub Actions (.github), commit/push hooks (.husky)
Milestone

Comments

@Kaladin13
Copy link
Contributor

Kaladin13 commented Feb 18, 2025

Sometimes we get

FAIL src/test/e2e-emulated/contract-with-init-init-parameter.spec.ts (5.616 s)
  ● contract-with-init-init-parameter › should return correct result

    thrown: "Exceeded timeout of 5000 ms for a hook.

Example failing CI

This could be easily avoided with timeout increase

@Kaladin13 Kaladin13 added kind: testing Tests (*.spec.ts) scope: ci Continuous Integration: GitHub Actions (.github), commit/push hooks (.husky) labels Feb 18, 2025
@anton-trunov anton-trunov added this to the v1.6.0 milestone Feb 18, 2025
@anton-trunov
Copy link
Member

let's go for it

@novusnota
Copy link
Member

novusnota commented Feb 18, 2025

There are two config options for the test timeout/threshold:

  1. https://jestjs.io/docs/configuration#slowtestthreshold-number
  2. https://jestjs.io/docs/configuration#testtimeout-number

Bumping the second to 10000 might be more than enough for the time being

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: testing Tests (*.spec.ts) scope: ci Continuous Integration: GitHub Actions (.github), commit/push hooks (.husky)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants