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

Subject: Re: [Boost-build] Latest b2 on trunk always rerunning tests
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2013-11-06 12:48:45

AMDG

On 11/06/2013 09:34 AM, Edward Diener wrote:
> 
> 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,

Sure.  If it's large, you should compress it
and send it off-list.

> or explain to me what I should be looking for to determine
> this ?
> 

- Find the entry for the test case
- look at its dependencies and find one that
  is being updated
- find the entry for this target and check
  /its/ dependencies
- repeat until you reach a leaf

> 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.
> 

In Christ,
Steven Watanabe