Boost logo

Boost :

Subject: Re: [boost] [test] boost.test owner unresponsive to persistent problems for multiple years
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2015-03-18 13:45:56


> -----Original Message-----
> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Edward Diener
> Sent: 18 March 2015 17:37
> To: boost_at_[hidden]
> Subject: Re: [boost] [test] boost.test owner unresponsive to persistent problems for multiple
years
>
> On 3/18/2015 12:15 PM, Paul A. Bristow wrote:
> >> -----Original Message-----
> >> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of
> >> Edward Diener
> >> Sent: 18 March 2015 15:37
> >> To: boost_at_[hidden]
> >> Cc: boost-users_at_[hidden]
> >> Subject: Re: [boost] [test] boost.test owner unresponsive to
> >> persistent problems for multiple
> > years
> >>
> >>>> It does not appear that the 'develop' branch is ready for me at all.
> >>>
> >>> This is the location of the new documentation:
> >>>
> >>> http://www.boost.org/doc/libs/develop/libs/test/doc/html/index.html
> >> Thanks, I was able to build the docs and view them from the top-level index.html.
> >>
> >> Still the top-level jam file build should not be failing as it is doing in the 'develop'
branch.
> >
> > I have built all the libraries, including test, from a recent clone of
> > the whole modular-boost tree (as per getting started instructions
> > apart from adding my choice of address-model and choosing
> > asynch-exceptions:
> > b2 address-model=32 architecture=x86 asynch-exceptions=on
> > )
> >
> > and can test things as expected.
> >
> > So that's pretty much 'works-for-me' ;-)
> >
> > And I think it would help if others can confirm this - thus reducing
> > any risk from moving develop to master for the next release.
>
> Am I supposed to be getting the latest Boost Build on 'develop' to do this ?

That was my suggestion - to try to find any remaining bugs only detectable by user (ab)use ;-)

Paul

---
Paul A. Bristow
Prizet Farmhouse
Kendal UK LA8 8AB
+44 (0) 1539 561830

Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk