On Mon, Sep 11, 2017 at 04:33:55PM +0100, Chris Lamb wrote: > One theory I've just thought of is that we are seeing more timeouts > simply because we have seen a larger number of GCC uploads recently. > > This not only produce either more diffoscope outputs in the first > place (as it makes packages unreproducible), the ones that it does > create are quite large.
That's certainly true. After the gcc uploads I always had to reschedule
all packages built in the previous day with an unpatched GCC that also
were unreproducible, to weed out false positive; and not to say that
before those uploads the builds were hugely different due to build paths
variation. So there were generally more diffoscope runs (which also
means more `objdump` processes, which tends to be heavy on the CPU),
which could just lead to a relevant increase of the general system load,
leading to a general slowness and also causing more "diffoscope
timeouts".
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
