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

            Bug ID: 8336
           Summary: Test fails with IO::Socket::SSL 2.091 or higher
           Product: Spamassassin
           Version: 4.0.1
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Regression Tests
          Assignee: dev@spamassassin.apache.org
          Reporter: build+apa...@de-korte.org
  Target Milestone: Undefined

Since upgrading to IO::Socket::SSL 2.092 (or later), I see consistent failures
on the following test:

[  918s]        Not found: firstline =  Return-Path: sb55s...@yahoo.com at
t/spamd_ssl_z.t line 36.
[  918s] 
[  918s] #   Failed test at t/SATest.pm line 926.
[  918s]        Not found: endsinnums =  TEST_ENDSNUMS at t/spamd_ssl_z.t line
36.
[  918s] 
[  918s] #   Failed test at t/SATest.pm line 926.
[  918s]        Not found: noreal =  TEST_NOREALNAME at t/spamd_ssl_z.t line
36.
[  918s] 
[  918s] #   Failed test at t/SATest.pm line 926.
[  918s]        Not found: flag =  X-Spam-Flag: YES at t/spamd_ssl_z.t line 36.
[  918s] 
[  918s] #   Failed test at t/SATest.pm line 926.
[  918s]        Not found: stars =  X-Spam-Level: ********** at t/spamd_ssl_z.t
line 36.
[  918s] 
[  918s] #   Failed test at t/SATest.pm line 926.
[  918s]        Not found: status =  X-Spam-Status: Yes, score= at
t/spamd_ssl_z.t line 36.
[  918s] 
[  918s] #   Failed test at t/SATest.pm line 926.
[  918s] Output can be examined in: log/spamd_ssl_z.LoRoz6/d.spamd_ssl_z/out.0
[  918s] # Looks like you failed 6 tests of 9.
[  918s] t/spamd_ssl_z.t ................... 
[  918s] Dubious, test returned 6 (wstat 1536, 0x600)
[  918s] Failed 6/9 subtests 

It looks like 2.092 introduced changes in one sided shutdown with following
plain data that might hit us here.

Note that currently I'm not sure if the implementation in IO::Socket::SSL is
wrong or that there is something in this test that is causing this.

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

Reply via email to