[Pkg-db-devel] Bug#443633: Bug#443633: db_4.6.19-1(m68k/unstable/washi): self-test FTBFS on m68k

Clint Adams schizo at debian.org
Sun Sep 23 08:38:45 UTC 2007


On Sat, Sep 22, 2007 at 08:00:30PM -0500, Stephen R Marenka wrote:
> | FAIL: run_subsystem: env env007:  env66: mmap: Cannot allocate memory

> | FAIL: error in ./TESTDIR/env012.log.p2 : ./TESTDIR/env012.log.p2:FAIL:23:19:53 (00:00:00) db_get: expected DATA1, got 
> | FAIL: error in ./TESTDIR/env012.log.p2 : ./TESTDIR/env012.log.p2:FAIL:23:19:53 (00:00:00) ../dist/../test/envscript.tcl run: FAIL:23:19:53 (00:00:00) db_get: expected DATA1, got : pid 7605: expected 0, got 1
> | FAIL: error in ./TESTDIR/env012.log.p3 : ./TESTDIR/env012.log.p3:FAIL:23:20:43 (00:00:00) db_get: expected DATA1, got 
> | FAIL: error in ./TESTDIR/env012.log.p3 : ./TESTDIR/env012.log.p3:FAIL:23:20:43 (00:00:00) ../dist/../test/envscript.tcl run: FAIL:23:20:43 (00:00:00) db_get: expected DATA1, got : pid 7757: expected 0, got 1

Looking in obj/ALL.OUT (instead of the grep) will give you more useful
information.  The tests are all TCL scripts in the test/ directory.

The detailed log and the scripts should help you isolate what's going on
better.





More information about the Pkg-db-devel mailing list