Re: [Boost-build] Latest b2 on trunk always rerunning tests

Subject: Re: [Boost-build] Latest b2 on trunk always rerunning tests
From: Edward Diener (eldiener_at_[hidden])
Date: 2013-11-06 12:34:30

On 11/6/2013 11:22 AM, Steven Watanabe wrote:
> AMDG
>
> On 11/06/2013 08:08 AM, Edward Diener wrote:
>> On 11/6/2013 4:21 AM, Vladimir Prus wrote:
>>>
>>> I don't see this on trunk, when running b2 in libs/program_options/test;
>>> I'm on Ubuntu. Can you see whether the problem exists in that
>>> directory as well, for you?
>>
>> It exists in that directory as well when running b2 in Windows. I will
>> try it in Linux to see if the same problem occurs.
>>
>
> I'm running with trunk_at_86572 on Windows and I
> don't see this in libs/mpl/test.

Running a test for my own vmd library for a single particular test, 
which is always being rerun, with the -d+12 option gives a dependency 
graph. But I do not know how to intepret the dependency graph, which is 
pretty large, to determine why the test is always being rerun. Can you 
take a look at the output, if I attach it, to determine why it is always 
being rerun, or explain to me what I should be looking for to determine 
this ?

I have carefully looked at source file dates for my own header files and 
test files and they are all earlier than the dates where the output 
files are being generated. I think this may be a problem with the latest 
Boost Build, perhaps having to do with the fact that my header file 
directory in the Boost directory structure is a symbolic link, since I 
have created my non-Boost library using the new modular Boost directory 
structure.