In article ,
Ned Deily wrote:
> In article ,
> Zvezdan Petkovic wrote:
> > So, the problem was introduced between February 11 and 2.6.5rc1 release.
> > This is a regression.
> Yes, and I now have a hunch what triggered it. I'll report back.
Yep, found it. It was a test failure side-effect of
In article ,
Zvezdan Petkovic wrote:
> I can confirm the same test failures on the same platform.
Sorry, I didn't see your reply here until after I had sent my most
recent one. I agree with your assessments. In particular:
> > test_tcl
> > 2010-03-02 14:36:19.459 python.exe[35793:60b] The a
I can confirm the same test failures on the same platform.
Configured like this:
./configure \
--prefix=${HOME}/opt \
BASECFLAGS="-arch x86_64 -arch i386" \
CFLAGS="-arch x86_64 -arch i386" \
LDFLAGS="-arch x86_64 -arch i3
I should have looked at the whole test output before my previous
post; there are other test failures, or at least "unexpected
output." The full output, up to the crash(?), is at this pastie:
http://www.pastie.org/850452
The troublesome parts are excerpted in part below.
-Tom
test_asynchat
te
