Re: [Boost-build] Recent commits broke the link-fail testing on Windows

Subject: Re: [Boost-build] Recent commits broke the link-fail testing on Windows
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2018-01-16 00:49:37

AMDG

On 01/15/2018 03:37 PM, Antony Polukhin wrote:
> 2018-01-15 18:36 GMT+03:00 Steven Watanabe via Boost-build
> <boost-build_at_[hidden]>:
> <...>
>> Just to validate, I changed link-fail to link and it passed.
> 
> I've also changed the `link-fail` to `link` and it failed:
> Commit https://github.com/apolukhin/type_index/commit/5bc4f54183b1e37da0623af6f77a65f4c76bcaa9
> CI run https://ci.appveyor.com/project/apolukhin/type-index/build/1.64.50-develop
> 
> Then I restored the `link-fail`, and the build still fails:
> Commit: https://github.com/apolukhin/type_index/commit/727cdadc86cd63d86420f70ffc00c39edb1dc2be
> CI run https://ci.appveyor.com/project/apolukhin/type-index/build/1.64.51-develop
> 
> 
> In both cases there's a '...failed updating 2 targets...' message.
> Found no other errors.
> Am I missing something?
> 
> 

  The output is wrong, but the exit status is correct.
It looks like you fixed one of the failures.  When
you fix link_fail_rtti_nortti as well, the exit status
should be 0.  I'll see what I can do about the output,
but for now, you can just ignore errors where the
'...failed' line names the .pdb file.

In Christ,
Steven Watanabe