Re: [boost] [release] Python 3 build problems

20 Apr 2015


      On Mon, Apr 20, 2015 at 9:12 AM, Rene Rivera  wrote:
...
On Mon, Apr 20, 2015 at 8:53 AM, Tom Kent  wrote:
...
On Fri, Apr 17, 2015 at 1:51 PM, Rene Rivera 
wrote:
...
On Apr 17, 2015 1:27 PM, "Stefan Seefeld"  wrote:
...
On 17/04/15 02:22 PM, Rene Rivera wrote:
...
On Apr 17, 2015 1:03 PM, "Stefan Seefeld" 
...
...
...
PS: It's a pitty that none of the test builders indicate what
Python
...
...
version they are running with. That would have been valuable
information
for Boost.Python tests.
If it's important you should add an informational test that shows
wrote:
the
...
...
Python version being tested.
While that might work, it seems a bit hackish to me. It seems the
Python
version (as well as a number of other config parameters) are valuable
metadata associated with a given build that would be useful to
display,
alongside the compiler name / version in use.
It's actually the less hackish way. As it handles the eventuality that
the
version of Python that the tools are using will be different than the
one
being tested for BPL. And would also account for multiple versions being
tested in the same b2 run.
I'd agree with this, if we can make it part of the test.
However, it might be nice to include some more information automatically
in
the comment html file, just like we do with the command that is executed.
For debugging purposes it might be nice to see: contents of the
user-config.jam file, version of python that run.py is executed with,
actual version of the toolsets being used (can we get this from bjam?).
I would avoid including user-config.jam or system-config.jam in the
uploaded information. They are "private" files and may contain confidential
information. And hence we would be liable for posting such information on a
publicly accessible location.
We can definitely include version information though. And maybe scrape the
--debug-configuration information from BB and put it in the info (it should
have the toolset information).
PS. If you have specific feature to add to the regression testing please
file a task in the github boostorg/regression repo <
https://github.com/boostorg/regression/issues>. So that I have a ready list
of stuff to do when I have free time.
...
-- 
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net
-- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail