Bug #30481 for CPAN: Failed Test Suite with Mail::SpamAssassin 3.2.3

Mon Nov 05 01:39:35 2007 imacat [...] cpan.org - Ticket created

Subject:

Failed Test Suite with Mail::SpamAssassin 3.2.3

Dear Andreas J. König, Hi. This is imacat from Taiwan. I found a strange issue that I cannot dig further. It seems that CPAN 1.9203 failed to run the test suite of Mail::SpamAssassin 3.2.3 without previous version of Mail::SpamAssassin installed. You may refer to this test report: Mail::SpamAssassin 3.2.3 without previous version installed http://www.nntp.perl.org/group/perl.cpan.testers/2007/11/msg741278.html Mail::SpamAssassin 3.2.0 without previous version installed http://www.nntp.perl.org/group/perl.cpan.testers/2007/11/msg741307.html Mail::SpamAssassin 3.2.3 with 3.2.0 installed http://www.nntp.perl.org/group/perl.cpan.testers/2007/11/msg741320.html However, CPAN 1.9203 runs the test suite of Mail::SpamAssassin 3.2.0 nicely. If I install Mail::SpamAssassin 3.2.0 first, CPAN 1.9203 runs the test suite of 3.2.3 nicely, too. CPAN 1.7602 (comes with Perl 5.8.8) works nicely, too. If I run "perl Makefile.PL; make; make test" manually on Mail::SpamAssassin 3.2.3, it works nicely, too. This issue seems to be specific to newer versions of CPAN. Sorry that since both CPAN and Mail::SpamAssassin are big modules, its a little difficult for me to dig further. But I still tried to limit the scope of this issue as possible. I do not know if this is a general issue or is specific to Mail::SpamAssassin 3.2.3. But I worry that if this is a general issue then all CPAN testers reporting with CPAN 1.9203 may suffer from this issue, and report many wrong result to innocent modules. (I'm still using CPANPLUS.) Please tell me if there is any question, or if I could be of help. Thank you.

Mon Nov 05 02:39:26 2007 andreas.koenig.7os6VVqR [...] franz.ak.mind.de - Correspondence added

Subject:	Re: [rt.cpan.org #30481] Failed Test Suite with Mail::SpamAssassin 3.2.3
Date:	Mon, 05 Nov 2007 08:39:08 +0100
To:	bug-CPAN [...] rt.cpan.org
From:	andreas.koenig.7os6VVqR [...] franz.ak.mind.de (Andreas J. Koenig)

A few days ago I posted a bug in their bugzilla where I had indications (but no prove) that their test suite calls "perl" instead $^X. This may or may not have an impact on your setup. Another interesting datapoint is that I have run 96 tests of fresh perls against Spamassassin 3.2.3 and 92 PASS. The 4 failing ones were due to dependency issues, so I can say I have 100% pass and none of these perls had the previous spamassassin version installed. I welcome further data points because at the moment I have no idea where to investigate. -- andreas

Mon Nov 05 02:39:27 2007 The RT System itself - Status changed from 'new' to 'open'

Mon Nov 05 23:47:19 2007 imacat [...] cpan.org - Correspondence added

Subject:	Fail Installing New Mail::SpamAssassin 3.2.3
From:	imacat [...] cpan.org

On 2007-11-05 02:39:26 Mon, andreas.koenig.7os6VVqR@franz.ak.mind.de wrote: Show quoted text

> A few days ago I posted a bug in their bugzilla where I had > indications (but no prove) that their test suite calls "perl" instead > $^X. This may or may not have an impact on your setup.

I do not think so, though this gave me new ideas. I tested on a separate fresh new Perl installation on a machine that has Mail::SpamAssassin installed on the system Perl build, and on a system Perl build without Mail::SpamAssassin. The results are the same. This issue seems to be related to the current Perl installation ($^X), not with the system Perl installation ("perl"). Show quoted text

> I welcome further data points because at the moment I have no idea > where to investigate.

I made more experiments. This issue seems to be limited to the following factors: 1. No previous Mail::SpamAssassin is installed in the current Perl installation ($^X). 2. CPAN 1.9203 3. Mail::SpamAssassin 3.2.1 or above (3.2.1, 3.2.2, 3.2.3) 4. Running as root. The 2 tests (t/spamc_optC.t and t/spamc_optL.t) success if any of the above condition does not meet. That is, if I install with CPANPLUS, or install with manually "perl Makefile.PL; make; make test", they success. I compares the 2 directories. Only the spamc/spamc binaries differ. It seems that the spamc/spamc binary created with CPAN 1.9203 fails to create the t/log/user_state/bayes_toks and t/log/user_state/bayes_seen files needed for testing when running t/spamc_optC.t and t/spamc_optL.t. Will there be any issue that built binaries created by CPAN may differ from the manually make'd binaries? For example, STDOUT/STDERR redirection? I filed a same bug report to Mail::SpamAssassin: http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5713 Please tell me if you need any information, or if you have any ideas. Thank you.