-
Notifications
You must be signed in to change notification settings - Fork 96
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
increase golangci-lint timeout to avoid sporadic CircleCI failures #2320
increase golangci-lint timeout to avoid sporadic CircleCI failures #2320
Conversation
Ooof 5m for a meta-linter is pretty wild... our code isn't that big. Is there any indication which specific linter is taking ages? I've been experiencing slowness in VSCode with linting updates which are a pain when doing large refactors... curious if we know why it is so slow? |
Not really...? Here's the output of one of the relevant failures (this one had example of linter timeout log output
|
FWIW, the issue I was seeing with linting my code was that |
We recently restricted |
What's the executor size for this task in CircleCI? We should likely match concurrency to the number of CPUs that are allocated.... and then anything else is going to be turning on/off linters that are making this take ages.... or upping the timeout :-/ |
This is all it says under the
Not sure what that means in terms of CPUs allocated etc. |
Default Docker executor size in CircleCI is Medium (2 vCPUs/4GB RAM) which I believe also makes the |
Thanks EmmEff - we're only using a non-default Large for the e2e-test step. Might be time to review executor size all-round, again, at some point. |
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.
…ylabs#2320) * increase golangci-lint timeout * reduce "concurrency" value 4 -> 2
Description of the Pull Request (PR):
Increases the timeout for
golangci-lint
from3m
to5m
to avoid sporadic CircleCI failures.