Sorry, it seems that the missing 'v2' problem only appears when run.py
is run from a clone distribtion, not an empty one.
I'm currently stuck on the --no-tag option of git, probably a git
version problem.
On 19/11/2014 10:10, Alain Miniussi wrote:
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:
http://www.boost.org/development/running_regression_tests.html
I'm looking into it.
Running python ./run.py --runner=miniussi --toolsets=intel-linux
--tag=master
fails with:
[alainm@gurney boost]$ python ./run.py --runner=miniussi
--toolsets=intel-linux --tag=master
# Running regressions in /gpfs/scratch/alainm/view/boost...
# Creating regression scripts at
/gpfs/scratch/alainm/view/boost/tools_regression_src...
# Copying regression scripts from
/gpfs/scratch/alainm/view/boost/tools/regression/src...
# Getting Boost.Build v2...
# Executing SVN command "svn --non-interactive co
http://svn.boost.org/svn/boost/trunk/tools/build/v2 tools_bb"
Checked out revision 86799.
# Getting Boost.Jam...
# Executing SVN command "svn --non-interactive co
http://svn.boost.org/svn/boost/trunk/tools/build/engine tools_bjam"
svn: URL 'http://svn.boost.org/svn/boost/trunk/tools/build/engine'
doesn't exist
Traceback (most recent call last):
File "./run.py", line 83, in <module>
runner(root)
File
"/gpfs/scratch/alainm/view/boost/tools_regression_src/regression.py",
line 205, in __init__
self.main()
File
"/gpfs/scratch/alainm/view/boost/tools_regression_src/regression.py",
line 566, in main
getattr(self,action_m)()
File
"/gpfs/scratch/alainm/view/boost/tools_regression_src/regression.py",
line 504, in command_regression
self.command_get_tools()
File
"/gpfs/scratch/alainm/view/boost/tools_regression_src/regression.py",
line 249, in command_get_tools
os.path.basename(self.tools_bjam_root) ) )
File
"/gpfs/scratch/alainm/view/boost/tools_regression_src/regression.py",
line 798, in svn_command
raise Exception( 'SVN command "%s" failed with code %d' % ( cmd,
rc ) )
Exception: SVN command "svn --non-interactive co
http://svn.boost.org/svn/boost/trunk/tools/build/engine tools_bjam"
failed with code 256
[alainm@gurney boost]$
there is a missing v2 in
http://svn.boost.org/svn/boost/trunk/tools/build/engine
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 run.py script.
Thanks,
Thanks
I was only able to find a mailing list
(http://lists.boost.org/mailman/listinfo.cgi/boost-testing).
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 <alain.miniu...@oca.eu>
wrote:
I have a question regarding:
https://github.com/boostorg/mpi/compare/master...develop
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@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-mpi
--
---
Alain
_______________________________________________
Boost-mpi mailing list
Boost-mpi@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-mpi
