Boost logo

Boost Testing :

Subject: Re: [Boost-testing] [urgent] Testing help needed..
From: Tom Kent (lists_at_[hidden])
Date: 2013-12-29 18:47:46

On Sun, Dec 29, 2013 at 2:41 PM, Rene Rivera <grafikrobot_at_[hidden]> wrote:
> I finally have the changes to the regression scripts sufficiently complete
> that I've managed to do a few minimal cycles of regression testing from the
> git repos. I now need some help in various ways:
> 1. General testing..
> I need some of the regular testers to do runs with their setups with the new
> scripts. To test I suggest starting from a new testing location. And follow
> the usual instructions except get the script from
> <>.
> The options are exactly the same as the SVN version of the scripts (the
> --tag is mapped to master or develop as needed). If you run patch scripts
> you will have to adjust paths for the new arrangement. In particular the
> boost tree is now checked out to <testing-root>/boost_root.

On Ubuntu, I get:

export id=a
export tools=gcc-4.8

tomkent_at_todd08:~/teeks99-09test/a$ python
--runner=teeks99-09${id}-Ubuntu12.04-64 --toolsets=${tools}
--force-update --bjam-options=-j2 --comment=../info.html 2>&1 | tee
# Running regressions in /home/tomkent/teeks99-09test/a...
# Creating regression scripts at
# Dowloading regression scripts from
# Getting Boost.Build v2...
error: unknown option `single-branch'
usage: git clone [options] [--] <repo> [<dir>]

    -v, --verbose be more verbose
    -q, --quiet be more quiet
    --progress force progress reporting
    -n, --no-checkout don't create a checkout
    --bare create a bare repository
    --mirror create a mirror repository (implies bare)
    -l, --local to clone from a local repository
    --no-hardlinks don't use local hardlinks, always copy
    -s, --shared setup as shared repository
    --recursive initialize submodules in the clone
    --recurse-submodules initialize submodules in the clone
    --template <template-directory>
                          directory from which templates will be used
    --reference <repo> reference repository
    -o, --origin <name> use <name> instead of 'origin' to track upstream
    -b, --branch <branch>
                          checkout <branch> instead of the remote's HEAD
    -u, --upload-pack <path>
                          path to git-upload-pack on the remote
    --depth <depth> create a shallow clone of that depth
    --separate-git-dir <gitdir>
                          separate git dir from working tree
    -c, --config <key=value>
                          set config inside the new repository

Traceback (most recent call last):
  File "", line 83, in <module>
  File "/home/tomkent/teeks99-09test/a/tools_regression_src/",
line 253, in __init__
  File "/home/tomkent/teeks99-09test/a/tools_regression_src/",
line 632, in main
  File "/home/tomkent/teeks99-09test/a/tools_regression_src/",
line 570, in command_regression
  File "/home/tomkent/teeks99-09test/a/tools_regression_src/",
line 282, in command_get_tools
  File "/home/tomkent/teeks99-09test/a/tools_regression_src/",
line 905, in git_checkout
    git_root_subdir )
  File "/home/tomkent/teeks99-09test/a/tools_regression_src/",
line 880, in git_command
    raise Exception( 'GIT command "%s" failed with code %d' % (git_cli, rc) )
Exception: GIT command "'git' 'clone' '--depth' '1' '--branch'
'develop' '--single-branch' ''
'tools_bb'" failed with code 33024

Boost-testing list run by mbergal at