Subject: Re: [Boost-build] Recent commits broke the link-fail testing on Windows
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2018-01-15 23:38:57
On 01/15/2018 03:37 PM, Antony Polukhin wrote:
> 2018-01-15 18:36 GMT+03:00 Steven Watanabe via Boost-build
>> 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?
I think I see what's going on. It seems that
msvc.link produces a .PDB file in addition to
the exe and the pdb is not marked as FAIL_EXPECTED,
so there's always an error one way or the other.
Now, to figure out how this passed my tests...
(Notice that the 2 targets that fail with `link`
are not the same 2 targets that fail with
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk