Le 27/03/2019 à 16:09, Daniel Ruggeri a écrit :
Hi, all;
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release this
candidate tarball as 2.4.39:
[ ] +1: It's not just good, it's good enough!
[X] +0: Let's have a talk.
[ ] -1: There's trouble in paradise. Here's what's wrong.
The computed digests of the tarball up for vote are:
sha1: e66d6bfea42254e64d3b5009f49ecc486ac46de2 *httpd-2.4.39.tar.gz
sha256:
8b95fe249f3a6c50aad3ca125eef3e02d619116cde242e1bc3c266b7b5c37c30
*httpd-2.4.39.tar.gz
Tested on Ubuntu 18.10, compiled with gcc 8.2.0.
Tested with event, prefork and worker.
I see some core dumps when using 'prefork' in the ssl tests.
t/TEST t/ssl/
t/ssl/proxy.t ...... ok
t/ssl/require.t .... ok
t/ssl/v2.t ......... skipped: SSLv2 test(s) not applicable
t/ssl/varlookup.t .. 62/83 [ error] oh dangit, server dumped core
[ error] for stacktrace, run: gdb /home/tititou36/httpd-2.4/bin/httpd
-core /home/tititou36/svn_test_framework/t/core
t/ssl/varlookup.t .. ok
t/ssl/verify.t ..... 1/3 [ error] oh dangnabit, server dumped core
[ error] for stacktrace, run: gdb /home/tititou36/httpd-2.4/bin/httpd
-core /home/tititou36/svn_test_framework/t/core
t/ssl/verify.t ..... ok
Each time I run the test framework it ends with a core dumps during ssl
tests, but not always on the same test.
I've NOT spotted any issue with the other MPM.
It is likely a issue in my test environment, but I've never seen it before.
Could others confirm that they have tested with 'prefork' and that they
don't have any issue?
Test coverage data from my test environment attached.
CJ
Title: HTTPd Test Coverage
|
HTTPd Test Coverage
|
This should give us some idea of how well our test-framework actually stress our
code.
Last generated vendredi 29 mars 2019, 22:45:04 (UTC+0100)
|
|
|
|
Copyright © 1997-2018, The Apache Software Foundation
|
|
