Backport of Increase golangci-lint timeout to 10m into release/1.0.x #2628
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #2621 to be assessed for backporting due to the inclusion of the label backport/1.0.x.
The below text is copied from the body of the original PR.
This is meant to solve for recurrent timeouts in several steps, particularly
golangci-lint-control-plane
andgolang-ci-lint-cli
.An accompanying change in
consul-k8s-workflows
should disable caching until the (unclear) root of the issue can be resolved, or we can disable or clear cache in a more targeted way that solves for these cases.Note from @DanStough : we've also done this in
consul
#2621
hashicorp/consul#17459
Changes proposed in this PR:
golangci-lint
cachingHow I've tested this PR:
How I expect reviewers to test this PR: 👀
Checklist:
Overview of commits