Subject: Re: [Boost-gil] Multi-compiler testing on CircleCI (and channel bug)
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2018-04-06 13:49:31
On 06.04.2018 09:41, Mateusz Loskot wrote:
> On 6 April 2018 at 14:30, Stefan Seefeld <stefan_at_[hidden]> wrote:
>> On 06.04.2018 05:18, Mateusz Loskot wrote:
>>> Although it may seem unnecessary or superfluous, I decided
>>> to test wide range of compilers after I noticed some versions reproduce
>>> the channel  tests are failing for some versions and I couldn't see
>>> the pattern.
>>> So, I suggest we keep testing against range of GCC/clang versions,
>>> at least until all CI the builds become perfectly and constantly green :)
>> Fair enough. But once we get there, I think we should split the test
>> configs in "essential" ones that really are to be performed on each
>> check-in, and everything else that we may want to trigger manually. (If
>> we were using BuildBot for this, I'd suggest some clever tricks to
>> reduce overhead, such as first running a single test config, and only if
>> that passes run everything else. Having ~20 test runs perform in
>> parallel only to then notice a single stupid typo is really wasteful.)
> Yes, I will optimise the CircleCI workflow to complement Travis CI
> and not duplicate it.
> There is variety of possibilities,
> - define dependencies between build jobs
> eg. builds: build 4.7, if OK, build 4.8, if OK, build 4.9, etc.
> and within each compiler/version line, build core tests, if OK, build extension
> and within each set of tests, build variant=debug first, if OK, build
> - only schedule builds eg. once a day
> However, that can be discussed once the issues/warnings are cleaned.
Exactly. In the meantime, it's indeed a great help to have this much
better coverage. So many thanks for working on the CI stuff !
-- ...ich hab' noch einen Koffer in Berlin...
This archive was generated by hypermail 2.1.7 : 2018-04-12 20:05:06 UTC