Boost logo

Boost-MPI :

Subject: Re: [Boost-mpi] [EXTERNAL] master vs develop
From: Alain Miniussi (alain.miniussi_at_[hidden])
Date: 2014-11-19 04:10:55

On 19/11/2014 09:20, Alain Miniussi wrote:
> On 19/11/2014 08:57, Alain Miniussi wrote:
>> Hi Noel,
>> Thank for the infos.
>> No, I am not familiar with the boost testing pages, could you point
>> me to some informations ?
> I think I found them:
> I'm looking into it.

Running python ./ --runner=miniussi --toolsets=intel-linux
fails with:

[alainm_at_gurney boost]$ python ./ --runner=miniussi
--toolsets=intel-linux --tag=master
# Running regressions in /gpfs/scratch/alainm/view/boost...
# Creating regression scripts at
# Copying regression scripts from
# Getting Boost.Build v2...
# Executing SVN command "svn --non-interactive co tools_bb"
Checked out revision 86799.
# Getting Boost.Jam...
# Executing SVN command "svn --non-interactive co tools_bjam"
svn: URL ''
doesn't exist
Traceback (most recent call last):
   File "./", line 83, in <module>
line 205, in __init__
line 566, in main
line 504, in command_regression
line 249, in command_get_tools
     os.path.basename(self.tools_bjam_root) ) )
line 798, in svn_command
     raise Exception( 'SVN command "%s" failed with code %d' % ( cmd, rc ) )
Exception: SVN command "svn --non-interactive co tools_bjam"
failed with code 256
[alainm_at_gurney boost]$

there is a missing v2 in
Note that I did not use the -use-svn option, yet the script does not
uses git as I would expect by looking at the script.


> Thanks
>> I was only able to find a mailing list
>> (
>> I guess I can contribute for those two libraries, at least on our
>> supported platform (linux/intel).
>> Thanks
>> Alain
>> On 19/11/2014 06:11, Belcourt, Kenneth wrote:
>>> Hi Alain,
>>> On Nov 18, 2014, at 3:48 AM, Alain Miniussi <>
>>> wrote:
>>>> I have a question regarding:
>>>> I guess that all the commit, specially the pull requests, listed
>>>> are those that made their way to develop but not to master.
>>>> What is the protocol/usage for having the stuff on the develop
>>>> branch merge onto the master branch ?
>>> Generally I’ve been waiting for testing to cycle for a while before
>>> merging changes to master.
>>>> I guess the stuff on develop is already considered as being
>>>> validated in some way, so what is needed for the next step ? does
>>>> some testing report need to be produced ? on a specific set of
>>>> platform ?
>>> Since very few people test Boost MPI on develop or master, I try to
>>> be very cautious with commits to develop and merges to master. It’s
>>> kinda easy to break things and, given the scarcity of MPI and Graph
>>> Parallel testers, I prefer to test the PR’s, develop and master
>>> branches on internal resources to ensure I don’t hit any problems
>>> before I push them to github.
>>> Are you familiar with the Boost testing pages? Can you contribute
>>> any testing resouces to specifically test MPI and Graph Parallel?
>>>> Also, does everything that is in master supposed to go
>>>> automagically in the next release ?
>>> Generally yes, everything in master goes into the release, that’s
>>> why we’re careful about what ends up in master.
>>> — Noel
>>> _______________________________________________
>>> Boost-mpi mailing list
>>> Boost-mpi_at_[hidden]


Boost-Commit list run by troyer at