Repository navigation
ci: Keep downloaded Prisma engines on the Namespace cache volume - #25665
Closed
sentry-junior[bot] wants to merge 1 commit into
Closed
sentry-junior[bot] wants to merge 1 commit into
sentry-junior[bot] wants to merge 1 commit into
Conversation
The Prisma suites install prisma into a tmp dir in their beforeAll hook. Its postinstall downloads about 34 MB of engines into ~/.cache/prisma, which is not on the cache volume, so every shard downloads them again. Co-Authored-By: Joshua Li <14209781+joshuarli@users.noreply.github.com>
joshuarli
approved these changes
Oct 22, 2026
Contributor
size-limit report 📦Compared: d395302 (PR test merge using develop at 40eff80) Against: 40eff80 (develop) · base run #63186 ✅ Baseline matches: this diff contains only this PR's changes.
|
Contributor
Optional E2E testsSome optional checks were not successful. They do not block the merge. 4 failing, 60 successful. See the run.
Successful checks
|
Contributor
Author
|
Superseded by #25668, which combines these CI changes so the suite runs once. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Prisma suites (
prisma-orm-v5tov8)npm installprisma into a tmp dir inside their 120 sbeforeAllhook. Prisma's postinstall then downloads about 34 MB of query and schema engines frombinaries.prisma.shinto~/.cache/prisma. The npm cache is already on the Namespace volume, but~/.cache/prismaisn't, so every Node, Bun and Deno integration shard downloads the engines again. This mounts the folder the same way~/.cache/mongodb-binariesis mounted.This is the most common Node integration flake right now. I checked 9 failed Node integration jobs from today. 8 of them failed with
Hook timed out in 120000msin that hook forprisma-orm-v5orprisma-orm-v7, on both Node 24 and Node 26 shards. Some of those jobs got an empty cache volume, so this won't fix every case. It does remove the one download that happens on every run, even when the volume is warm.via @joshuarli.
--
View Junior Session [Sentry]