-
Notifications
You must be signed in to change notification settings - Fork 2
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
Support Gradle configuration cache #159
Comments
Corresponding E2E test: skippy-io/skippy-regression-suite#2 |
Quick update: All E2E test except TestFailureTest.java pass with Configuration Cache enabled using the changes in #160 . I'm still investigating why the result property for a failed test is set incorrectly with Configuration Cache enabled. |
My best guess is that it's somehow related to not having the class-dirs as inputs, so Gradle doesn't realize the task is stale (due to classpath changing), and the task is not re-run as a result. Simply adding |
I added some logging. From what I can tell, it's not due to tasks not being executed. What I see: |
I will create a minimal project that demonstrates my problem and reach out to the Gradle folks for help. |
FYI: https://discuss.gradle.org/t/sharing-objects-across-taks-with-configuration-cache-enabled/48598 |
Accidentally closed this issue when squashing the PR. Have to add additional tests and figure out how to solve that for Gradle 7. @Kantis What version of Gradle are you using? This should be fixed in 0.0.21-SNAPSHOT if you use Gradle 8 or above. |
@fmck3516 Amazing work with this tool. However I have a question, how do I use the snapshot version? I'm currently running some experiments with skippy and will like to test out the gradle cache fix before proceeding. The project uses gradle 8.5 |
You can use snapshot versions as follows:
|
This has been fixed in release 0.0.22 which has been published to Maven Central and Gradle's Plugin Portal. PRs: |
Running
SkippyAnalyze
task in a project which uses Gradle's configuration cache yields the following error:The text was updated successfully, but these errors were encountered: