Le 18/09/2018 à 02:56, 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.35: [X] +1: It's not just good, it's good enough! [ ] +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: md5: 92ddccfbd43b533578499d1faaad17fe *httpd-2.4.35.tar.gz sha1: b7996c2c1f7ff5bb217114fe5354a19a5207ab62 *httpd-2.4.35.tar.gz sha256: 31c2c82c9cd34749cbb60d04619d9aa3fb0814ab22246ad588d2426dde90c72c *httpd-2.4.35.tar.gz
+1 Ubuntu 18.04 gcc 8.1I now build with gcc test-coverage options. Attached, the results on my machine after a t/TEST. I use a slightly modified version of the script I've updated for APR. (don't pay attention to all the APR related text in the attached file :))
This gives the picture of what need more love in the test-framework. I can share the corresponding .gcov files to see which lines are never executed while running the tests.
This still need to be improved and I will post one day a How-To about it.Based on it, I'll try to add some new test-cases to improve the test coverage of the test-framework. (i.e. see my latest additions for modules that were completely untested (reflector.t; allowmethods.t) or some paths not tested (setenvif.t)) We'll never be able to test all possible combination, but the more lines are executed at least one, the better it is.
Thx for RM CJTitle: Test Coverage