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.

classification
Title: test_ssl failure
Type: behavior Stage: resolved
Components: Tests Versions:
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: neologix, pitrou
Priority: normal Keywords: buildbot

Created on 2013-04-05 07:44 by neologix, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (3)
msg186066 - (view) Author: Charles-François Natali (neologix) * (Python committer) Date: 2013-04-05 07:44
test_ssl is failing on one the NetBSD buildbots:
http://buildbot.python.org/all/builders/x86%20NetBSD%205.1.2%20%5BSB%5D%203.x/builds/1129/steps/test/logs/stdio

"""
======================================================================
ERROR: test_options (test.test_ssl.ContextTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/cpython/buildslave/3.x.snakebite-netbsd51-x86-1/build/Lib/test/test_ssl.py", line 87, in f
    return func(*args, **kwargs)
  File "/home/cpython/buildslave/3.x.snakebite-netbsd51-x86-1/build/Lib/test/test_ssl.py", line 420, in test_options
    ctx.options = (ctx.options & ~ssl.OP_NO_SSLv2) | ssl.OP_NO_TLSv1
ValueError: can't clear options before OpenSSL 0.9.8m
"""

Antoine, I think I saw commits from you some time ago to deal with this SSL version thing...
msg186067 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2013-04-05 08:45
Well, that exception is raised when the OpenSSL version doesn't have the HAVE_SSL_CTX_CLEAR_OPTIONS macro, which appeared in 0.9.8m. But the OpenSSL version on that buildbot identifies itself as "OpenSSL 0.9.9-dev 09 May 2008", which is logically posterior to 0.9.8m. I don't know how to handle this in a non-hackish way, except by just ignoring the issue :-)
msg186137 - (view) Author: Charles-François Natali (neologix) * (Python committer) Date: 2013-04-06 16:41
> I don't know how to handle this in a non-hackish way, except by just ignoring the issue :-)

Sound fine to me :)
History
Date User Action Args
2022-04-11 14:57:43adminsetgithub: 61838
2013-04-06 16:41:06neologixsetstatus: open -> closed
resolution: not a bug
messages: + msg186137

stage: resolved
2013-04-05 08:45:50pitrousetmessages: + msg186067
2013-04-05 07:44:40neologixcreate