diff options
-rw-r--r-- | documentation/overview-manual/concepts.rst | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/documentation/overview-manual/concepts.rst b/documentation/overview-manual/concepts.rst index 7ad21e0d7d..76e02eafff 100644 --- a/documentation/overview-manual/concepts.rst +++ b/documentation/overview-manual/concepts.rst | |||
@@ -2004,6 +2004,15 @@ task output from the Shared State cache. | |||
2004 | the stability of the task's output hash. Therefore, the effectiveness | 2004 | the stability of the task's output hash. Therefore, the effectiveness |
2005 | of Hash Equivalence strongly depends on it. | 2005 | of Hash Equivalence strongly depends on it. |
2006 | 2006 | ||
2007 | Recipes that are not reproducible may have undesired behavior if hash | ||
2008 | equivalence is enabled, since the non-reproducible diverging output maybe be | ||
2009 | remapped to an older sstate object in the cache by the server. If a recipe | ||
2010 | is non-reproducible in trivial ways, such as different timestamps, this is | ||
2011 | likely not a problem. However recipes that have more dramatic changes (such | ||
2012 | as completely different file names) will likely outright fail since the | ||
2013 | downstream sstate objects are not actually equivalent to what was just | ||
2014 | built. | ||
2015 | |||
2007 | This applies to multiple scenarios: | 2016 | This applies to multiple scenarios: |
2008 | 2017 | ||
2009 | - A "trivial" change to a recipe that doesn't impact its generated output, | 2018 | - A "trivial" change to a recipe that doesn't impact its generated output, |