High RAM usage for app:koverXmlReport command in multi-module Android project on Azure CI

[CazimirRoman]

We are using Kover in a multi-module Android project written in Kotlin and running our CI on Azure. We've observed a significant increase in RAM usage when running the app:koverXmlReport command. The CI is currently showing a peak RAM usage of 24GB, which is approximately 10GB higher compared to when we don't run the Kover report generation.

We have already attempted to exclude specific classes that are not relevant for code coverage analysis, but the RAM consumption remains the same.

Has anyone experienced similar high RAM usage with app:koverXmlReport in multi-module Android projects?

• What are some potential causes for this high memory consumption?

• What strategies can we use to reduce the RAM usage of the app:koverXmlReport command?

• Are there any specific configurations or optimizations within Kover that can be applied to address this issue?

Any guidance or suggestions would be greatly appreciated. Thank you!

[shanshin]

Hi, could you please specify which command is running koverXmlReport? What does the Gradle command look like?
like gradlew koverXmlReport or gradlew :app:koverXmlReport

[CazimirRoman]

We are running it like this tasks: ./gradlew clean assembleDebug app:koverXmlReport

[shanshin]

Do you have any observations at what stage exactly is the peak of memory consumption?

The fact is that the app:koverXmlReport command runs the building of all build variants in all modules, and then calls all unit tests for them (both for release and debug).

Also, please double-check that the koverXmlReport (without a colon) command is not accidentally called anywhere. This causes the generation of a local report for each module, which, due to specific of Gradle, may increase memory consumption.