Re: [boost] [gil][test] HOWTO set up the Boost testing process for projects with extra prerequisites ?

Subject: Re: [boost] [gil][test] HOWTO set up the Boost testing process for projects with extra prerequisites ?
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2017-11-17 17:26:24

On Fri, Nov 17, 2017 at 11:10 AM, Stefan Seefeld via Boost <
boost_at_[hidden]> wrote:

> On 17.11.2017 11:59, Rene Rivera via Boost wrote:
> > On Fri, Nov 17, 2017 at 10:51 AM, Stefan Seefeld via Boost <
> > boost_at_[hidden]> wrote:
> >
> >> Or have I misunderstood what you are proposing ?
> >>
> > ^^ That..
> >
> > <https://github.com/boostorg/build/blob/develop/src/tools/zlib.jam#L73>
>
> OK, much better. But that doesn't answer the original question: How does
> a tester need to set up his system (and configure the build) for the GIL
> IO tests to work ?

In either case does he
>
> a) need to install additional libraries
>

Probably.

> b) add instructions (no matter whether it's a `-s...` command line
> option or an entry in the `user-config.jam` file) to locate them.
>

Like in my other email.. Add to their user-config.jam where/how to get
those libraries.

> So with our current process we need to make all testers aware of that,
> or else the GIL tests will fail.

Right.

> (And no, I don't consider testing with
> in-process-built-prereq libs an option, as that doesn't represent the
> world that our users live in).
>

It represents some percentage of users. For example game devs build just
about all the libraries they depend on. I suspect so does the trading
field. And anything that is embedded or close to it. But I understand what
you meant when you said "users" ;-)

> It's this existing practice that leads to a lot of noise in the test
> matrix (at least for the Boost.Python tests), as there are a ton of test
> runs that simply aren't set up correctly, and thus making it hard to
> identifying which of the many test failures are significant and should
> be acted upon by developers, rather than ignored.
>

Couldn't tell you if that's true or not. As I haven't looked at other devs
libraries. All I can say is that it's my responsibility to make sure my
library gets tested appropriately. Which includes bugging the testers for
appropriate setups and fixes. And making sure anything I depend on is
available and/or that I can adjust to it being there.

-- 
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net