Reproducibility and testing migration

Vagrant Cascadian vagrant at reproducible-builds.org
Mon Nov 16 09:14:14 GMT 2026


On 2026-11-16, Stéphane Glondu wrote:
> Le 14/11/2026 à 13:22, Holger Levsen a écrit :
>>> [1] https://reproduce.debian.net/excuses.html?source_name=eliom
>>>
>>> Wouldn't it make more sense for reproduce.debian.net to report build
>>> failures as "UNKNOWN" rather than "BAD"?
>> 
>> not really, because reproduce.debian.net is rebuilding (or is aiming to rebuilding)
>> packages which have build before. (and it's using the exact same dependencies
>> as the build on buildd.d.o used), so it should not happen that such a build does
>> not build.
> Well, it does happen.
>
> Meanwhile, eliom managed to be reproduced on loong64, but not on amd64. 
> And it seems that it doesn't always fail on the same test. And I cannot 
> reproduce the failure on my own machine; it doesn't happen on buildds 
> either.
>
> There must be something not obvious specific to the reproduce.debian.net 
> setup. I tried with nice, cpulimit, systemd-run with a CPU limit... to 
> no avail.

Not sure off the top of my head what it might be, but a list of expected
and known differences:

  https://release.debian.org/reproducible-builds-host-requirements.html


live well,
  vagrant



More information about the Reproducible-builds mailing list