I've gone ahead and dropped the gcc test build and switched the coverage
test to gcc. If we find in time that clang's speed is really an issue
compared to its better error messages we can swap the compilers' roles.
On Sun, 26 Mar 2017 at 04:31 Nick Coghlan wrote:
> On 26 March 2017 at 03:54, Ant
On 26 March 2017 at 03:54, Antoine Pitrou wrote:
>
> Le 25/03/2017 à 16:27, Nick Coghlan a écrit :
>>
>> However, from the point of view of making it easier for Windows devs to
>> debug *nix debug errors, it probably makes more sense to use clang for
>> the main *nix test run, and then use gcc to
Le 25/03/2017 à 16:27, Nick Coghlan a écrit :
>
> However, from the point of view of making it easier for Windows devs to
> debug *nix debug errors, it probably makes more sense to use clang for
> the main *nix test run, and then use gcc to do the coverage run.
What's the problem exactly? Situat
On 25 March 2017 at 02:24, Brett Cannon wrote:
> Another option is if we drop a compiler from a debug build we can use it
> for the coverage run so it's at least being exercised somewhere.
>
> If we drop either compiler I would vote for dropping gcc actually as the
> compiler messages are much wo
Even if for most changes, testing gcc and clang is useless, I'm in
favor of keeping both for the CI. It doesn't cost much, and it's not
that uncommon that Clang catchs bugs or warnings, than GCC doesn't.
The question is more who checks for compiler warnings in the CI :-)
Currently, you have to dig
On Fri, 24 Mar 2017 at 06:43 Antoine Pitrou wrote:
>
> Hello,
>
> I am curious about the decision to have Travis-CI tests with both clang
> and gcc.
It was when I was trying to maximize Travis usefulness before the
migration. It's also because we as a project have found bugs in both
compilers p
Hello,
I am curious about the decision to have Travis-CI tests with both clang
and gcc. clang is a compiler which strives to be very compatible with
gcc. I would understand testing under OS X with clang in addition to
Linux with gcc, but I'm skeptical we gain much from testing both gcc and
clan
