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
Slow Tests #13092
Comments
Looping this one in too #13029 |
That warning (not error) is expected to be there. What is your complete setup from "checkout repo" to when you run the tests? |
Could you be a little more specific ? |
What did you do to install dependencies and other setup steps after checking out the repo? |
1, NodeVersion: 16.0.0 2, Prerequisites:https://github.com/prisma/prisma/blob/main/CONTRIBUTING.md#general-prerequisites 3, Fork
Navigate into the fork:
Pull upstream main:
4, InstallUse pnpm to install dependency's
5, DockerRun default docker:
5, EnvPlace
5(a), Run Direnv:
6 Run Tests
|
Running the commands using Gitbash on Windows. |
Side note: Instructions on how to install |
Hm, I think I can not reproduce:
Failures are mostly timeouts though indeed:
Computer is a https://www.microsoft.com/en-us/d/surface-laptop-studio/8srdf62swkpf:
(This tool is misreporting the Windows version btw, I am on Win11) |
I beleive this should be fixed right now. iTx caused the slowdown. Issue was fixed in prisma/prisma-engines#3028 |
I'm submitting this issue because I believe there to be a problem with the test suite that is really hindering the contributor developer experience, plus there could be a more serious underlying problem that could be causing this.
I don't believe the specs on my machine to be amazing but nor do I believe them to be low end and I have run test suites, including integrations, of similar size before with no problem.
I'm using the provided
docker-compose
file in thedocker
dir. - This is using about 2GB of ram.When running the tests in the
client
dir for example:I first get a bunch of successful tests and then a warning stating that something has not been awaited:
Shortly after this, I'm getting a few more passing tests then an error stating that there is many instances of Prisma client constructed:
It's at this point when the tests completely stop my machine(100%cpu, 100%ram) and hang for a unknown amount of time sometimes > 1 hour.
I can't trust the location of the warnings because of the way jest is rendering the console logs, and so it's really unknown where this error is happening.
I have tried running the tests with
--maxWorkers=50%
to no avail:PC Specs
Running tests with Gitbash
Related
Some issues I dug out that could be related to this.
nApi
enabled #8989The text was updated successfully, but these errors were encountered: