https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8031

--- Comment #8 from Giovanni Bechis <giova...@paclan.it> ---
(In reply to Giovanni Bechis from comment #7)
> Created attachment 5802 [details]
> SATest workaround
> 
> This workaround fixes the issue, I do not know if it break something on
> other systems and it's better to have it as local patch.

(In reply to Sidney Markowitz from comment #6)
> (In reply to Giovanni Bechis from comment #5)
> > The proposed fix was just a way to better explain what's going on.
> > spamd(8) starts without issues, only regression tests are failing.
> > I think it may be one of recent changes to SATest.pm.
> > I will investigate more.
> 
> Oh, sorry, my brain must have been fried when I read the bug report and I
> thought it was from some random person running some older build and who
> didn't know the difference between require and use, and I didn't notice your
> name.
> 
> Ok, confirm if this is before or after the commit for bug 8030 because it
> seems like something related. If it happens even with the commit for bug
> 8030 it might be a case that I missed. Please post the output, usi9g the
> same perl that you run the tests with, of
> 
> perl -e 'print "\@INC:\n".join("\n", @INC)."\nPerl env:\n"; map {print "$_ =
> $ENV{$_}\n" if (/^PERL/);} keys(%ENV)'
> 
@INC:
/usr/local/cpanel
/usr/local/cpanel/3rdparty/perl/532/lib/perl5/cpanel_lib/x86_64-linux-64int
/usr/local/cpanel/3rdparty/perl/532/lib/perl5/cpanel_lib
/usr/local/cpanel/3rdparty/perl/532/lib/perl5/532/x86_64-linux-64int
/usr/local/cpanel/3rdparty/perl/532/lib/perl5/532
/opt/cpanel/perl5/532/site_lib/x86_64-linux-64int
/opt/cpanel/perl5/532/site_lib
Perl env

> to show the default @INC and relevant environment variables that the patch
> is supposed to be working with.
> 
> One thing to look for in this in the debug logs is if it only happens after
> a SIGHUP restart, and secondly, if it only happens when spamd is starting up
> a copy of itself some other way. Those are the most likely places my changes
> could fail.

reverting your latest change doesn't help.
Test output is:

+ /usr/bin/make test TEST_FILES=t/sa_check_spamd.t
"/usr/local/cpanel/3rdparty/perl/532/bin/perl" build/mkrules --exit_on_no_src
--src rulesrc --out rules --manifest MANIFEST --manifestskip MANIFEST.SKIP
no source directory found: exiting
"/usr/local/cpanel/3rdparty/perl/532/bin/perl" build/preprocessor  -Mvars
-DVERSION="4.000000" -DPREFIX="/usr/local/cpanel/3rdparty/perl/532/lib/perl5"
-DDEF_RULES_DIR="/usr/share/spamassassin"
-DLOCAL_RULES_DIR="/etc/mail/spamassassin"
-DLOCAL_STATE_DIR="/var/lib/spamassassin"
-DINSTALLSITELIB="/usr/local/cpanel/3rdparty/perl/532/lib/perl5/cpanel_lib"
-DCONTACT_ADDRESS="root\@localhost"
-DRE2C_BIN="/usr/local/cpanel/3rdparty/bin/re2c" -Msharpbang -Mconditional
-DPERL_BIN=""/usr/local/cpanel/3rdparty/perl/532/bin/perl"" -DPERL_WARN=""
-DPERL_TAINT="" -m755 -isa-update.raw -osa-update
cp sa-update blib/script/sa-update
"/usr/local/cpanel/3rdparty/perl/532/bin/perl" -MExtUtils::MY -e
'MY->fixin(shift)' -- blib/script/sa-update
PERL_DL_NONLAZY=1 "/usr/local/cpanel/3rdparty/perl/532/bin/perl"
"-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef
*Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')"
t/sa_check_spamd.t
t/sa_check_spamd.t .. 1/7       Not found: flag =  X-Spam-Flag: YES at
t/sa_check_spamd.t line 20.

#   Failed test at t/SATest.pm line 926.
        Not found: status =  X-Spam-Status: Yes, score= at t/sa_check_spamd.t
line 20.

#   Failed test at t/SATest.pm line 926.
Output can be examined in: log/sa_check_spamd.WH4bSS/d.sa_check_spamd/out.1
t/sa_check_spamd.t .. 6/7 # Looks like you failed 2 tests of 7.
t/sa_check_spamd.t .. Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/7 subtests 

Test Summary Report
-------------------
t/sa_check_spamd.t (Wstat: 512 Tests: 7 Failed: 2)
  Failed tests:  3-4
  Non-zero exit status: 2
Files=1, Tests=7, 10 wallclock secs ( 0.04 usr  0.01 sys +  1.02 cusr  0.20
csys =  1.27 CPU)
Result: FAIL
Failed 1/1 test programs. 2/7 subtests failed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to