-
Notifications
You must be signed in to change notification settings - Fork 57
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
pitest build cache not working if the absolute path changes #314
Milestone
Comments
SidB3
changed the title
pitest task is rerun with same task inputs if the absolute file path of the project changes
pitest build cache not working if the absolute path changes
Aug 3, 2022
|
I don't know a whole lot about gradle plugins, but it seems these two methods/properties are not in use? I managed to get things working by simply removing them. |
@C-Otto Looking at the field level, there is:
And gradle/gradle#12351 seems to be still open, so @SidB3 change in #315 seems to be more accurate. |
Implemented in #315 and available in 1.9.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce:
This causes CI builds to rerun pitest for every build when there are no code updates
Additional information:
Gradle version - 7.5
Attaching sample project to run the pitest task
sample_building_java_applications-kotlin-dsl.zip
Running from two different folders produces two different cache keys
From my cursory knowledge of gradle plugin development, I see no issues in the PitestTask.groovy file. All file properties are annotated with
@PathSensitive(PathSensitivity.RELATIVE)
The text was updated successfully, but these errors were encountered: