Bug#902383: [Qa-jenkins-dev] Bug#902383: Bug#902383: reproducible-builds.org: test host-specific FTBFS failures on i386
On Mon, Jun 25, 2018 at 08:16:07PM +0200, Mattia Rizzolo wrote: > splitting the builder hosts is a bunch of work and Holger was somewhat > opposed to it, ... I'm neither opposed to the idea nor the work, we just lack the diskspace for more nodes... -- cheers, Holger signature.asc Description: PGP signature
Bug#902383: [Qa-jenkins-dev] Bug#902383: reproducible-builds.org: test host-specific FTBFS failures on i386
On Mon, Jun 25, 2018 at 01:54:16PM -0400, David Steele wrote: > For some jobs, it appears that profitbricks-build2-i386.debian.net > repeatedly returns FTBFS, while profitbricks-build6-i386.debian.net always > succeeds. This situation has been in place for 2 months. That's because that host (and pb12) is running on the jessie's kernel, because later kernels are bugged for us (→ #876035). It just so happens that Qt >= 5.10 requires linux 3.17 (→ #895718), and for some crappy reason the linker returns ENOENT in when the abitag of a library doesn't match. > Note that i386 has the highest current FTBFS count across architectures. Quite sure that's due to this issue. To me, it's not yet quite clear how to best deal with this issue, as updating the kernel is going to tear the performance apart once again, splitting the builder hosts is a bunch of work and Holger was somewhat opposed to it, patching Qt requires competences I don't have, and the workaround suggested in #895718#104 is terrible. Thanks for filing this bug, I believe nobody took care of filing a tracking bug against j.d.o yet… -- 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
Bug#902383: reproducible-builds.org: test host-specific FTBFS failures on i386
Package: jenkins.debian.org Severity: Serious For some jobs, it appears that profitbricks-build2-i386.debian.net repeatedly returns FTBFS, while profitbricks-build6-i386.debian.net always succeeds. This situation has been in place for 2 months. There is a FTBFS failure currently reported for Sirikali in Buster and Sid. The failure is persistent across re-runs. I can't reproduce the failure locally. The formal build succeeded. Looking closer, success and failure is tied to the worker hardware. build2 always fails, whether running the first run or the second. build6 always passes, when used for the first run. I'm not able to see what the difference may be. Note that i386 has the highest current FTBFS count across architectures. -- AE0D BF5A 92A5 ADE4 9481 BA6F 8A31 71EF 3661 50CE
