I'm seeing more test failures for 2.0.11 RC1 than for 2.0.10 with the
same setup.
Test Summary Report
-------------------
t/api/request_rec.t (Wstat: 0 Tests: 43 Failed: 0)
Parse errors: Bad plan. You planned 55 tests but ran 43.
t/compat/request.t (Wstat: 0 Tests: 12 Failed: 0)
Parse errors: Bad plan. You planned 22 tests but ran 12.
t/filter/in_bbs_inject_header.t (Wstat: 0 Tests: 36 Failed: 3)
Failed tests: 22, 26, 30
Files=245, Tests=3392, 102 wallclock secs ( 0.76 usr 0.34 sys + 72.85
cusr 11.27 csys = 85.22 CPU)
Result: FAIL
Failed 3/245 test programs. 3/3392 subtests failed.
The compat/request.t failures don't occur on the previous version. Is
this expected? I'm using perl 5.28.0, and httpd 2.4.41 prefork.
Adam
On 9/2/19 8:34 AM, Steve Hay wrote:
Please download, test, and report back on this mod_perl 2.0.11 release
candidate.
https://dist.apache.org/repos/dist/dev/perl/mod_perl-2.0.11-rc1.tar.gz
MD5 = 417823274b32e5ca8759cf3760ad1591
SHA1 = e47c72337e6766c403d0a76b59d3808625e5162b
Major changes in this release are as follows:
Fix use-after-free segfault in ap_server_config_defines seen on
start-up on OpenBSD. [Found/fixed by Sam Vaughan/Joe Orton]
Fix build with Perls earlier than 5.13.6. [Rainer Jung
<rainer.j...@kippdata.de>]
Fix filter/in_bbs_inject_header.t test failure with Apache 2.4.25+.
[Stefan Fritsch <s...@sfritsch.de>]
Fix apache/read.t test failure with Apache 2.4.25+. [Niko Tyni
<nt...@debian.org>]
