-
Notifications
You must be signed in to change notification settings - Fork 776
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] actions/upload-artifact@v4 often fails, but can succeed after trying again #642
Comments
Please let us know if this is still occurring, and if it still does, could you please try with
|
I haven't encountered it in the past few weeks, if I encounter it in the future, I will add it again. |
Also, I would like to ask you, what is the specific meaning of this parameter |
It sets the concurrency value in this call: https://learn.microsoft.com/en-us/javascript/api/@azure/storage-blob/blockblobclient?view=azure-node-latest#@azure-storage-blob-blockblobclient-uploadstream |
Okay, thanks! |
What happened?
In spark, we often find that
actions/upload-artifact@v4
fails, but after trying again, it will basically succeed. Do we have anyparameters
orapproaches
to avoid this situation? Because the first step in the job may take a long time to execute, and retry is for the entire job, which wastes resources and time.https://github.com/panbingkun/spark/actions/runs/11733712912/job/32688556735
What did you expect to happen?
Automatic retry or approaches that can increase the probability of success.
How can we reproduce it?
Occasionally, it occurs, but recently the probability of it happening is very high. I personally have encountered it once every 2-3 days.
Anything else we need to know?
No response
What version of the action are you using?
v4
What are your runner environments?
linux
Are you on GitHub Enterprise Server? If so, what version?
No response
The text was updated successfully, but these errors were encountered: