-
Notifications
You must be signed in to change notification settings - Fork 53
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
Kover 0.7.1 failure at configuration time - gradleWrapper.getProperty(name) must not be null #405
Comments
Hi, Unfortunately, I couldn't reproduce this error locally, so a reproducer would help. |
Hi, I'll try to provide one 👍 |
I'm having a hard time reproducing on a smaller project. We're using a convention plugin to set up all our modules, which is hard to replicate, and I suspect this bug is caused by a lifecycle issue where we apply the Kover plugin too early compared to AGP. #362 might be related? |
@outadoc, |
No change unfortunately, same error |
Unfortunately, according to the message, it is difficult to fully understand the reason. Could you please send a full stacktrace of the error? |
@shanshin The full stack trace should be above, in the issue's description (it's collapsed by default). Thanks for your effort. I haven't been able to spend much time investigating, but i'll try to. |
I'm facing the exact same issue while migrating to 0.7.2. I'm on a different version of gradle (8.2), the rest is pretty much the same configuration |
Here are a few things that I've tried:
No luck. All leads to the following error:
|
@quanturium, it looks like the problem is related to a test task. The task |
@shanshin Thank you for the pointer. I was able to troubleshoot this by setting some breakpoints. It turns out we disable unitTest for our release build type.
Even though I'm triggering the Replace:
with:
or even better, changing |
Oh that's a very good find! We also set |
Fixes #405 A small refactoring of DynamicBean was also carried out
@quanturium, thanks for the investigation! |
Fixes #405 A small refactoring of DynamicBean was also carried out
@shanshin My pleasure. When could we expect a 0.7.3 release including this fix? |
Release is expected around next week. |
Fixed in |
Describe the bug
When upgrading Kover to 0.7.1, when running any Gradle task, we now get this error:
Errors
Full stack trace
Expected behavior
A clear and concise description of what you expected to happen.
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.
Will try to provide one if the stack trace is not enough
Reports
If applicable, report files or screenshots.
Environment
The text was updated successfully, but these errors were encountered: