Open lilnasy opened 8 months ago
We should actually remove turborepo caching when running the tests - always. I don't know turborepo very well though, I don't know how to configure that
I agree.
I don't think we should remove turborepo. The issue is that we did not configure the dependency of Astro to the other integrations, so when Astro core is updated, turborepo didn't invalidate the cache for the other integrations.
The last time I checked, I didn't fix it is because it'll cause way longer test times, but if we're fine with the tradeoff for more robust testing, we can definitely fix that.
If we remove turborepo entirely, tests will unnecessarily run. For example, if we update the @astrojs/vercel
only, we should only run its tests and not Astro core.
No one suggested removing turborepo, but simply removing the caching of the tests. IMHO test tasks shouldn't be cached.
Describe the Bug
What's the expected result?
The tests get executed.
Link to Minimal Reproducible Example
https://github.com/withastro/astro/blob/main/packages/integrations/node/test/errors.test.js
Participation