Skip to content

reportScoverage without extra JVM process #75

@dsilvasc

Description

@dsilvasc

The reportScoverage task spawns a separate JVM process. Would it be possible to run it within the gradle process?

For a gradle project with many sub-projects, spawning a JVM per subproject for test coverage reports ends up slowing down the build with the JVM startup time and with a cold JIT for each subproject report. Keeping the reporting task within the gradle process could shave about 1.5sec per subproject.

> Task :testing:reportScoverage
...
Starting process 'command '/Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/bin/java''. ... Command: /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/bin/java ... org.scoverage.SingleReportApp ...
[scoverage] Generating scoverage reports...
...
:testing:reportScoverage (Thread[Task worker for ':' Thread 3,5,main]) completed. Took 1.531 secs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions