Your message dated Tue, 3 Mar 2009 23:56:14 -0800
with message-id <[email protected]>
and subject line Re: Bug#516193: bogofilter: FTBFS: Test failure
has caused the Debian Bug report #516193,
regarding bogofilter: FTBFS: Test failure
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
516193: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516193
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bogofilter
Version: 1.1.7-2
Severity: serious
From my pbuilder build log (on amd64):
...
PASS: t.bogoutil
PASS: t.lock1
FAIL: t.lock3
----> the following test is skipped, set BF_RUN_VALGRIND=1 to run it
SKIP: t.valgrind
======================
1 of 50 tests failed
(2 tests were not run)
======================
make[6]: *** [check-TESTS] Error 1
make[6]: Leaving directory `/tmp/buildd/bogofilter-1.1.7/obj-db/src/tests'
make[5]: *** [check-am] Error 2
make[5]: Leaving directory `/tmp/buildd/bogofilter-1.1.7/obj-db/src/tests'
make[4]: *** [check] Error 2
make[4]: Leaving directory `/tmp/buildd/bogofilter-1.1.7/obj-db/src/tests'
make[3]: *** [check-recursive] Error 1
make[3]: Leaving directory `/tmp/buildd/bogofilter-1.1.7/obj-db/src'
make[2]: *** [check] Error 2
make[2]: Leaving directory `/tmp/buildd/bogofilter-1.1.7/obj-db/src'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/tmp/buildd/bogofilter-1.1.7/obj-db'
make: *** [check] Error 2
dpkg-buildpackage: failure: fakeroot debian/rules binary gave error exit status
2
pbuilder: Failed autobuilding of package
W: no hooks of type C found -- ignoring
-> Aborting with an error
-> unmounting /var/cache/pbuildd filesystem
-> unmounting dev/pts filesystem
-> unmounting proc filesystem
-> cleaning the build env
-> removing directory /build/chroot/ and its subdirectories
Can't open file 'wordlist.db' in directory './checks.26734.20090216T090059'.
error #2 - No such file or directory.
Remember to register some spam and ham messages before you
use bogofilter to evaluate mail for its probable spam status!
../../../src/tests/t.lock3: 31: cannot create
./checks.26734.20090216T090059/exits: Directory nonexistent
Can't open file 'wordlist.db' in directory './checks.26734.20090216T090059'.
error #2 - No such file or directory.
Remember to register some spam and ham messages before you
use bogofilter to evaluate mail for its probable spam status!
../../../src/tests/t.lock3: 31: cannot create
./checks.26734.20090216T090059/exits: Directory nonexistent
Can't open file 'wordlist.db' in directory './checks.26734.20090216T090059'.
error #2 - No such file or directory.
Remember to register some spam and ham messages before you
use bogofilter to evaluate mail for its probable spam status!
../../../src/tests/t.lock3: 31: cannot create
./checks.26734.20090216T090059/exits: Directory nonexistent
Can't open file 'wordlist.db' in directory './checks.26734.20090216T090059'.
error #2 - No such file or directory.
Remember to register some spam and ham messages before you
use bogofilter to evaluate mail for its probable spam status!
../../../src/tests/t.lock3: 31: cannot create
./checks.26734.20090216T090059/exits: Directory nonexistent
I'm not (currently) using any custom DEB_BUILD_OPTIONS like parallel=N
that would cause it to try to run tests asynchronously like that...
--
Daniel Schepler
--- End Message ---
--- Begin Message ---
On Tuesday 03 March 2009 16:47:14 Clint Adams wrote:
> On Tue, Feb 24, 2009 at 02:13:21PM +0000, Clint Adams wrote:
> > Can you reproduce this consistently?
>
> Or can you reproduce this at all with 1.2.0?
No, the new upload built fine on my machine, closing.
--
Daniel Schepler
--- End Message ---
