-
Notifications
You must be signed in to change notification settings - Fork 669
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] v4.3.1: Unexpected token '<', "<!DOCTYPE "... is not valid JSON #543
Comments
For reference: keycloak/keycloak#27692 |
same issue here |
I also just encountered this issue with this workflow run: https://github.com/nlnwa/warchaeology/actions/runs/8449566338/job/23143911184#step:11:14 The relevant part of the log is:
|
Same issue here. We have recently migrated to v4.3.1 |
It seems the bump in the @actions/artifacts npm dependency in v4.3.1 of actions/upload-artifact has introduced a flaky error in the back end communication: actions/upload-artifact#543 Downgrade to v4.3.0 to avoid this.
We upgraded the upload-artifacts action in our workflows to v4.3.3 about 3 weeks ago and have not seen any issue with the upload until today, then we see the issue again.
|
If that can be of any help, we ended up wrapping the download action in a composite action like this:
Basically if it fails to upload the first time, it will retry again. It's not a real solution, ideally the To use it:
|
@markmssd We have seen this issue in our builds a few more times since last week, so I'm going to add the wrapper like you did. Thank you for your advice! |
What happened?
Intermittent failures when uploading artifacts using
uses: actions/upload-artifact@5d5d22a31266ced268874388b861e4b58bb5c2f3 #version 4.3.1
The errors we have seen (in different builds):
What did you expect to happen?
Successful upload of artifacts
How can we reproduce it?
Not sure, these are intermittent errors for us, seen only a couple of times since we started using v4 about 2 weeks ago. The workflows in our project do a few hundreds of similar uploads per day, most of the time without problem.
Anything else we need to know?
The artifacts that were failed to be uploaded were just a couple of small files.
What version of the action are you using?
version 4.3.1
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: