-
Notifications
You must be signed in to change notification settings - Fork 38
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
Error: Cache upload failed because file read failed with EBADF: bad file descriptor, read #238
Comments
Are you running GitHub Enterprise? This looks like the sort of error that would be caused by network infrastructure blocking certain requests (or requests over a certain size). You could test a workflow using actions/cache. The |
See this issue that was due to GHES installation: #235 |
bigdaz Thank you! I have contacted our infrastructure team and am awaiting their response.
|
Is this error coming from GitHub Enterprise, or from github.com? |
Hi @bigdaz, The issues I'm facing is exactly the same as this issue report comment
Both of the scenarios are showing as warnings showing in the github annotations of summary. |
The The other messages indicate a general issue with the GitHub Actions cache. Assuming you're running GitHub Enterprise (and not using the public github.com) then this is something your infrastructure team will need to deal with. The best and simplest test is to use a workflow with |
Hi,
We have checked several discussion and reported issues but still we're getting a bunch of warnings after updating to
gradle/actions/setup-gradle@v3
. I'm wondering if any suggestions how to fix those issues properly.Setup
Added the gradle workaround.
Disable local cache regarding to the readme doc
Warnings
The text was updated successfully, but these errors were encountered: