upload-artifact icon indicating copy to clipboard operation
upload-artifact copied to clipboard

[bug] Failed to CreateArtifact: Failed to make request after 5 attempts: Request timeout

Open lukaszcl opened this issue 1 year ago • 12 comments

What happened?

I'm seeing random failures in Github Actions when trying to upload artifacts:

2024-05-21T02:14:34.9725770Z With the provided path, there will be 9 files uploaded
2024-05-21T02:14:34.9727364Z Artifact name is valid!
2024-05-21T02:14:34.9728185Z Root directory input is valid!
2024-05-21T02:14:40.0221024Z Attempt 1 of 5 failed with error: Request timeout: /twirp/github.actions.results.api.v1.ArtifactService/CreateArtifact. Retrying request in 3000 ms...
2024-05-21T02:14:48.0300611Z Attempt 2 of 5 failed with error: Request timeout: /twirp/github.actions.results.api.v1.ArtifactService/CreateArtifact. Retrying request in 4541 ms...
2024-05-21T02:14:57.5783685Z Attempt 3 of 5 failed with error: Request timeout: /twirp/github.actions.results.api.v1.ArtifactService/CreateArtifact. Retrying request in 7858 ms...
2024-05-21T02:15:10.4508466Z Attempt 4 of 5 failed with error: Request timeout: /twirp/github.actions.results.api.v1.ArtifactService/CreateArtifact. Retrying request in 11672 ms...
2024-05-21T02:15:27.1556076Z ##[error]Failed to CreateArtifact: Failed to make request after 5 attempts: Request timeout: /twirp/github.actions.results.api.v1.ArtifactService/CreateArtifact

Happened multiple times in the last week. I'm using ubuntu-latest runner. Example: https://github.com/smartcontractkit/chainlink/actions/runs/9167647126/job/25205269179

What did you expect to happen?

Artifacts should be successfully uploaded.

How can we reproduce it?

This is an issue that happens randomly

Anything else we need to know?

No response

What version of the action are you using?

v4.3.3

What are your runner environments?

linux

Are you on GitHub Enterprise Server? If so, what version?

No response

lukaszcl avatar May 21 '24 13:05 lukaszcl

Also seeing this, for example: https://github.com/canonical/postgresql-k8s-operator/actions/runs/9638014269/job/26578262353#step:22:16

Also seeing this on download-artifact: https://github.com/actions/download-artifact/issues/338

We're using the latest version of actions/upload-artifact and we're using ubuntu-latest runners (hosted by GitHub, we have no control over networking)

https://www.githubstatus.com/history shows no incidents when we encountered this issue

carlcsaposs-canonical avatar Jun 25 '24 11:06 carlcsaposs-canonical

I met the same issue on actions/upload-artifact@v4 image

trihoang1 avatar Aug 02 '24 02:08 trihoang1

I'm seeing this issue right now over at: https://github.com/forcedotcom/sfdx-scanner/actions/runs/10216682015/job/28268718086#step:11:19

--- Rerunning my workflow worked. So this seemed to just be a blip of sorts. https://github.com/forcedotcom/sfdx-scanner/actions/runs/10216830278

stephen-carter-at-sf avatar Aug 02 '24 13:08 stephen-carter-at-sf

I'm also seeing this frequently on v4, e.g. this run. It usually succeeds on retry. Is there any plan to have more robust retries in this action?

zanieb avatar Oct 02 '24 21:10 zanieb

For my reference, I hit this today: https://github.com/orgs/community/discussions/143089

jsoref avatar Oct 30 '24 14:10 jsoref

Same happening to me at the moment:

image

marcodicro-dp avatar Nov 14 '24 14:11 marcodicro-dp

yep same here. could someone please take a look?

momentmaker avatar Nov 14 '24 15:11 momentmaker

same in my case. Atleast please don't deprecate v3

rwader-swi avatar Nov 19 '24 09:11 rwader-swi

GitHub support is notifying that the workaround is to use v3 while they resolve problems with v4 as a high priority.

GitHub has also notified here that v3 (the only viable workaround) will be experiencing scheduled brownouts during January 2025, leading up to the shut-down of v3 as of January 30th 2025.

connorhsm avatar Nov 26 '24 01:11 connorhsm

same in my case. Atleast please don't deprecate v3

You could downgrade to actions/[email protected]. This version works pretty well.

trihoang1 avatar Nov 27 '24 03:11 trihoang1

observe same today , first is gets a timeout  and then hangs hours

Image

ykhrustalev avatar Jan 29 '25 16:01 ykhrustalev

this issue keeps appearing randomly Is there a way to fix this? tried rerunning the job but keeps failing

pen-pal avatar Sep 06 '25 15:09 pen-pal