[prev in list] [next in list] [prev in thread] [next in thread] 

List:       boost-testing
Subject:    [Boost-testing] Abbreviate Paths option also shortens toolset reported
From:       Tom Kent <lists () teeks99 ! com>
Date:       2016-06-30 2:39:42
Message-ID: CAArKS8hDGXT3XOndGyZoLcHv608-y2TXVy-_sDYwr_r8JJ43JQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


When running the regression test suite, with a command like:
python run.py --runner=teeks99-tmp --toolsets=gcc-6~cpp11~O2
--bjam-options="-j2 address-model=64 --abbreviate-paths
--remove-test-targets" --comment=info.html --tag=develop

I see that the --abbreviate-paths option to b2 causes the path not to have
the whole toolset in it (good), however, when the results are reported the
toolset that shows up there is also the abbreviated version. I would expect
that column header to match the toolset that was specified as an option to
run.py. Is this intentional? Thoughts?

Tom

[Attachment #5 (text/html)]

<div dir="ltr">When running the regression test suite, with a command like:<br>python \
run.py --runner=teeks99-tmp --toolsets=gcc-6~cpp11~O2 --bjam-options=&quot;-j2 \
address-model=64 --abbreviate-paths --remove-test-targets&quot; --comment=info.html \
--tag=develop<br><div><br></div><div>I see that the --abbreviate-paths option to b2 \
causes the path not to have the whole toolset in it (good), however, when the results \
are reported the toolset that shows up there is also the abbreviated version. I would \
expect that column header to match the toolset that was specified as an option to \
run.py. Is this intentional? Thoughts?</div><div><br></div><div>Tom</div></div>



_______________________________________________
Boost-Testing mailing list
Boost-Testing@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

[prev in list] [next in list] [prev in thread] [next in thread]