Re: [Boost-testing] [EXTERNAL] [boost] [modular] and status/explicit-failures-markup.xml

Subject: Re: [Boost-testing] [EXTERNAL] [boost] [modular] and status/explicit-failures-markup.xml
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2014-02-10 12:16:58

AMDG

On 02/10/2014 08:59 AM, Belcourt, Kenneth wrote:
> 
> This is strange.  When we run tests we dump out the list of tests to run.  Notice the container example and test testsuites are listed under container directly whereas bench is in a subdirectory under container.  I have no idea why that's happening but I'd guess that's the source of the bench results not appearing, the source locations are fine.
> 
> ….
> boost-test(RUN) "container/bench/bench_set_avl" : "libs/container/bench/bench_set_avl.cpp"
> <snip>
> ….
> boost-test(RUN) "container/doc_extended_allocators" : "libs/container/example/doc_extended_allocators.cpp"
> <snip>
> 
> Any idea why bench test targets show up under container/bench, but not the example and test targets?
> 

testing.jam know about the test/ and example/ subdirectories.

local rule get-library-name ( path )
{
    # Path is in normalized form, so all slashes are forward.
    local match1 = [ MATCH /(tools|libs)/(.*)/(test|example) : $(path) ] ;
#...

In Christ,
Steven Watanabe