search

actions / upload-artifact

MIT License
3.16k stars 710 forks source link

[Bug] Error: Request timeout: #423

Closed Kief5555 closed 9 months ago

Kief5555 commented 1 year ago

What happened?

I am building an app using a self hosted macOS vm on vmware. On an attempt to upload my build aritfact. The request hangs and fails. It times out. 

An error has been caught http-client index 0, retrying the upload
Error: Request timeout: /<myid>/_apis/resources/Containers/7705068?itemPath=Signtunes_1[56](https://github.com/StarfilesFileSharing/Signtunes-App/actions/runs/<id>/job/<id>#step:8:57)%2F<username>%2Factions-runner%2F_work%2FSigntunes-App%2FSigntunes-App%2Fbuild%2Fsigntunes.ipa
    at ClientRequest.<anonymous> (/Users/kieferlin/actions-runner/_work/_actions/actions/upload-artifact/v3/dist/index.js:4869:26)
    at Object.onceWrapper (node:events:641:28)
    at ClientRequest.emit (node:events:527:28)
    at TLSSocket.emitRequestTimeout (node:_http_client:771:9)
    at Object.onceWrapper (node:events:641:28)
    at TLSSocket.emit (node:events:539:35)
    at TLSSocket.Socket._onTimeout (node:net:516:8)
    at listOnTimeout (node:internal/timers:5[59](https://github.com/StarfilesFileSharing/Signtunes-App/actions/runs/5767346898/job/15636870184#step:8:60):17)
    at processTimers (node:internal/timers:502:7)

All it logs is Total file count: 1 ---- Processed file #0 (0.0%) and it keeps doing it until it eventially gives up.

What did you expect to happen?

For it to upload successfully

How can we reproduce it?

macOS ventura using vmware

Anything else we need to know?

What version of the action are you using?

v3

What are your runner environments?

self-hosted

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

No response

Kief5555 commented 1 year ago

503's also occur

konradpabjan commented 9 months ago

v4 has been released today which is a complete rewrite of v1-v3 where this error was occurring: https://github.blog/changelog/2023-12-14-github-actions-artifacts-v4-is-now-generally-available/

With v4 this no longer happens. Recommend switching over today!