Skip to content
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

Random error capturing snapshot #899

Open
esetnik opened this issue Dec 28, 2024 · 8 comments
Open

Random error capturing snapshot #899

esetnik opened this issue Dec 28, 2024 · 8 comments

Comments

@esetnik
Copy link

esetnik commented Dec 28, 2024

The problem

Every now and then I will get a failure from percy saying "RequestError: Error: write EPIPE". I don't know how to reproduce it or fix it. Only happens in ~1/10 builds.

cypress-1     | [percy:sdk] [percy] Could not take DOM snapshot "snapshot name redacted (5909143)" (6254ms)
cypress-1     | [percy:sdk] [percy] RequestError: Error: write EPIPE (0ms)

Environment

  • Node version: v22.12.0
  • @percy/cli version: 1.30.4
  • Version of Percy SDK you’re using: 3.1.3
  • If needed, a build or snapshot ID: 37984291
  • OS version: linux docker
  • Type of shell command-line [interface]: sh

Details

If necessary, describe the problem you have been experiencing in more detail.

Debug logs

If you are reporting a bug, always include logs! Give the "Debugging SDKs"
document a quick read for how to gather logs

Please do not trim or edit these logs, often times there are hints in the full
logs that help debug what is going on.

Code to reproduce issue

Given the nature of testing/environment bugs, it’s best to try and isolate the
issue in a reproducible repo. This will make it much easier for us to diagnose
and fix.

@shantanuk-browserstack
Copy link

Hi @esetnik ,

Can you please check by setting the concurrency to 1 in percy.yml and gradually increasing it?

Currently, we're unsure why this is happening, and it's not reproducible on our end.

@esetnik
Copy link
Author

esetnik commented Jan 7, 2025

I can confirm it is still happening with:

discovery:
  retry: true
  concurrency: 1

@esetnik
Copy link
Author

esetnik commented Jan 7, 2025

Also tried @percy/cli@v1.30.6 and able to reproduce with that version as well.

@esetnik
Copy link
Author

esetnik commented Jan 8, 2025

I found that this is a duplicate of #451

@prklm10
Copy link
Contributor

prklm10 commented Jan 10, 2025

Hi @esetnik This type of error comes when resources are fully utilized.
Can you check your pods metrics where you are running tests and see CPU and memory usage during the percy test executions.
You can also create a support ticket and we will look into it more.

@esetnik
Copy link
Author

esetnik commented Jan 10, 2025

image

I don't think we are facing resource utilization issues.

@prklm10
Copy link
Contributor

prklm10 commented Jan 17, 2025

@esetnik can you create a support ticket on percy.

@esetnik
Copy link
Author

esetnik commented Jan 17, 2025

@esetnik can you create a support ticket on percy.

Ok, i just did.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants