<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Thu, Jan 9, 2025, at 02:28, James Addison via rb-general wrote:<br></div><blockquote type="cite" id="qt" style=""><div>are there any<br></div><div>recommendations about whether SOURCE_DATE_EPOCH must-not / can /<br></div><div>should / must be configured during (immediate and/or later) testing of<br></div><div>software that has been built reproducibly? And if so, for what<br></div><div>reason(s)?<br></div></blockquote><div><br></div><div>I think generally tests should succeed whether or not SOURCE_DATE_EPOCH was set beforehand.<br></div><div><br></div><div>If a program is intended to have different behavior based on whether or not SOURCE_DATE_EPOCH is set, the test should either allow both behaviors, or make sure SOURCE_DATE_EPOCH is set or not during the test setup.<br></div><div><br></div><div>I can definitely see projects choosing to set SOURCE_DATE_EPOCH when running their tests (nice and predictable, and many build systems don't neatly distinguish between the 'build' and 'test' parts of the build). On the other hand, it can also be valuable to run tests without SOURCE_DATE_EPOCH being set (as that is potentially more consistent with how 'real' users will be running the software). The latter might not be so true for 'development' tools like sphinx, though.<br></div><div><br></div><div><br></div><div>Kind regards,<br></div><div><br></div><div id="sig124436424"><div class="signature">-- <br></div><div class="signature">Arnout Engelen<br></div><div class="signature">Engelen Open Source<br></div><div class="signature"><a href="https://engelen.eu">https://engelen.eu</a><br></div></div><div><br></div></body></html>