Replies: 2 comments 5 replies
-
Been seeing the same on GitLab CI test jobs using gitlab runners as well (locally works totally fine):
Using Unfortunately there is not much to indicate what is causing the error, so as said above, having some way to catch and report what exactly such errors might be within Vitest would be very useful for debugging. |
Beta Was this translation helpful? Give feedback.
-
We've started seeing this same error in our CI pipeline (vitest |
Beta Was this translation helpful? Give feedback.
-
Hi,
I've been struggling with the
Unhandled error
exception in our test files using for"vitest": "^1.6.0"
. The error appears only in the CircleCI test job (locally it works fine). I tried to debug what is causing the issue but couldn't find out the root cause because the reported Unhandled error is not bound to any failing test file. We had usedpool: 'forks'
before I changed it to the default behaviour (default isthreads
I think) and the problem has gone.An additional context: We use Prisma calls in our integration test files. The error looks following (missing reference to the test file):
My question/plea is if it's possible to somehow catch the
Unhandled error
within the Vitest context? If not, it would be really nice to have some kind of ability to either catch the error or report the file in which the error occurred.Beta Was this translation helpful? Give feedback.
All reactions