Open judson-firebolt opened 7 months ago
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 Failed to FinalizeArtifact: Unable to make request
error.
+1
Example failure (on GitHub-hosted ubuntu-latest
runner): https://github.com/canonical/pgbouncer-k8s-operator/actions/runs/9557337019/job/26344437669
Raw logs: job-logs.txt
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
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