Package: jenkins.debian.org Followup-For: Bug #1067232 X-Debbugs-Cc: hol...@layer-acht.org
On Wed, 20 Mar 2024 16:05:30 +0000, Holger wrote: > or maybe even simpler: first run diffoscope normally, then if that runs into > a timeout, > run with --max-container-depth=3 (or 5). I think this would be acceptable with > only 286 suite/arch/package combinations currently which run into a timeout. That seems like a straightforward way to get started, and without adding much complexity. In reproducible_build.sh it looks like there are some IRC notifications: it could make sense to suppress the retried-diffoscope-results, or emit a noticably different message for those to distinguish them from the initial attempt?
