test: increase jest test timeout

[patak-dev]

Description

Testing CI after increasing jest test timeout from 30sec to 40sec. I also bumped the local timeout since in my Windows machine is required for tests to pass, so this may be also affecting other contributors.

This is what it took to run test-serve

Test Suites: 28 passed, 28 total
Tests:       228 passed, 228 total
Snapshots:   18 passed, 18 total
Time:        27.369 s

and test-build

Test Suites: 25 passed, 25 total
Tests:       200 passed, 200 total
Snapshots:   0 total
Time:        22.155 s

Additional context

There may be another issue to fix here, but the timeout is generating a lot of noise in CI at this point.

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[patak-dev]

Closing, this is no longer needed after #3097

[patak-dev]

Reopening this PR. We are getting timeouts issues even after fixing the server close race. I think it makes sense to merge this one, while we continue to improve the test suite.

[Shinigami92]

But this is a new failing test 👀

packages/playground/backend-integration/__tests__/backend-integration.spec.ts https:/vitejs/vite/pull/3081/checks?check_run_id=2414364393#step:11:27

[patak-dev]

Yes, but it is failing because of the timeout, maybe because this new test already pushed the test suite to pass the limit.

[patak-dev]

I think you are right @Shinigami92, I tried locally and I also see this error after increasing the timeout.

[nihalgonsalves]

Can you try setting DEBUG=pw:api to try to narrow down why they are failing?

[patak-dev]

I did but looks like it is an issue with the test itself, all other tests are working correctly. Closing this PR again, we should directly talk in #3081