-
Notifications
You must be signed in to change notification settings - Fork 12
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
ci: disable go cache for self-hosted runner #467
Conversation
Apparently self-hosted runners don't require the go caching, and for some reason it can take 20 minutes. This sets `cache: false` for actions/setup-go@v4
oh, this seems make sense, probably the docker cache is no need as well? |
I wondered about that, but really don't know. Related, I see this in the "raw logs":
I wonder if the docker buildx cache isn't working anyway? |
Not sure, I checked the latest run and I didn't see the error from the raw log. |
Re-ran CI a few times and still working. Consistently about 7 minutes. Weird that it's so slow to tar up the cache. Oh well |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Apparently self-hosted runners don't require the go caching, and for some reason it can take 20 minutes.
I saw this:
I can't explain why that should take so long on bare metal, especially the fast machine we have, but it did. Probably there is a way to tweak the compression program so it uses faster settings or perhaps an uncompressed tar, but according to discussion at actions/setup-go#431 and actions/setup-go#403 that there is no point to using the action's cache on a self-hosted runner.
Thus, this PR sets
cache: false
for actions/setup-go@v4