Florian Schneider
2a6847de41
Testing should not depend on how long it takes to get a response from the analysis server. Depending on how long an analysis step takes, these tests will randomly fail e.g. when run in -mdebug mode, or with other VM flags that change (i.e. slow-down) timing (--trace-compiler, --optimization-counter-threshold=5" There are probably more problematic places like this. I just fixed the ones that I saw failing when running with --optimization-counter-threshold=5. BUG=#26556 R=scheglov@google.com Review URL: https://codereview.chromium.org/2016993004 .
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.