-
-
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
Bazel build hangs on with 100% CPU #312
Comments
hi! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@Helcaraxan Is this still an issue with the most recent version or unreleased master branch? @jirfag Has done quite a bit of work to reduce memory usage (see: #337, #758, #764) that should help quite a bit here. |
@tpounds I have not been able to reproduce this of late and we have been running |
Summary
I've been trying out
golangci-lint
for a while in several small scale projects as well as in the setting of VSCode in a larger code-base. I am now looking to potentially start usinggolangci-lint
as the principal CI linter in that same larger code-base (currentlygometalinter
and some other ones).While trying out larger scale runs, with just a plain
golangci-lint run
and not with specific packages like VSCode provides, I have been running into a persistent issue that sees the run reaching the specified deadline (30s
or the default1m
for example). However at that point the binary does not correctly exit and leaves one of its threads running at 100% CPU indefinitely. I have actually left it running for a whole night to check if it wasn't some clean-up or anything else taking extra long due to the code-base's size. Running only a single simple linter likelll
that actually finished within the deadline does exit correctly.Even stranger, I am only seeing this occur on my Linux but not on my Mac where I don't even reach the deadline by an order of magnitude. The full data (configuration, etc) can be found below.
Last but not least, in case that might make a difference (given the recent move to use
golang.org/x/tools/go/packages
), we are using Bazel for our build systems.Data
Version of golangci-lint:
golangci-lint --version
Same on both Linux and OSX
-> golangci-lint --version golangci-lint has version v1.12.3 built from 014a924 on Wed 5 Dec 09:50:04 GMT 2018
(Date differs from official release as I built it on my local machine from the
v1.12.3
tag).Config file:
cat .golangci.yml
NB: Have removed all default settings that I tend to keep around for awareness in the file. This is the list of non-standard setting.
Go environment:
go version && go env
NOTE: In the setting of our Bazel build system we actually use a pinned Go version at
1.10
.OSX (Mojave)
Linux (Ubuntu 18.04 LTS)
Verbose output of running:
golangci-lint run -v
OSX (Mojave)
Linux (Ubuntu 18.04 LTS)
NOTE: interrupted by Ctrl+C after ~6 minutes -
htop
is showing 1 parent and 8 child processes with 1 of them at 100% CPU)The text was updated successfully, but these errors were encountered: