Re: [boost] New B2 version, and CI failures.

Subject: Re: [boost] New B2 version, and CI failures.
From: Antony Polukhin (antoshkka_at_[hidden])
Date: 2019-04-14 18:01:57

On Sun, Apr 14, 2019, 16:40 Rene Rivera <grafikrobot_at_[hidden]> wrote:

> On Sun, Apr 14, 2019 at 8:33 AM Rene Rivera <grafikrobot_at_[hidden]> wrote:
>
>> On Sun, Apr 14, 2019 at 1:54 AM Antony Polukhin <antoshkka_at_[hidden]>
>> wrote:
>>
>>>
>>>
>>> On Sat, Apr 13, 2019, 23:17 Rene Rivera via Boost <boost_at_[hidden]>
>>> wrote:
>>>
>>>> Well, that's interesting, and strange given that such a label does
>>>> exist <
>>>>
>>>> https://github.com/boostorg/build/blob/develop/src/engine/config_toolset.bat#L57
>>>
>>>
>>> Same issue with variant. Note that there's one successful build
>>> https://ci.appveyor.com/project/apolukhin/variant-ykfti/builds/23831018
>>> . Comparing the environments of failed and succeeded builds may be helpful
>>> in locating the issue.
>>>
>>
>> So... There's something weird in the Appveyor VS 2013 image that is not
>> present in the VS 2015 or 2017 images.
>>
>
> My suggestion would be to switch all those 2013 images to the 2015 images.
> It has all the same versions of compilers.
>

This may work, however having an unknown issue in the b2 code makes me
nervous. This issue could fire on a user device at some inappropriate time
(during release candidate testing for example).

>