Subject: Re: [boost] [gil] Ok to merge new gil's extension to release branch?
From: Christian Henning (chhenning_at_[hidden])
Date: 2013-04-13 11:16:50
On Sat, Apr 13, 2013 at 10:44 AM, Steven Watanabe <watanabesj_at_[hidden]>wrote:
> On 04/13/2013 07:23 AM, Christian Henning wrote:
> >> Anything listed in test_all.py should work.
> >>> I'll try again tonight. But do you have any idea for what I should look
> >> for when something isn't working? I know I can run normal python
> >> So it has to do something with the test cases..
> > So I run test_all.py. Here is the stdout:
> > http://pastebin.com/PtjKvdgb
> > and here is the stderr:
> > http://pastebin.com/V6CF0uFK
> > It's somewhat funny that zlib.py is the only test passing. Does that
> > ring a bell?
> Unfortunately, test_all.py doesn't show the actual errors.
> The tests appear to be passing for the Windows test runners:
> Can you try core_language.py? It's the most basic test.
> If it fails, I wouldn't expect anything to work.
According to the output the error happens testcmd.py at line 409. I added
some debug code:
sys.stdout.write( "CHH: " + str( cmd ) + "\n")
sys.stdout.write( "CHH: " + chdir + "\n")
sys.stdout.write( "CHH: " + str( universal_newlines ) + "\n")
and the output is:
_BUILD_PATH="c:\\boost\\tools\\build\\v2\\test/.."', '-d0', '--quiet',
Does that look reasonable?