Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Out of memory error when running either kover:koverHtmlReport or kover:koverVerify #566

Closed
Chrisjc28 opened this issue Mar 15, 2024 · 1 comment
Assignees
Labels
Bug Bug issue type S: untriaged Status: issue reported but unprocessed

Comments

@Chrisjc28
Copy link

Chrisjc28 commented Mar 15, 2024

Describe the bug
When running our unit tests if we run them with kover:koverHtmlReport or kover:koverVerify we are getting an out of memory error ```
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "/127.0.0.1:51537 to /127.0.0.1:51536 workers Thread 2"

This is causing the job to fail but if we run the Unit tests with these commands they all pass with flying colours.

Errors

Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "/127.0.0.1:51537 to /127.0.0.1:51536 workers Thread 2"

Expected behavior
We can run the Unit tests with the kover commands without suffering from an out of memory error.

Reproducer
A link to your project, if it is open source. Otherwise, please try to reproduce the problem on a small project.
If this is not feasible, give an example of the code on which the problem manifests itself.

Reports
If applicable, report files or screenshots.

Environment

  • Kover Gradle Plugin version: [0.7.6]
  • Gradle version: [8.3.0]
  • Kotlin project type: [Kotlin/Android]
  • Coverage Toolset (if customized in build script): [Kover]
  • Other context important for this bug: [N/A]
@Chrisjc28 Chrisjc28 added Bug Bug issue type S: untriaged Status: issue reported but unprocessed labels Mar 15, 2024
@imcmib
Copy link

imcmib commented Apr 17, 2024

@Chrisjc28 I faced same issue. Did you manage to fix it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Bug issue type S: untriaged Status: issue reported but unprocessed
Projects
None yet
Development

No branches or pull requests

3 participants