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 668e002565..80d75dd7c3 100644 --- a/documentation/overview-manual/concepts.rst +++ b/documentation/overview-manual/concepts.rst | |||
| @@ -1963,6 +1963,15 @@ task output from the Shared State cache. | |||
| 1963 | the stability of the task's output hash. Therefore, the effectiveness | 1963 | the stability of the task's output hash. Therefore, the effectiveness |
| 1964 | of Hash Equivalence strongly depends on it. | 1964 | of Hash Equivalence strongly depends on it. |
| 1965 | 1965 | ||
| 1966 | Recipes that are not reproducible may have undesired behavior if hash | ||
| 1967 | equivalence is enabled, since the non-reproducible diverging output maybe be | ||
| 1968 | remapped to an older sstate object in the cache by the server. If a recipe | ||
| 1969 | is non-reproducible in trivial ways, such as different timestamps, this is | ||
| 1970 | likely not a problem. However recipes that have more dramatic changes (such | ||
| 1971 | as completely different file names) will likely outright fail since the | ||
| 1972 | downstream sstate objects are not actually equivalent to what was just | ||
| 1973 | built. | ||
| 1974 | |||
| 1966 | This applies to multiple scenarios: | 1975 | This applies to multiple scenarios: |
| 1967 | 1976 | ||
| 1968 | - A "trivial" change to a recipe that doesn't impact its generated output, | 1977 | - A "trivial" change to a recipe that doesn't impact its generated output, |
