> > You might want to ensure (as maintainer of Salsa CI) that such thing > > does not happen (or, at the very minimum, document the differences > > between a completely clean chroot and the one used by Salsa CI). > > Simple question: Does it help if I open an issue in Salsa CI for that?
Thanks Santiago for quick reply. Your theory might be correct, but please note the issue didn't reproduce on Launchpad builders either, see https://launchpadlibrarian.net/773490787/buildlog_ubuntu-plucky-amd64.golang-github-caarlos0-env_11.3.1-1~bpo25.04.1~1738188869.de7bd9d+debian.latest_BUILDING.txt.gz Can you describe how you did your test builds, maybe I can try to replicate the exact situation and reproduce the issue? Or maybe the issue is sporadic, or maybe it requires the host to have a specific time zone or something?
