Re: [boost] [build][testing] Auto-generated tests not present in reports

Subject: Re: [boost] [build][testing] Auto-generated tests not present in reports
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2014-03-24 14:17:03

On Mon, Mar 24, 2014 at 8:44 PM, Steven Watanabe <watanabesj_at_[hidden]> wrote:
> AMDG
>
> On 03/24/2014 09:16 AM, Andrey Semashev wrote:
>> <snip>
>>           all_rules += [ compile compile/self_contained_header.cpp :
>> <define>"BOOST_LOG_TEST_HEADER=$(rel_file)" :
>> self_contained_header/$(rel_file) ] ;
>> <snip>
>>
>> It works locally, I can see the generated tests for all headers being
>> compiled. However, I made this change quite some time ago but still I don't
>> see these tests in the test reports table. I can see other tests which are
>> generated by the same test_all rule, so it works. What could be the problem?
>> Any ideas?
>>
>
> I suspect that the extra nesting is confusing
> the test scripts.  If that's the case, it will
> probably work if you avoid using '/' in the
> test name.

The problem is the headers are in multiple subfolders inside
boost/log, so if I remove the directory, name clashes will appear. For
instance, there are boost/log/core/record.hpp and
boost/log/expressions/record.hpp.

I could try replacing '/' with some other delimiter. Any suggestions
on a safe replacement candidate?

Also, another idea. Is it possible that $(BOOST_ROOT) is not defined
by testers? If so, is there a bullet proof way to know the root of
Boost checkout or my library?