status of test code

[steve at keptprivate.com]

Update:I was finally able to build 2.3.13 on centos 8 (8.3). I managed this by going back to the qmailtoaster spec file, removing a few things no longer relevant (vpopmail) and disabling all the tests. Most tests were still running but there were also many that did not. The good news is the resulting executable in the RPM no longer complains about not being able to find libdovecot.so. i've done some basic testing on imap and everything appears to be working.Someone who maintains the tests and rpm build should really have a look. Doing a build on a fresh centos 8 machine, as I was able to with the qmailtoaster source rpm, should really be much simpler. My impression is the current spec file may have edits that were eroneously committed? SteveSent from my T-Mobile 4G LTE device------ Original message------From: steve at keptprivate.comDate: Sat, Jan 9, 2021 3:42 PMTo: dovecot at dovecot.org;Cc: Subject:status of test codeHi,

I'm continuing to try to build 2.3.13 with a source RPM.

At this
 point I've taken the source zip file and I'm working with the previously working qmailtoaster SPEC file and RPM build process.

The toaster SPEC file runs the built-in dovecot tests after build... 2.3.11 would make it through all the tests with a few minor exceptions.

2.3.13 seems no longer able to run the test is lib-ssl-iostream or lib-lua (and perhaps others, but that's as far as I've gotten).

I can selectively disable the tests to make progress, but it raises the question of what the plans are for the built-in tests.

Also, I continue to not be able to find where all the testing is turned on/off at once? I'm sure it will be obvious when someone tells me but 
please tell me, because I'm pulling my hair out.

Steve

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dovecot.org/pipermail/dovecot/attachments/20210110/3d5aff4c/attachment.html>