Re: [boost] [build] Headers rule does both too much and too little

Subject: Re: [boost] [build] Headers rule does both too much and too little
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2014-02-18 17:54:06

AMDG

On 02/18/2014 02:07 PM, Peter Dimov wrote:
> Steven Watanabe wrote:
> 
>> Are the testers using incremental builds?
> 
> I don't think so. This run, for example:
> 
> http://www.boost.org/development/tests/develop/developer/output/teeks99-02e-win2008-64on64-boost-bin-v2-libs-smart_ptr-test-allocate_shared_alloc11_test-test-msvc-12-0-debug.html
> 
> 
> is apparently using an old version of shared_count.hpp, and there's no
> yellow i.
> 

This tester is using --force-update, which could
also be a problem.

> This one:
> 
> http://www.boost.org/development/tests/develop/developer/output/VC8%20jc-bell-boost-bin-v2-libs-smart_ptr-test-allocate_shared_alloc11_test-test-msvc-8-0-debug.html
> 
> 
> fails due to a missing config/user.hpp. Doesn't appear incremental as well.
> 

This one we've discussed on the testing list.
Summary: The regression test system's cleanup
command is deleting a large number of headers,
because git doesn't know about junctions (git
clean treats a junction as an ordinary
directory and deletes the contents).

> This one:
> 
> http://www.boost.org/development/tests/develop/developer/output/DebSidC++-boost-bin-v2-libs-assert-test-assert_exp_test-test-gcc-4-8-2~11-debug.html
> 
> appears to be using an old version of assert.hpp.
> 

--force-update here too.

In Christ,
Steven Watanabe