Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes: > I think the config.cache of lorikeet needs to be cleaned, because the > return type of strerror_r() has changed as a result of this commit, but > the build farm logs still show the old test result being used from the > cache.
lorikeet's latest build run appears to have been done without config cache, and it succeeded, so your guess was correct.
Next question is why the buildfarm client got that wrong. Seems like its accache logic needs to notice changes in src/template/* as well as the configure script proper.
The problem with that is that a change in one template will cause the cache to be invalidated for every buildfarm member. Maybe that doesn't matter too much - after all we used not to keep the cache at all.
