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
test(client,sdk,integration-tests): remove --forceExit #7990
Conversation
So the open handle problem has been fixed for BuildKite and locally. Tuned CPU to 15% and I also get open handles locally like on GH. |
Ok, so |
Nice!! Would be good to merge this in chunks, and create other PR maybe if fixing all of them takes long. |
@millsp I think we could merge this soon and create new PRs for the others? |
Ok let me look if I can remove the remaining |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Well done 👍🏼
Co-authored-by: Joël Galeran <Jolg42@users.noreply.github.com>
…#8149) * fix(db push): make sure to stop migrate engine when it errors Related prisma#7795 prisma#7990 * Restore package.json
Figuring why tests are blocking jest from finishing:
https://sourcegraph.com/search?q=context:global+repo:%5Egithub%5C.com/prisma/e2e-tests%24+forceExit&patternType=literal
https://sourcegraph.com/search?q=context:global+repo:github.com/prisma/prisma+--forceExit+count:1000&patternType=literal
Partially fulfills #7795