Hi Adrian, On Mon, Jul 31, 2017 at 2:31 PM, Adrian Bunk <b...@debian.org> wrote: > Source: graphicsmagick > Version: 1.3.26-3 > Severity: serious > > 2 out of the 4 latest build attempts FTBFS on ppc64el: [...] > PASS: Magick++/tests/tests.tap 7 - colorHistogram > PASS: Magick++/tests/tests.tap 8 - exceptions > PASS: Magick++/tests/tests.tap 9 - montageImages > PASS: Magick++/tests/tests.tap 10 - morphImages > PASS: Magick++/tests/tests.tap 11 - readWriteBlob > PASS: Magick++/tests/tests.tap 12 - readWriteImages > E: Build killed with signal TERM after 150 minutes of inactivity Seen these, I do follow auto builds.
> The next test is "Magick++/demo/demos.tap 1 - analyze", > this seems to be the hanging one? I have no idea. I know three things. It can not be reproduced on the porterbox - I've tried the build several times. The build occasionally hangs since the Perl transition started - but the mentioned test rules are shell scripts. But the most important thing is that the fail always happened on ppc64el-unicamp-01 - the other buildd, ppc64el-osuosl-01 can build it without any problem. As such, I think it's the buildd that different in some way than the source has any known problem. Can you reschedule the build, first on ppc64el-unicamp-01, then on ppc64el-osuosl-01 and see the results? Maybe the former is not up to date and has some inconsistent package set installed? Regards, Laszlo/GCS
