Hi,
On Thu, Sep 03, 2015 at 10:55:15PM +0200, Julien Cristau wrote:
> Control: severity -1 serious
>
> On Wed, Jan 14, 2015 at 17:47:20 +0000, Fernando Seiti Furusato wrote:
>
> > Source: ergo
> > Severity: normal
> > Tags: patch
> > User: debian-powe...@lists.debian.org
> > Usertags: ppc64el
> >
> > Dear Maintainer,
> >
> > The package ergo fails to build from source on ppc64el. It actually times
> > out at some point, in addition to the test failures.
> >
> It fails on many architectures:
> https://buildd.debian.org/status/logs.php?pkg=ergo&ver=3.4.0-1%2Bb1&suite=sid
>
> That may or may not be the same issue, in any case raising to serious.
After digging into this a bit more, I think ergo's testsuite is
inheritly not parallel-safe: it uses no subdirectories and a default
output file ("ergoscf.out") which it only renames to something
test-specific on failure. There's also intermediate binary files like
"density.bin" and above mentioned ergoscf.out gets removed at the
beginning of a test...
There does not seem to be a safe way to tell ergo to use a different
name as output file (it's not using stdout by default).
So I will see about forcing parallel to off for this package. Not sure
what this will mean for the timeouts seen on some buildds, though.
Michael
