-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
tests are successful but process ends with error #2415
Comments
I don't think Did you mean to run it as |
yeah, i did mean to
|
@kaminskypavel So this is no an error? |
is the |
no. I mean is I can't to replay it. 🤦 |
I suggest someone else try to run it. Let's see if I'm the only one getting it. Btw I'm using a beast PC (64gb of RAM), so I doubt it has to do with my specs. |
I'm also getting segmentation fault when running my test My config |
Running into the same Segmentation Fault issue with GitHub Actions, even when tests succesfully complete in GitHub Actions using |
Since this is appeared at the top of the Google search, I'm leaving the two things that were causing issues on my side:
|
The recommended solution when working with Prisma is using the |
Describe the bug
migrating prisma examples of integration tests to vitest.
running
pnpm test
- everything is passing, but the process ends with errorsI suspect it has something to do with the in-memory mongo I'm instantiating in
vitest.setup.ts
.jest has
--detectOpenHandles
for this case, but I couldn't find anything related in vitest.off-topic:
what is the recommended way to share env variable from
vitest.setup.ts
and the tests themselves?as per documentation
Reproduction
System Info
Used Package Manager
pnpm
Validations
The text was updated successfully, but these errors were encountered: