You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by "Mark G. Thomas" <Ma...@Misty.com> on 2005/05/25 19:29:16 UTC
SpamAssassin-3.0.3 test failure
Hi,
I'm new here, and am not positive if this is the right place to ask
this question.
I am not sure how to proceed in determining what broke and why.
I had no troubles with SpamAssassin-3.0.2, but after following the same
configure and build steps, I'm getting a test failure on 3.0.3, for a
test that is fine in 3.0.2. I've repeated clean untar, configure, "make",
and "make test" for both versions, and still get this new failure on 3.0.3,
but not 3.0.2. This is the only test that fails on my system.
segment from SpamAssassin-3.0.2 testing:
----------------------------------------------
make test
...
t/utf8......................ok
t/whitelist_addrs...........ok
t/whitelist_from............ok
t/whitelist_to..............ok
t/zz_cleanup................ok
All tests successful, 11 tests skipped.
Files=68, Tests=1384, 690 wallclock secs (574.54 cusr + 57.29 csys = 631.83 CPU)
segment from SpamAssassin-3.0.3 testing:
----------------------------------------------
make test
...
t/utf8......................ok
t/whitelist_addrs...........FAILED test 5
Failed 1/5 tests, 80.00% okay
t/whitelist_from............ok
t/whitelist_to..............ok
t/zz_cleanup................ok
Failed Test Stat Wstat Total Fail Failed List of Failed
-------------------------------------------------------------------------------
t/whitelist_addrs.t 5 1 20.00% 5
11 tests skipped.
Failed 1/68 test scripts, 98.53% okay. 1/1386 subtests failed, 99.93% okay.
*** Error code 29
make: Fatal error: Command failed for target `test_dynamic'
Here is just the failed test, on 3.0.3:
----------------------------------------
mark@marvin% /opt/bin/perl whitelist_addrs.t
1..5
# Running under perl version 5.008004 for solaris
# Current time local: Wed May 25 13:19:17 2005
# Current time GMT: Wed May 25 17:19:17 2005
# Using Test.pm version 1.24
/opt/bin/perl -T -w ../spamassassin -C log/test_rules_copy --siteconfigpath log/localrules.tmp -p log/test_default.cf --add-addr-to-whitelist whitelist_test@whitelist.spamassassin.taint.org
/opt/bin/perl -T -w ../spamassassin -C log/test_rules_copy --siteconfigpath log/localrules.tmp -p log/test_default.cf -L < data/nice/002
ok 1
Checking spamno
ok 2
/opt/bin/perl -T -w ../spamassassin -C log/test_rules_copy --siteconfigpath log/localrules.tmp -p log/test_default.cf -L < data/spam/004
Checking spamno
ok 3
/opt/bin/perl -T -w ../spamassassin -C log/test_rules_copy --siteconfigpath log/localrules.tmp -p log/test_default.cf --remove-addr-from-whitelist whitelist_test@whitelist.spamassassin.taint.org
/opt/bin/perl -T -w ../spamassassin -C log/test_rules_copy --siteconfigpath log/localrules.tmp -p log/test_default.cf -L < data/spam/004
Checking spamyes
ok 4
/opt/bin/perl -T -w ../spamassassin -C log/test_rules_copy --siteconfigpath log/localrules.tmp -p log/test_default.cf --add-addr-to-blacklist whitelist_test@whitelist.spamassassin.taint.org
/opt/bin/perl -T -w ../spamassassin -C log/test_rules_copy --siteconfigpath log/localrules.tmp -p log/test_default.cf -L < data/nice/002
Checking spamyes
Not found: spamyes = X-Spam-Status: Yes
not ok 5
# Failed test 5 in SATest.pm at line 530
Here is at same test, successful, on 3.0.2:
----------------------------------------
mark@marvin% !/opt
/opt/bin/perl whitelist_addrs.t
1..5
# Running under perl version 5.008004 for solaris
# Current time local: Wed May 25 13:27:00 2005
# Current time GMT: Wed May 25 17:27:00 2005
# Using Test.pm version 1.24
/opt/bin/perl -T -w ../spamassassin -C log/test_rules_copy --siteconfigpath log/localrules.tmp -p log/test_default.cf --add-addr-to-whitelist whitelist_test@whitelist.spamassassin.taint.org
/opt/bin/perl -T -w ../spamassassin -C log/test_rules_copy --siteconfigpath log/localrules.tmp -p log/test_default.cf -L < data/nice/002
ok 1
Checking spamno
ok 2
/opt/bin/perl -T -w ../spamassassin -C log/test_rules_copy --siteconfigpath log/localrules.tmp -p log/test_default.cf -L < data/spam/004
Checking spamno
ok 3
/opt/bin/perl -T -w ../spamassassin -C log/test_rules_copy --siteconfigpath log/localrules.tmp -p log/test_default.cf --remove-addr-from-whitelist whitelist_test@whitelist.spamassassin.taint.org
/opt/bin/perl -T -w ../spamassassin -C log/test_rules_copy --siteconfigpath log/localrules.tmp -p log/test_default.cf -L < data/spam/004
Checking spamyes
ok 4
/opt/bin/perl -T -w ../spamassassin -C log/test_rules_copy --siteconfigpath log/localrules.tmp -p log/test_default.cf --add-addr-to-blacklist whitelist_test@whitelist.spamassassin.taint.org
/opt/bin/perl -T -w ../spamassassin -C log/test_rules_copy --siteconfigpath log/localrules.tmp -p log/test_default.cf -L < data/nice/002
Checking spamyes
ok 5
--
Mark G. Thomas (Mark@Misty.com)
voice: 215-591-3695
http://www.misty.com/ http://mail-cleaner.com/
Re: SpamAssassin-3.0.3 test failure
Posted by Loren Wilton <lw...@earthlink.net>.
> I am pleased to report the problem is solved.
>
> I obtained and installed the latest Berkeley DB from sleepycat.org,
> then the perl module DB_File-1.811. This resolved the problem.
Please open a bug in BZ showing the symptoms and documenting the fix, and
give it a title of something like "unuseful error messages for old DB_File
version".
There is supposed to be a check during the install that checks for the
required version of everything SA might use, and complains if an old version
is found. Clearly DB_FIle doesn't seem to be on that list, and clearly
should be.
Separately, there is an open bug for cleaning up useless "perl error!" error
messages that describe an SA option with incorrect syntax. One could argue
that your 'error message' falls into both of these camps.
Loren
Re: SpamAssassin-3.0.3 test failure
Posted by "Mark G. Thomas" <Ma...@Misty.com>.
Hi,
On Wed, May 25, 2005 at 06:38:00PM -0700, Robert Menschel wrote:
> Hello Mark,
>
> Wednesday, May 25, 2005, 10:29:16 AM, you wrote:
...
> MGT> I had no troubles with SpamAssassin-3.0.2, but after following the same
> MGT> configure and build steps, I'm getting a test failure on 3.0.3, for a
> MGT> test that is fine in 3.0.2. I've repeated clean untar, configure, "make",
> MGT> and "make test" for both versions, and still get this new failure on 3.0.3,
> MGT> but not 3.0.2. This is the only test that fails on my system.
...
I am pleased to report the problem is solved.
I obtained and installed the latest Berkeley DB from sleepycat.org,
then the perl module DB_File-1.811. This resolved the problem.
Mark
--
Mark G. Thomas (Mark@Misty.com)
voice: 215-591-3695
http://www.misty.com/ http://mail-cleaner.com/
Re: SpamAssassin-3.0.3 test failure
Posted by Robert Menschel <Ro...@Menschel.net>.
Hello Mark,
Wednesday, May 25, 2005, 10:29:16 AM, you wrote:
MGT> I'm new here, and am not positive if this is the right place to
MGT> ask this question.
Yes, it is.
MGT> I am not sure how to proceed in determining what broke and why.
MGT> I had no troubles with SpamAssassin-3.0.2, but after following the same
MGT> configure and build steps, I'm getting a test failure on 3.0.3, for a
MGT> test that is fine in 3.0.2. I've repeated clean untar, configure, "make",
MGT> and "make test" for both versions, and still get this new failure on 3.0.3,
MGT> but not 3.0.2. This is the only test that fails on my system.
By "clean untar", do you mean you opened the tar into a new/empty
directory, and then did all the install steps in that directory, with
nothing left behind from any previous install?
If so, then that's good, and what should have worked.
By "configure", do you mean "perl Makefile.pl"?
I've found occasional problems when I attempt to "remake" SA in a
directory structure that already has previous files in it. However,
working in a completely clean directory has always worked for me.
Bob Menschel