anchor.diff:  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
  +===== Correctness Issues
   
   These issues may affect the correctness of your build when using the build cache. Please consider these issues carefully.
   
  
positive.code: ============================================
  
  [[sec:task_output_caching_known_issues]]
  ==== Feedback and Known issues
  
  The task output caching feature has known issues that may impact the correctness, usability and performance of your build when using the build cache.
  These issues will be corrected as this feature becomes stable.
  
negative.code: and `jar` being Copy-like tasks which are not cacheable since it is generally faster to execute them.
  
  [[sec:task_output_caching_details]]
  ==== Task Output Caching in Detail
  
  Since a task describes all of its inputs and outputs, Gradle can compute a _build cache key_ that uniquely defines the task's outputs based on its inputs.
  That build cache key is used to request previous outputs from a build cache or push new outputs to the build cache. If the previous build is already populated by someone else, e.g. your
  