So it looks like I have sorted out the issue with nightly builds and now
I'd like to reduce the number of tests being skipped.

I see this at the end of the nightly report :

TESTDONE: 782 tests out of 782 reported OK: 100%
TESTDONE: 1026 tests were considered during 529 seconds.
TESTINFO: 244 tests were skipped due to these restraints:
TESTINFO: "curl lacks debug support" 78 times (67, 68, 69, 81, 89, 90,
91, 150, 155 and 69 more)
TESTINFO: "curl lacks Metalink support" 16 times (2005, 2008, 2009,
2010, 2011, 2012, 2013, 2014, 2015 and 7 more)
TESTINFO: "curl lacks http2 support" 1 times (1800)
TESTINFO: "failed starting HTTP-pipe server" 4 times (1900, 1901, 1902,
1903)
TESTINFO: "no stunnel" 34 times (300, 301, 302, 303, 304, 305, 306, 307,
308 and 25 more)
TESTINFO: "failed starting SSH server" 56 times (564, 582, 583, 600,
601, 602, 603, 604, 605 and 47 more)
TESTINFO: "rlimit problem: fds needed 65562 > system limit 65536" 1
times (518)
TESTINFO: "curl lacks PSL support" 1 times (1136)
TESTINFO: "configured as DISABLED" 10 times (594, 836, 882, 938, 1209,
1211, 1316, 1510, 1512 and 1 more)
TESTINFO: "Resolving IPv6 'ip6-localhost' didn't work" 2 times (241, 1083)
TESTINFO: "curl lacks WinSSL support" 1 times (2043)
TESTINFO: "curl lacks unittest support" 21 times (1300, 1301, 1302,
1303, 1304, 1305, 1306, 1307, 1308 and 12 more)
TESTINFO: "curl lacks TrackMemory support" 2 times (96, 558)
TESTINFO: "precheck command error" 17 times (831, 834, 877, 880, 933,
936, 2023, 2024, 2025 and 8 more)
gmake[1]: Leaving directory `/build-3315/tests'
testcurl: tests were run
testcurl: the tests were successful!
testcurl: ending nicely
testcurl: removing the build-3315 dir
testcurl: removing the buildlog-3315 file
testcurl: ENDING HERE

So from top to bottom :

  1) TESTINFO: "curl lacks debug support"

     I am certain that I have the -g option in the compiler flags
     but this must refer to something else. Perhaps some configure
     option that allows for better testing.

  2) TESTINFO: "curl lacks Metalink support"

     No idea here at all. I can search around.

  3) TESTINFO: "curl lacks http2 support"

     This seems obvious. Most likely I need nghttp2 but I have no idea
     how close to production ready that is.

  4) TESTINFO: "failed starting HTTP-pipe server"

     No idea on this. Hopefully it is because I do nightly builds as
     an ordinary user. If that user needs special permissions to use
     a low port number like 80 or 443 then it is easily sorted out.

  5) TESTINFO: "no stunnel"

     I agree. No idea why I would want it or need it but perhaps
     worth looking into merely for testing purposes.

  6) TESTINFO: "failed starting SSH server"

     Most likely a similar fault as (4) wherein a low number port
     service is needed.

  7) TESTINFO: "rlimit problem: fds needed 65562 > system limit 65536"

     This one has me scratching my head. If limits need to move then
     no problem. At the moment prctl tells me :

         NAME PRIVILEGE VALUE FLAG ACTION
         process.max-file-descriptor basic 256 - deny
         privileged 65.5K - deny
             system 2.15G max deny

    So that resource control can be moved but I will need to fiddle
    with a project setup and perhaps a new user to run the nightly.

  8) TESTINFO: "curl lacks PSL support"

    No clue.

  9) TESTINFO: "configured as DISABLED"

    Also no clue.

10) TESTINFO: "Resolving IPv6 'ip6-localhost' didn't work"

    OKay .. this has me baffled because I certainly have ipv6
    enabled and I guess what I need to do is check with ISC dig
    against my nearby dns server to see if ipv6 data is being
    returned.

11) TESTINFO: "curl lacks WinSSL support"

     yep .. never will either.

12) TESTINFO: "curl lacks unittest support"

     no clue here

13) TESTINFO: "curl lacks TrackMemory support"

     no clue here

14) TESTINFO: "precheck command error"

     another "no clue" here either.

So a few items to tweak above will most likely result in more nightly
tests running. Certainly the HTTP2 issues should be looked at however
it means I have to go down a software rabbit hole a bit.

Dennis
-------------------------------------------------------------------
List admin: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2016-05-21