-
Notifications
You must be signed in to change notification settings - Fork 198
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
[v4] Error: Write EPIPE #1280
Comments
Same here, I actually created an issue a few seconds after you 😄 |
@rohan-at-sentry can you help @thomasrockhu-codecov get this investigated and resolved? Sound potentially CLI-related. |
I am also experiencing this error on my mono-repo, let me know what I can do to help investigate |
@houserx-jmcc can you share a link to CI where this is failing? or the config file specifying the os and hardware? |
@thomasrockhu-codecov We can't provide a link as it is an internal/private repository, but we are using the vanilla image from actions-runner-controller for self-hosting GitHub runners on AWS EKS. |
Intermittent issues from codecov/codecov-action#1280
Is this no longer being actively worked on? |
@houserx-jmcc no it is, sorry I was doing some cleanup on my side |
there is a bug in the action since february which is resulting in intermittently failing builds. this issue introduced in 730679b, which upgraded the codecov action. references: GH codecov/codecov-action#1280
@houserx-jmcc sorry for the delay here. I implemented retries and wanted to see if this will work for you. In your CI, would you be able to replace the action with
|
2 days without seeing the error using this version. I'll report back if we see it, but assume no news is good news otherwise. |
there is a bug in the action since february which is resulting in intermittently failing builds. this issue introduced in 730679b, which upgraded the codecov action. references: GH codecov/codecov-action#1280
My colleague Alberto spotted one error today, happening on our public repo:
|
Got it @houserx-jmcc @Jolg42, to be clear this not an always thing (for reproducibility)? |
@thomasrockhu-codecov correct, only happening sometimes. 1-2 retries of the same job in a workflow will usually succeed if the first time failed. |
@houserx-jmcc got it, yeah, let me work on implementing retries for this |
@thomasrockhu-codecov It's flaky, only happens once in a while and retrying usually works but since retrying means a human needs to retry and then wait, it's sub-otimal. An automatic retry would be much better for this. |
Also adds `if: success() && github.repository == 'prisma/prisma'` everywhere (only added to one before) See codecov/codecov-action#1280
@houserx-jmcc would you be able to try |
It seems a bit less frequent, but the issue is still occurring. Example output from
|
@houserx-jmcc blast. I'll keep on noodling |
Hi all, I think this should be solved in |
When switching from a working v3 setup to the new v4, we encounter this error 10-20% of the time in a high volume monorepo. Re-runs succeed on the 2nd or 3rd try. We do host our own GitHub runners.
Also a quick shoutout for #926 - if we had builtin retries this would be much less of a problem.
The text was updated successfully, but these errors were encountered: