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: 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.
  
negative.code: NOTE: When https://github.com/gradle/gradle/issues/new?labels=in:build-cache[reporting issues with the build cache], please check if your issue is a known issue or related to a known issue.
  
  [[sec:task_output_caching_known_issues_correctness]]
  ==== Correctness issues
  
  These issues may affect the correctness of your build when using the build cache. Please consider these issues carefully.
  
  