anchor.diff:  |===
   
   [[sec:task_output_caching_known_issues_caveats]]
  -==== Caveats
  +===== Caveats
   
   These issues may affect the number of cache hits you get between machines.
   
  
positive.code:     api:org.gradle.api.tasks.WriteProperties[]
  
  All other tasks are currently not cacheable, but this may change in the future for other languages (Scala) or domains (native, Android, Play).
  Some tasks, like api:org.gradle.api.tasks.Copy[], usually do not make sense to make cacheable because Gradle is only copying files from one location to another.
  It also doesn't make sense to make tasks cacheable that do not produce outputs or have no task actions.
  
  [[sec:task_output_caching_inputs]]
  
negative.code: We suggest adding tests to ensure that the task inputs are relocatable, i.e. that the task can be loaded from the cache into a different build directory (see `@api:org.gradle.api.tasks.PathSensitive[]`).
  
  [[sec:task_output_caching_known_issues]]
  ==== Feedback and known issues
  
  The task output caching feature has known issues that may impact the correctness of your build when using the build cache,
  and there are some caveats to keep in mind which may reduce the number of cache hits you get between machines.
  