Re: [boost] ATTN: Beman / Eric (was Re: [1.37] status/Jamfile.v2)

Subject: Re: [boost] ATTN: Beman / Eric (was Re: [1.37] status/Jamfile.v2)
From: Eric Niebler (eric_at_[hidden])
Date: 2008-10-20 12:55:46

CC'ing Rene ...

Nicola Musatti wrote:
> Eric Niebler <eric <at> boost-consulting.com> writes:
> 
>> Nicola Musatti wrote:
>>> Hallo,
>>> sorry to insist, but I think this should go in rather sooner than later.
>> Thanks for the head-up Nicola. Some questions below ...
>>
>>> Nicola Musatti wrote:
>>>> Nicola Musatti wrote:
>>>>> Hallo,
>>>>> I believe the Jamfile.v2 in the status directory should be merged
>>>>> to the release branch. The one that's there looks older than the
>>>>> directory reorganization that was performed a while ago,
>> What makes you say that? The tests on the release branch have been 
>> running successfully.
> 
> I'm not sure where the difference is between how the official regression tests
> are run and how local testing is performed. If I run bjam from the boost/status
> directory in a sandbox checked out from branches/release with a command line as
> the following:
> 
> bjam -a --v2 --dump-tests toolset=borland-6.1.0
> 
> The tests for the libraries I listed below aren't run.

But from the release test results here:

http://beta.boost.org/development/tests/release/developer/summary.html

it appears these tests are in fact getting run.

>>>>> and it doesn't include the tests for several libraries.
>> Which ones?
>>
>>>> No, it's much worse than that. I suspect that several libraries' test 
>>>> directories need to be merged to release:
>>>> - array
>>>> - crc
>>>> - functional
>>>> - integer (?)
>>>> - preprocessor (?)
>>>> - rational
>>>> - utility/swap
>>>>
>>>> Let me know if you need any help with this.
>> How did you come up with this list? It's really up to the authors of 
>> those libraries whether to merge to release or not, right?
> 
> I started by comparing the test results I get by running
> process_jam_log/compiler_status on trunk and on branches/release and noticed
> that the latter was missing a few results. I then compared the corresponding
> libraries' directories under boost/libs and noticed that a few of them were
> lacking their respective test subdirectory, while others had other
> discrepancies. I can't reach my testing environment right now, but if I remember
> correctly array, crc, functional/hash and rational all lack their test
> directory, preprocessor is lacking its test/Jamfile.v2 file and utility/swap is
> completely missing from the release branch. Concerning this last issue I took
> the liberty of mailing utility/swap's author to remind him about the need of
> merging.

But looking at the status/Jamfile.v2 on the release branch, none of 
these are issues. These libraries don't follow the normal boost 
convention of having a test directory with a Jamfile.v2 in it; rather, 
the tests are invoked directly from the status/Jamfile.v2. And 
utility/swap which isn't part of 1.37 IIUC. Everything looks copacetic 
to me.

> I'm aware that library authors should take care of merging their libraries to
> the release branch, but some of these libraries are quite old and their authors
> may not be that active in Boost any more; I'm not even sure they were involved
> in the test reorganization. Judging from the svn logs the reorganization was
> actually performed by Rene Rivera.

It would certainly be good to sync up trunk and release after 1.37 is 
out, to avoid this confusion and to make it easier to merge changes to 
status/Jamfile.v2. In fact, I wonder why this wasn't done for 1.37 
(Rene?) but it's too late now.

-- 
Eric Niebler
BoostPro Computing
http://www.boostpro.com