When the configuration cache is enabled, the cache entry is always immediately invalidated after the first run
Errors
If present, stacktraces or files from build/kover/errors directory
Expected behavior
After invoking a command once, the configuration cache from the previous invocation should be reused
Reproducer
By applying the following patch to the project you can see that the configuration cache is not used in the first identical run because the test assertion fails
In the output of this run you can see the following message
Calculating task graph as configuration cache cannot be reused because the file system entry 'build/kover/.artifact' has been created.
If you run the build three times, on the third attempt the configuration cache will be re-used, if you apply the patch below the test passes, but it should already be available after the first attempt.
Describe the bug
When the configuration cache is enabled, the cache entry is always immediately invalidated after the first run
Errors If present, stacktraces or files from
build/kover/errors
directoryExpected behavior
After invoking a command once, the configuration cache from the previous invocation should be reused
Reproducer
By applying the following patch to the project you can see that the configuration cache is not used in the first identical run because the test assertion fails
In the output of this run you can see the following message
If you run the build three times, on the third attempt the configuration cache will be re-used, if you apply the patch below the test passes, but it should already be available after the first attempt.
Environment