Konstantin Shcheglov
470c5de12e
The completion tests are fragile and too sensitive to task model changes. I have a change that inserts a new analysis result between RESOLVED_UNIT3 and RESOLVED_UNIT4, and by doing this the next task to perform resolves types in imported libraries. But in CC test we continue performing analysis tasks and incidentally resolve something what the 'null' checks don't expect. So, I think we need to stop doing these checks. If needed, we can check something directly by asking the state of some analysis results from AnalysisContext. R=jwren@google.com, danrubel@google.com BUG= Review URL: https://codereview.chromium.org/1932003002 .
analysis_server
A long-running process that provides analysis results to other tools.
The analysis server is designed to provide on-going analysis of one or more code bases as those code bases are changing.
Using the server
The analysis server is not intended to be used stand-alone, and therefore does not have a human-friendly user interface.
Clients (typically tools, such as an editor) are expected to run the analysis
server in a separate process and communicate with it using a JSON protocol. The
protocol is specified in the file analysis_server/doc/api.html.
Features and bugs
Please file feature requests and bugs at the issue tracker.