-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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/gha: disable double caching #3822
Conversation
@thaJeztah PTAL |
~/go/pkg/mod | ||
~/.cache/go-build | ||
key: ${{ runner.os }}-go.sum-${{ hashFiles('**/go.sum') }} | ||
restore-keys: ${{ runner.os }}-go.sum- |
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.
The issue with CGO caching was resolved?
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.
It is irrelevant to this PR for two reasons:
- We remove own caching here, which is sort of orthogonal to that issue
- We only validate the dependencies here, and the issue (cache key do not include linux distro name and version actions/setup-go#368; which is not yet fixed) only surfaces when we use different distros at the same time (which we don't do here).
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.
(and when we use different distros at the same time and are affected, we disable caching:
runc/.github/workflows/test.yml
Line 70 in 2685116
cache: false # https://github.com/actions/setup-go/issues/368 |
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 (if the issue with CGO is resolved)
Since commit e3cf217 actions/setup-go@v4 uses caching implicitly, so it is no longer required. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Since commit e3cf217 actions/setup-go@v4 uses caching implicitly, and olangci/golangci-lint-action also uses caching. These two caches clash, resulting in multiple warnings in CI logs. The official golangci-lint-action solution is to disable caching for setup-go job (see [1]). Do the same. [1] golangci/golangci-lint-action#704 Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Since commit e3cf217 (#3771) actions/setup-go@v4 uses caching implicitly.
Fix two cases of double caching.