-
Notifications
You must be signed in to change notification settings - Fork 109
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
Feature request: live status on "Analyzing" #148
Comments
Hey man! I hear you, and thanks for taking the time to write in with feedback. Currently we have this stuff from bazel shushed on the theory that it created a lot of noise, and that, probably, if it was taking a long time we should be coaching people to run after builds w/ the same flags so it can hit cache for the slow header search part--to run it on faster-running subsets of their code. Does that seem reasonable/applicable, or do you definitely want more logging? I sadly don't have bandwidth for this one at the moment. Would you be interested in exploring? If so, there are two internal phases that are (sometimes) slow: (1) aquerying bazel (if v large) and (2) running header search (if can't hit cache from prior builds/runs of this tool). For (1) you could play with removing the silencing of bazel (go into the generated python and comment Thanks again, |
During
>>> Analyzing commands used in @//...
It can take quite a while before anything prints, or between things printing.It might be helpful to have a status printout at the bottom of the screen which indicates that it's still working, and how many targets/total targets.
The text was updated successfully, but these errors were encountered: