Re: [boost] Master Regression Tests Failing

Subject: Re: [boost] Master Regression Tests Failing
From: Vicente J. Botet Escriba (vicente.botet_at_[hidden])
Date: 2017-10-11 07:15:10

Le 11/10/2017 à 08:26, Vicente J. Botet Escriba a écrit :
> Le 10/10/2017 à 20:23, Rene Rivera via Boost a écrit :
>> On Tue, Oct 10, 2017 at 1:00 PM, Vicente J. Botet Escriba <
>> vicente.botet_at_[hidden]> wrote:
>>
>>> Le 10/10/2017 à 16:48, Rene Rivera via Boost a écrit :
>>>
>>> On Mon, Oct 9, 2017 at 10:45 AM, Peter Dimov via Boost 
>>> <boost_at_[hidden]> wrote:
>>>
>>>
>>> Tom Kent wrote:
>>>
>>>
>>> It appears that we haven't had any successful runs of the regression
>>> tests on master since last Friday afternoon. Looking at some logs, I'm
>>> seeing output like below. Any ideas?
>>>
>>>
>>> ...
>>>
>>>
>>> notice: [lzma] Condition
>>> /var/boost/run/boost_bb/src/build/feature.jam:140: in feature.feature
>>> from
>>> module feature
>>> error: feature already defined:
>>> error: in feature declaration:
>>> error: feature "threadapi" : "pthread" "win32" : "propagated"
>>>
>>>
>>> Looks like you're using the develop Boost.Build. It contains a 
>>> change that
>>> requires two other corresponding patches, to Thread and the 
>>> superproject.
>>>
>>>
>>> I change B2 so that it avoids the error.
>>>
>>>
>>> Did you mean Rene that we don't need to merge the 3 changes on Build,
>>> Boost and Thread?
>>>
>> Correct. The master testing can use the current develop B2. But 
>> obviously
>> merging those others will need to be coordinated.
>>
> Rene, it seems the develop branch is broken now.
>
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/286174190/log.txt?X-Amz-Expires=29&X-Amz-Date=20171011T062304Z&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJRYRXRSVGNKPKO5A/20171011/us-east-1/s3/aws4_request&X-Amz-SignedHeaders=host&X-Amz-Signature=b583d978a3467ef38a48039024e554307f9f77af0cde554315902129fbdc94b7 
>
>
> https://ci.appveyor.com/project/viboes/thread/build/1.0.141-feature/timespec_clocks/job/q1kxy8an0p5u1fre 
>
>
>
> Have you changed something in develop?
Sorry, I believe this PR was related to develop, and it was for the 
branch timespec_clocks, which is not yet synchronized with develop :(

Best,
Vicente