Skip to content

Fix golangci-lint CI cache restore failure and bump timeout - #98

Merged
ljkiraly merged 1 commit into
mainfrom
fix-golangci-lint-cache-timeout
Sep 1, 2026
Merged

ljkiraly merged 1 commit into
mainfrom
fix-golangci-lint-cache-timeout

Conversation

@ljkiraly

@ljkiraly ljkiraly commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

The reusable golangci-lint workflow intermittently failed when the golangci-lint-action cache restore errored out ("Cache service responded with 400" and a tar extraction conflict on the Go toolchain files), leaving the runner to be killed before the lint completed.

Disable the action's internal cache (skip-cache) and add an explicit "go clean -cache -modcache" step to avoid restoring a stale/corrupted cache. Also increase the lint timeout from 3m to 5m to give cache-cold runs enough headroom, since the CLI --timeout flag overrides the value in each repo's .golangci.yml.

Assisted-by: Kiro (AI assistant)

The reusable golangci-lint workflow intermittently failed when the
golangci-lint-action cache restore errored out ("Cache service responded
with 400" and a tar extraction conflict on the Go toolchain files),
leaving the runner to be killed before the lint completed.

Disable the action's internal cache (skip-cache) and add an explicit
"go clean -cache -modcache" step to avoid restoring a stale/corrupted
cache. Also increase the lint timeout from 3m to 5m to give cache-cold
runs enough headroom, since the CLI --timeout flag overrides the value
in each repo's .golangci.yml.

Assisted-by: Kiro (AI assistant)
Signed-off-by: Laszlo Kiraly <laszlo.kiraly@est.tech>
@ljkiraly
ljkiraly merged commit 653c5dd into main Sep 1, 2026
2 checks passed
@ljkiraly
ljkiraly deleted the fix-golangci-lint-cache-timeout branch September 1, 2026 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant