Skip to content

Conversation

prisma-bot
Copy link
Contributor

This automatic PR updates the engines to version 4.5.0-32.a66b69af49362ba2f860db3ab422a3633d3309d2. This will get automatically merged if all the tests pass.

Packages

Package NPM URL
@prisma/engines-version https://npmjs.com/package/@prisma/engines-version/v/4.5.0-32.a66b69af49362ba2f860db3ab422a3633d3309d2
@prisma/prisma-fmt-wasm https://npmjs.com/package/@prisma/prisma-fmt-wasm/v/4.5.0-32.a66b69af49362ba2f860db3ab422a3633d3309d2

Engines commit

prisma/prisma-engines@a66b69af49362ba2f860db3ab422a3633d3309d2

@prisma-bot prisma-bot requested a review from a team October 13, 2022 09:49
@prisma-bot prisma-bot requested review from millsp and removed request for a team October 13, 2022 09:49
@github-actions
Copy link
Contributor

Client memory tests, node 14, library:

❌ Failure, see report.

@github-actions
Copy link
Contributor

Client memory tests, node 16, library:

❌ Failure, see report.

@github-actions
Copy link
Contributor

Client memory tests, node 18, library:

❌ Failure, see report.

@Jolg42
Copy link
Contributor

Jolg42 commented Oct 13, 2022

@SevInf is checking the Client memory tests failures

SevInf pushed a commit to prisma/prisma-engines that referenced this pull request Oct 13, 2022
See prisma/prisma#15772. After 2.10 update, every memory test strted
leaking around 20-100kb per iteration. Reverting napi, napi-derive and
napi-derive-backend to previous versions fixes the issue.
@SevInf
Copy link
Contributor

SevInf commented Oct 13, 2022

Can confirm that the leak is most likely caused by napi update and reverting it to previous version helps. Engine PR

@Jolg42
Copy link
Contributor

Jolg42 commented Oct 13, 2022

New engines PR #15782

@Jolg42 Jolg42 closed this Oct 13, 2022
@Jolg42 Jolg42 deleted the deps/engines-4.5.0-32.a66b69af49362ba2f860db3ab422a3633d3309d2 branch October 13, 2022 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants