-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Allow running multiple instances serialy #1301
Labels
enhancement
New feature or improvement
Comments
rski
added a commit
to rski/golangci-lint
that referenced
this issue
Aug 11, 2020
By default, golangci-lint fails after five seconds if another instance is running. It is possible to disable that, but the discussion around whether the cache is safe to use concurrently is not exactly full of confidence. Add a flag that allows golangci-lint to wait forever instead of failing. see golangci#1301
daixiang0
pushed a commit
that referenced
this issue
Aug 28, 2020
By default, golangci-lint fails after five seconds if another instance is running. It is possible to disable that, but the discussion around whether the cache is safe to use concurrently is not exactly full of confidence. Add a flag that allows golangci-lint to wait forever instead of failing. see #1301
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
When golangci-lint runs, --allow-parallel-runners defaults to false, so multiple instances can't run at the same time. It's also kind of dubious whether the cache will work well on parallel runs, so I would like a middle solution where I can run multiple instances, each waiting for the lock.
Describe the solution you'd like
An
--allow-serial-runners
flag, that will remove the flock timeout, effectively waiting forever until all other instances finish.I have a change for this ready, I'm filing this first for reference/posterity
The text was updated successfully, but these errors were encountered: