tests: have runtests figure out disabled features #3950
Conversation
... so that runtests can skip individual test cases that test features that are explictiyl disabled in this build. This new logic is intended for disabled features that aren't otherwise easily visible through the curl_version_info() or other API calls. tests/server/disabled is a newly built executable that will output a list of disabled features. Outputs nothing for a default build.
| "* $curl\n", | ||
| "* $libcurl\n", | ||
| "* Features: $feat\n", | ||
| "* Disabled: $dis\n", |
There was a problem hiding this comment.
This can be used uninitialized according to the buildfarm: https://curl.haxx.se/dev/log.cgi?id=20190527165744-10382#prob1
There was a problem hiding this comment.
@dago how come these builds run on PR branch like this? The autobuilds are supposed to run on master... In this case of course it turned out useful since the solaris builds in the CI didn't spot this problem but the autobuilds one did!
There was a problem hiding this comment.
@bagder The builds are actually triggered by the GitHub hook and that one seems to be configured to pick up pull requests too. I vaguely remember I changed this from separate triggers (one poll, one trigger) to make the code easier and this looks like an artifact from that. Is the current configuration acceptable? It should be possible to set up a branch filter for autobuilds if needed.
... so that runtests can skip individual test cases that test features
that are explicitly disabled in this build. This new logic is intended
for disabled features that aren't otherwise easily visible through the
curl_version_info() or other API calls.
tests/server/disabled is a newly built executable that will output a
list of disabled features. Outputs nothing for a default build.