-
Notifications
You must be signed in to change notification settings - Fork 695
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
[bug] Request failures in v4 on ECONNRESET and 403 Forbidden. #560
Comments
Can second this, have a workflow w/ ~100 jobs and it seems to fail when two or more try uploading around the same time, but that could be in my head. However the workflow never completes successfully without needing to retry failed jobs solely due to this action failing intermittently. |
Also experiencing this issue with v4. We have a workflow that runs multiple jobs which use this action and intermittently one or more of these fails because of the |
+1 Example failure (on GitHub-hosted Raw logs: job-logs.txt |
Potentially related: |
I am also seeing this issue on my self hosted ubuntu runners (sporadically) that then pass on re-run no issues after upgrading to v4 |
…acts issue GitHub artifacts v4 has intermittent issues: actions/upload-artifact#560 (comment) actions/upload-artifact#569 (comment) actions/download-artifact#338 Capture tcpdump as requested by GitHub Support
…acts issue GitHub artifacts v4 has intermittent issues: actions/upload-artifact#560 (comment) actions/upload-artifact#569 (comment) actions/download-artifact#338 Capture tcpdump as requested by GitHub Support
…acts issue GitHub artifacts v4 has intermittent issues: actions/upload-artifact#560 (comment) actions/upload-artifact#569 (comment) actions/download-artifact#338 Capture tcpdump as requested by GitHub Support
…acts issue (#229) GitHub artifacts v4 has intermittent issues: actions/upload-artifact#560 (comment) actions/upload-artifact#569 (comment) actions/download-artifact#338 Capture tcpdump as requested by GitHub Support
What happened?
Sometimes actions/upload-artifact@v4 gives errors like this one:
It feels like this is happening more since upgrading from v3.
Is the backend for v4 less stable than the one for v3?
Also, at approximately the same time, I got one of
Failed request: (403) Forbidden: Error from intermediary with HTTP status code 403 "Forbidden"
:Which is strange. Supposedly we don't have any outbound restrictions on our runner environment so I don't think this was on our side.
What did you expect to happen?
The upload should have succeeded
How can we reproduce it?
Try uploads throughout the day? It's a flaky problem.
Anything else we need to know?
No response
What version of the action are you using?
v4
What are your runner environments?
self-hosted
Are you on GitHub Enterprise Server? If so, what version?
No response
The text was updated successfully, but these errors were encountered: