-
Notifications
You must be signed in to change notification settings - Fork 0
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
Knapsack Jest runs not respecting cache #96
Comments
Please share the knapsack pro command that you use to run tests. Do you pass any options to Jest? |
The command looks like this:
|
What version of Jest have you used before? Please share a link to the slow CI build in the Knapsack Pro user dashboard. You can also share a link to a CI build that is working fine (before Jest update). Please share an output from a CI for the slow CI build. You can send the private data to the support email. Thank you. |
We're coming from Jest version Dependencies that got bumped to support the Jest upgrade:
Dependencies that got bumped while trying to figure out the performance issue:
I've tweaked app configuration in a few places but mostly just required changes to support the Jest upgrade; nothing that seems like it might impact this. Here is a build experiencing slowness I'll dig up some CI output and send it along. Thank you for your help so far, @ArturT ! |
Sorry for the troubles, @what-is-a-crow I tried with several configurations, but couldn't reproduce the issue. I'm surprised because Knapsack Pro should respect the jest cache. It would be fantastic if you could share a minimal repository that reproduces the problem. That would be the quickest way for me to investigate further. If that's not an option, I'd ask you to please help me with the following (feel free to send an email if anything is too sensitive to paste here):
Thanks 🙏 |
We've been using Knapsack Pro with our Jest tests for several months now with no problems; however, when we bump our version of Jest to the latest (29.7.0), the runs in Github Actions go from ~10 minutes each to ~50. The initial load of the app has always been very slow; however, it's a one-time cost, as I believe Jest uses a local cache for subsequent runs. Instead of something like this:
...we're seeing this:
...with the first test of each Jest run taking longer than a minute.
Is our suspicion correct, that Jest is for some reason ignoring the cache and reloading all the modules each time now?
The text was updated successfully, but these errors were encountered: