Still seeing the t/api/request_rec.t failures, which do not occur with the same machine and same settings with 2.0.10. It's failing after the mtime test, before the finfo test.

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/filter/in_bbs_inject_header.t       (Wstat: 0 Tests: 36 Failed: 3)
  Failed tests:  22, 26, 30
Files=245, Tests=3402, 98 wallclock secs ( 0.71 usr 0.30 sys + 67.05 cusr 12.05 csys = 80.11 CPU)
Result: FAIL
Failed 2/245 test programs. 3/3402 subtests failed.

This is what i see in the error_log:

[Tue Sep 24 22:56:10.012601 2019] [perl:error] [pid 743] [client] APR::Finfo::stat: (70008) Partial results are valid but processing is incomplete at /tmp/mod_perl-2.0.11-rc2/t/response/TestAPI/ line 168

Not sure if this is a concern or not, but it seems like it should be?


On 9/24/19 12:53 PM, Steve Hay wrote:
Please download, test, and report back on this mod_perl 2.0.11 release

MD5  = abc2c2168121a09b0fc3b6fc6adc00bd
SHA1 = 36ee7626506a3a461118b3957814dfe9331ef1de

Changes since RC1 are as follows:

Fix [CVE-2011-2767] Arbitrary Perl code execution in the context of the user
account via a user-owned .htaccess. Patch from #644169. [Jan
Ingvoldstad <>]

Fix potential test suite hangs due to pipelined response deadlocks. Patch
from #82409. [Zefram <>]

Fix t/compat/request.t failures [Steve Hay]

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to