-
Notifications
You must be signed in to change notification settings - Fork 52
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
[0.7.4] Cannot access input property externalReports$kover_gradle_plugin
of task
#478
Comments
externalReports$kover_gradle_plugin
of task
externalReports$kover_gradle_plugin
of taskexternalReports$kover_gradle_plugin
of task
Hi, It is not possible to reproduce this problem locally, so a small project producer would really help us (if anyone encounters this error on a small open source project). |
@shanshin we have the same issue. It appeared only when bumping to version |
We have the same exact issue. Also, we noticed that |
There are a lot of tests on the build cache, but only this one fell (it was unstable before), besides, it fell before using the cache. |
@guerrerorodrigo, is it reproduced only on CI or also locally?
|
@shanshin Weirdly it fails both locally. (reproduced across multiple machines) and on our CI but with different errors: CI:
ℹ️ (the file path is exactly how it's being printed on our CI logs) Locally:
🤷🏻 |
@HarisHoulis, if I publish a special version with advanced logging, could you run this version locally to test multiple versions? There is an assumption that random files fall into the list of Kover artifacts, which Kover tries to read as a text file and parse file names from there. |
@shanshin got the same error when upgrading from
|
@HarisHoulis, @wezley98 , @sureshg |
@shanshin Can you please provide me a secure way to share our |
@HarisHoulis, by e-mail sergey.shanshin@jetbrains.com You may also replace all sensitive names: so that the same substituted name corresponds to the same source directory name. |
@shanshin Exactly same issue but with 0.7.3 and only happens when using On CI fails with (ubuntu-22.04)
Locally fails with (macOS Sonoma)
Tried to bump kover to 0.7.4. Same error on CI. Now local fails with
|
@HarisHoulis, thanks for the files! @sureshg, thanks for the project! I will try to reproduce locally if the problem still repeats! |
Hello, I have also the issue with Kover 0.7.4, both locally and on the CI.
The project is open source, here is the PR: element-hq/element-x-android#1782 And the CI build https://github.com/vector-im/element-x-android/actions/runs/6815987723/job/18536289873?pr=1782 If I use Kover 0.7.3, this error is not observed (but I have other issue I am working on right now). |
Exactly the same error on my side and it is raised only with a mix of JVM and Android reports with the |
@bmarty, thanks for the reproducer! |
Finally, I think I've found the reason. The reason is that in some cases, when there is a merge of subprojects in which there are no overlapping variants (e.g. default variant, and Android build variant), a this error appears. Unfortunately, so far I have not found a completely correct solution using Gradle, and I have created related Gradle issue: gradle/gradle#27019 I'll try to get rid of the fall by workarounds, however, the primary issue is in the configuration of the build.
also in docs |
If an artifact that completely matches the attributes is not found in the dependency, then a random artifact is taken, the processing of which can lead to unpredictable errors. An additional check of the dependency resolution is needed to exclude such a situation. Fixes #478
Fixed in Now, in case of an incorrect Kover configuration, a more meaningful message is thrown out. |
Describe the bug
Upgrade from 0.7.3 -> 0.7.4 (0.7.3 works as expected with no errors)
Errors
Cannot access input property 'externalReports$kover_gradle_plugin' of task ':kover:koverHtmlReportDebug'. Accessing unreadable inputs or outputs is not supported. Declare the task as untracked by using Task.doNotTrackState(). For more information, please refer to https://docs.gradle.org/8.4/userguide/incremental_build.html#disable-state-tracking in the Gradle documentation.
Expected behavior
Build passes with no errors
Environment
The text was updated successfully, but these errors were encountered: