anchor.diff:  
   Upon failure to serialize the state required to run the tasks, an HTML report of detected problems is generated.
   The Gradle failure output includes a clickable link to the report.
  -This report is useful and allows to drill down into problems, understand what is causing them.
  +This report is useful and allows you to drill down into problems, understand what is causing them.
   
   Let's look at a simple example build script that contains a couple problems:
   
  
positive.code: ----
  
  The previous configuration cache entry could not be reused, and the task graph had to be calculated again.
  This is because we read the system property at configuration time, hence requiring to run the configuration phase again when the value of that property changes.
  Fixing that is as simple as wiring the system property directly, without reading it at configuration time.
  
  ====
  
negative.code: Details can be found in the linked HTML report.
  The report displays the set of problems twice.
  First grouped by problem message, then grouped by task.
  The former allows you to quickly see what classes of problems your build is facing.
  The latter allows you to quickly see which tasks are problematic.
  In both cases you can expand the tree in order to discover where the culprit is in the object graph.
  
  [TIP]
  ====
  