You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
don’t register properties as inputs if they don’t affect the output
As the pitest history file doesn't affect the results of mutation analysis, the properties historyInputLocation, defaultFileForHistoryData and historyOutputLocation should not be added to inputs/outputs of PitestTask, but should instead be treated like internal task properties.
This is important e.g. when sharing history files across builds: currently the PitestTask is considered to be out-of-date even when only the history file changed since the last successful run (e.g. because a new history file was provided by another build). Thus, mutation analysis is executed but the results will of course always be the same.
The text was updated successfully, but these errors were encountered:
This blocks us from integrating history support in our CI pipeline as history file handling depends on whether this will be fixed in the pitest-plugin. Otherwise we have to implement a workaround.
This is really a pain as it increases build times of CI builds by hours for no reason.
If it helps, I can provide a PR, but I don't want to make the effort unless you're really interested. Unfortunately I've seen that this projects seems to be inactive for a while?
The gradle docs on incremental builds say
As the pitest history file doesn't affect the results of mutation analysis, the properties
historyInputLocation
,defaultFileForHistoryData
andhistoryOutputLocation
should not be added to inputs/outputs ofPitestTask
, but should instead be treated like internal task properties.This is important e.g. when sharing history files across builds: currently the PitestTask is considered to be out-of-date even when only the history file changed since the last successful run (e.g. because a new history file was provided by another build). Thus, mutation analysis is executed but the results will of course always be the same.
The text was updated successfully, but these errors were encountered: