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

Running ./gradlew clean test fails with Gradle 8.12 #721

Closed
ShindongLee opened this issue Dec 31, 2024 · 4 comments · Fixed by #722
Closed

Running ./gradlew clean test fails with Gradle 8.12 #721

ShindongLee opened this issue Dec 31, 2024 · 4 comments · Fixed by #722
Assignees
Labels
Bug Bug issue type S: ready for release Status: merged in the main branch

Comments

@ShindongLee
Copy link

Describe the bug
With Gradle 8.12, running

./gradlew clean test

fails with the following error:

java.io.FileNotFoundException: /path/to/module/build/tmp/test/kover-agent.args (No such file or directory)

It works with Gradle 8.11 or by running ./gradlew clean or ./gradlew test separately in Gradle 8.12.

Errors

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ‘:utils:test’.
> java.io.FileNotFoundException: /path/to/module/build/tmp/test/kover-agent.args (No such file or directory)

Expected behavior
./gradlew clean test should work successfully in Gradle 8.12.

Reproducer
run ./gradlew clean test with Gradle 8.12 in Kotlin/JVM multi-module projects.

Reports
If applicable, report files or screenshots.

Environment

  • Kover Gradle Plugin version: 0.9.0, 0.8.3
  • Gradle version: 8.12
  • Kotlin project type: Kotlin/JVM multimodule
  • Coverage Toolset (if customized in build script): kover
  • Other context important for this bug: Mac, Linux
@ShindongLee ShindongLee added Bug Bug issue type S: untriaged Status: issue reported but unprocessed labels Dec 31, 2024
@shanshin shanshin added S: in progress Status: implementing or design in process and removed S: untriaged Status: issue reported but unprocessed labels Jan 2, 2025
shanshin added a commit that referenced this issue Jan 6, 2025
Previously parent directory hasn't been creating for an arguments file

Fixes #721
@shanshin shanshin reopened this Jan 6, 2025
@shanshin shanshin added S: ready for release Status: merged in the main branch and removed S: in progress Status: implementing or design in process labels Jan 6, 2025
@mudasar187
Copy link

mudasar187 commented Jan 7, 2025

Is this issue been resolved? I get the same issue when running ./gradlew clean build shadowJar. But if i run ./gradlew clean and then ./gradlew build shadowJar it works.

I also get following problem report

    - [warn]  Calling configuration method 'attributes(Action)' is deprecated for configuration 'kover', which has permitted usage(s): Declarable - this configuration can have dependencies added to it This method is only meant to be called on configurations which allow the (non-deprecated) usage(s): 'Consumable, Resolvable'. This behavior has been deprecated.`org.jetbrains.kotlinx.kover`
This behavior is scheduled to be removed in Gradle 9.0.
Calling configuration method 'attributes(Action)' is deprecated for configuration 'kover', which has permitted usage(s): Declarable - this configuration can have dependencies added to it This method is only meant to be called on configurations which allow the (non-deprecated) usage(s): 'Consumable, Resolvable'. This behavior has been deprecated.

Kover Gradle Plugin version: 0.9.0
Gradle version: 8.12

@shanshin
Copy link
Collaborator

shanshin commented Jan 7, 2025

@mudasar187 , it's resolved but not released yet.

Fix for #716 is also ready to release.

@mudasar187
Copy link

@mudasar187 , it's resolved but not released yet.

Fix for #716 is also ready to release.

Thank you! I have severeal projects waiting for upgrade :) And again, thank you! keep ut the good work!

@shanshin
Copy link
Collaborator

shanshin commented Jan 8, 2025

Fixed in 0.9.1

@shanshin shanshin closed this as completed Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Bug issue type S: ready for release Status: merged in the main branch
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants