This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author db3l
Recipients db3l, loewis, pitrou
Date 2013-05-08.18:59:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1368039591.8.0.755097579837.issue17935@psf.upfronthosting.co.za>
In-reply-to
Content
Yeah, the XP buildbot was pretty old, at nasm 2.02, so I updated to the same 2.09 as the Win7 buildbot, restarted the last build and it went through compilation fine.

However, then it failed in test_ssl, and in checking, it looks like my Win7 buildbot is failing the same way.  I thought it might just be an independent problem, but then found issue 15172 from last June (like Jeremy I have 2.09.02) which seems to say OpenSSL 1.0.1+ needs nasm 2.10.  In Jeremy's case it only affected his 64-bit build, so maybe that's why I haven't seen it yet, but perhaps with the recent move to 1.0.1d it can affect 32-bit as well?

Ah, or wait, there's also issue 17425 that seems to indicate 1.0.1d may be at fault for that test failure.

Anyway, I installed the latest nasm 2.10.07 both both XP and Win7, and flushed the openssl tree in the 3.3 and 3.x build branches.  In retrying the XP 3.x build it still fails test_ssl, so I don't think there's anything else I can change on the buildbot side as it looks like fixing that needs us to switch to 1.0.1e
History
Date User Action Args
2013-05-08 18:59:51db3lsetrecipients: + db3l, loewis, pitrou
2013-05-08 18:59:51db3lsetmessageid: <1368039591.8.0.755097579837.issue17935@psf.upfronthosting.co.za>
2013-05-08 18:59:51db3llinkissue17935 messages
2013-05-08 18:59:51db3lcreate