On 26/09/14 14:07, Wookey wrote:
> Hanging: (Killed after some hours)
> http://buildd.debian-ports.org/status/fetch.php?pkg=augeas&arch=arm64&ver=1.2.0-0.2&stamp=1409191411
> 
> This ended with:
> PASS: test-wctype-h
> PASS: test-init.sh
> PASS: test-verify.sh
> PASS: test-memchr
> make[7]: *** Deleting file 'test-lock.log'
> E: Caught signal ‘Terminated’: terminating immediately
> make[2]: *** [check-recursive] Terminated
> make: *** [build-arch] Terminated
> make[4]: *** wait: No child processes.  Stop.
> make[4]: *** Waiting for unfinished jobs....
> make[4]: *** wait: No child processes.  Stop.
> make[6]: *** [check-TESTS] Terminated
> make[3]: *** [check] Error 2
> make[1]: *** [override_dh_auto_test] Terminated
> make[7]: *** [test-lock.log] Terminated
> make[5]: *** [check-am] Terminated
> Terminated
> 
> Repeating it in a chroot it stopped for an hour or two after:
> PASS: test-localename
> 
> And I had to ctrl-C out.
> 
> The above log got further suggesting that it was actually stuck on either 
> SKIP: test-mbrtowc4.sh
> or
> PASS: test-malloca

These first tests are actually from gnulib, which is included in the
tarball.  It's held at a fixed version with a submodule in the upstream
repo (https://github.com/hercules-team/augeas) so you may want to try
replacing the gnulib directory in the tarball with a newer version.
It's quite possible there's a bug that's been fixed for arm64 that
Augeas is missing.

> (Does it try the 'SKIP' tests at all or not?)

I don't think so, at least for core Augeas tests they usually indicate
some pre-req is missing (e.g. wrong platform).

> Could this be a malloc problem?

Maybe, that's the sort of thing gnulib is usually testing in strange
ways to ensure compatibility.

The other thing to be aware of is that the Augeas tests (once the gnulib
suite has run) will happily use a few GB of RAM to test some of the more
complex modules.

-- 
Dominic Cleal
Red Hat Engineering


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to