-
Notifications
You must be signed in to change notification settings - Fork 750
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
500 errors when attempting to upload artifacts #84
Comments
@konradpabjan I believe this was due to some special characters being included in the |
What were the characters that you had to sanitize @agrobbin? Any invalid characters should be caught beforehand 🤔https://github.com/actions/toolkit/blob/9ba7c679ad74f6a80017feeb94b7a7c19b590796/packages/artifact/src/internal/utils.ts#L271 I've managed to repo this 500 randomly (caused by some timeouts behind the scenes). We currently don't retry 500s during upload so I was planning on doing some back-end updates so that 503s (which do get retried) get returned so the upload doesn't fail. |
Here is the full path (not scrubbed at all as nothing is private):
|
Also seeing a lot of those 500. We have 3 compilers x 3 OS jobs (so 9 total) and every other push we see at least one of them fail, which forces us to re-trigger the whole build. Re-triggers can be even more flakey, and I've found that removing the artifacts before re-triggering (our artifacts are pretty big) seems to help. See e.g. https://github.com/bpfkorea/agora/runs/712332960?check_suite_focus=true (but ignore the last failure on |
+1 here: https://github.com/Gallopsled/pwntools/pull/1570/checks?check_run_id=754787700 |
We've done some work behind the scenes to address users hitting 500s during artifact upload. In most cases they were caused by timeouts. If there was a timeout in the backend, a 503 should now be returned and the action will retry the upload. If there are any more instances of 500s being hit, please ping me or create a new issue |
|
|
|
Uploading github-actions artifacts is extremely flaky. Just look at actions/upload-artifact#84 (comment) (Note the many +1 on the issue even after the issue has been closed.). This tries to make sure that the test isn't marked as failure because archiving the artifacts failed on some files. pr-link: #12328 change-id: cid-72f6694761bfc3a88a62ca0422deee116779e6be
Uploading github-actions artifacts is extremely flaky. Just look at actions/upload-artifact#84 (comment) (Note the many +1 on the issue even after the issue has been closed.). This tries to make sure that the test isn't marked as failure because archiving the artifacts failed on some files. pr-link: #12328 change-id: cid-72f6694761bfc3a88a62ca0422deee116779e6be
|
I'm seeing a similar thing on the latest version (I'm assuming, since we're using
(Redacted for privacy.) |
We have started getting semi-frequent 500 errors when attempting to upload artifacts after a failed test run:
I'm unable to determine the cause, but it is pretty frequent (though I wouldn't say constant). I wish I had more debug information to provide, but there's not much else in the debug output.
Version
Environment
Pulling this out of #71 into its own issue, as @konradpabjan requested!
The text was updated successfully, but these errors were encountered: