Can you generate a thread dump of the gradle process (or daemon process if you're using it) which shows what lint is doing?
(jps to get the pid's of the java processes, jstack <pid> to get a thread dump from the process). -- Tor On Fri, Dec 20, 2013 at 8:57 AM, Alex Baker <[email protected]> wrote: > I noticed a problem when my travis build started to time out after > updating to gradle 1.9 + plugin 0.7.1. My project [github > link<https://github.com/abaker/tasks>] is > composed of three modules, android-aac-enc, api, and astrid, and running > lint from the command line only takes a few seconds for each. The gradle > lint task is running slow for the two library modules (android-aac-enc, > api) and I killed it after letting it run overnight on the main module > (astrid). > > It pegs one cpu and memory usage fluctuates between one and two GB. I > messed with a few lintOptions to no avail. Adding the debug flag to gradle > doesn't provide any additional lint output. > > -- > You received this message because you are subscribed to the Google Groups > "adt-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
