Re: [exim-dev] Preliminary testing of a new Exim test suite

Philip Hazel wrote:
> On Thu, 13 Oct 2005, Daniel Tiefnig wrote:
>> As I said I'm using GnuTLS 1.2.6, I'll see if I can try 1.2.3 soon.

Not yet..

> I haven't done anything about that, because I do suspect it is a version
> issue.

Hmm, so what? Require people to use GnuTLS 1.2.3? :o)

>>I'll give it a try with content scanning and OpenSSL tomorrow...

First, I had a different problem with the testsuite now, it repeatedly
crashed on test 0021, without an error or anything.

I tried to debug this with perl debugger and strace, but after tinkering
with suid strace (what a pain) the test started working again. :o(
I remember I allready had this problem once, and I weren't lucky to
debug it. I'll see if I can find a way to reliably reproduce this. At a
first glance, test 0021 seems to succeed and crash quite randomly.

The last two lines in spool/log/mainlog an rejectlog were:
2005-10-17 11:31:39 H=[10.9.8.9] U=tiefnig rejected connection in
"connect" ACL: forcibly dropped
2005-10-17 11:31:39 U=tiefnig rejected connection in "connect" ACL

Feature request: Maybe there should be some sort of positive response,
so one can tell whether the script (or single tests) finished
successfully, or just died silently. A " ... OK." for each test or "Test
set finished." at the end of the test run would do the trick.


Test OpenSSL/2102 fails with the following:
Line 83 of "test-stdout-munged" does not match line 83 of "stdout/2102".
----------
pppp:error14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake
failure:s3_pkt.c:1054:SSL alert number 40
----------
pppp:error14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake
failure:s3_pkt.c:1052:SSL alert number 40

Duh. This is with OpenSSL 0.9.8.
The same mismatch applies for tests OpenSSL/2114 and OpenSSL/2124.

And in test OpenSSL/2111:
Line 3 of "test-mainlog-munged" does not match line 3 of "log/2111".
----------
[...] (SSL_CTX_set_cipher_list): error: <<detail omitted>>
----------
[...] (SSL_connect): error: <<detail omitted>>


And OpenSSL/2125:
Line 3 of "test-mainlog-munged" does not match line 3 of "log/2125".
----------
1999-03-02 09:44:33 10HmaX-0005vi-00 a TLS session is required for
ip4.ip4.ip4.ip4 [ip4.ip4.ip4.ip4], but an attempt to start TLS failed
----------
1999-03-02 09:44:33 10HmaX-0005vi-00 TLS error on connection to
ip4.ip4.ip4.ip4 [ip4.ip4.ip4.ip4] (SSL_connect): error: <<detail omitted>>

Line 10 has the "SSL_CTX_set_cipher_list => SSL_accept" mismatch, like
test 2111.


When omitting "4000-scanning" tests, the message "missing running
SpamAssassin" is quite misleading if e.g. spamc is just not installed.
Something like "spamc failed, is spamd running?" would be better, maybe.

For ClamAV, the default config file on debian systems is
"/etc/clamav/clamd.conf". AFAIK there's no way to make clam binaries
tell their configuration files. Maybe you should prompt for the location
of the config file if you can't find it on the default locations?

Test scanning/4000 says:
Line 39 of "test-mail-munged" occurs before line 39 of "mail/4000.userx".
----------
X-is-spam: classified as spam


lg,
daniel