Subject: Re: --enable-tests configure option?

Re: --enable-tests configure option?

From: Brad House <brad_at_brad-house.com>
Date: Fri, 31 Jul 2020 07:26:35 -0400

>> The problem is c-ares, though a C library, relies on gmock, a C++11 testing framework. We cannot guarantee there is a C++ compiler or that it supports C++11 or higher.
>>
>> I don't have experience with gmock.
>>
>> I think you need some sort of testing. Right now, I cannot test with
>> Asan, UBSan, Coverity or Enterprise Analysis. That is a major handicap
>> for the library.
>>
>> Can you re-write the self tests and avoid the dependency?
>>
>> I'm not sure what you're saying exactly. There's a fully functional test suite. No, it won't be rewritten to not depend on gmock. I was just explaining why it wasn't enabled by default. If you look at our Travis-CI builds, it runs the test suite under ASAN, UBSAN, clang static analyzer, and valgrind.
> If I am parsing
> https://travis-ci.org/github/c-ares/c-ares/builds/709496849 correctly,
> c-ares is missing platforms.
>
> Can you at least add OS X, arm64, ppc64 and s390x?

Do you know of any CI providers that have build systems that cover those?

We are doing OSX on travis but the other systems aren't available on travis.
Received on 2020-07-31