jest-image-snapshot: Error: "Error running image diff." for large images
Hey,
for some of my tests I get the error Error running image diff.
.
As those are the longest pages e.g. 14252px
I assume the length is the deciding factor.
Other pages work fine. The diff file was also created and is in the folder.
Can I do something to fix this (e.g. is there a config option I missed)?
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 1
- Comments: 37 (17 by maintainers)
Commits related to this issue
- fix: issue #210 Issue results from max buffer size being fixed to 10MB. Replaced with maximum allowable memory so that it becomes the imperative of the user if the user performs tasks that cause an ... — committed to omnisip/jest-image-snapshot by omnisip 4 years ago
- fix: issue #210 Issue results from max buffer size being fixed to 10MB. Replaced with maximum allowable memory so that it becomes the imperative of the user if the user performs tasks that cause an ... — committed to omnisip/jest-image-snapshot by omnisip 4 years ago
Hi, this is happening to me to a lot. Curious though I cannot reproduce this issue locally, only when running on CI environment through TeamCity build pipeline
This issue is stale because it has been open 30 days with no activity.
You’re welcome. Let’s see what we can do about finding a really large PNG file…
On Thu, Jul 23, 2020 at 8:06 PM Lukas Oppermann notifications@github.com wrote:
I recently came accross this project: https://github.com/dmtrKovalenko/odiff which could help with image diff. from what I understand odiff is much muster than other similar libraries, including the one used in this project.
It would be nice to expose an option to experimentally try odiff. What do you think?
We’re going to fix this if we can. I’ll submit a patch today if we can get to the bottom of it.
Yes. Very helpful.
There’s an option to run jest image snapshot in process.
Can you add runInProcess: true as soon of the options you pass toMatchSnapshot, and paste the next stack trace here as well?
On Wed, Jul 1, 2020, 00:33 Lukas Oppermann notifications@github.com wrote: