For whatever reason, AMD 64 Open Indiana ('stable' buildbot #3) is not building ctypes. test_venv fails with
FAIL: test_with_pip (test.test_venv.EnsurePipTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/export/home/buildbot/64bits/3.4.cea-indiana-amd64/build/Lib/test/test_venv.py", line 356, in test_with_pip
    with_pip=True)
subprocess.CalledProcessError: Command '['/tmp/tmp644tt7bi/bin/python', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/export/home/buildbot/64bits/3.4.cea-indiana-amd64/build/Lib/test/test_venv.py", line 362, in test_with_pip
    self.fail(msg.format(exc, details))
AssertionError: Command '['/tmp/tmp644tt7bi/bin/python', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1

**Subprocess Output**
Traceback (most recent call last):
  File "/export/home/buildbot/64bits/3.4.cea-indiana-amd64/build/Lib/runpy.py", line 170, in _run_module_as_main
    "__main__", mod_spec)
  File "/export/home/buildbot/64bits/3.4.cea-indiana-amd64/build/Lib/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/export/home/buildbot/64bits/3.4.cea-indiana-amd64/build/Lib/ensurepip/__main__.py", line 4, in <module>
    ensurepip._main()
  File "/export/home/buildbot/64bits/3.4.cea-indiana-amd64/build/Lib/ensurepip/__init__.py", line 209, in _main
    default_pip=args.default_pip,
  File "/export/home/buildbot/64bits/3.4.cea-indiana-amd64/build/Lib/ensurepip/__init__.py", line 116, in bootstrap
    _run_pip(args + [p[0] for p in _PROJECTS], additional_paths)
  File "/export/home/buildbot/64bits/3.4.cea-indiana-amd64/build/Lib/ensurepip/__init__.py", line 40, in _run_pip
    import pip
  File "/tmp/tmp7od_thjv/pip-1.5.6-py2.py3-none-any.whl/pip/__init__.py", line 9, in <module>
  File "/tmp/tmp7od_thjv/pip-1.5.6-py2.py3-none-any.whl/pip/log.py", line 9, in <module>
  File "/tmp/tmp7od_thjv/pip-1.5.6-py2.py3-none-any.whl/pip/_vendor/colorama/__init__.py", line 2, in <module>
  File "/tmp/tmp7od_thjv/pip-1.5.6-py2.py3-none-any.whl/pip/_vendor/colorama/initialise.py", line 5, in <module>
  File "/tmp/tmp7od_thjv/pip-1.5.6-py2.py3-none-any.whl/pip/_vendor/colorama/ansitowin32.py", line 6, in <module>
  File "/tmp/tmp7od_thjv/pip-1.5.6-py2.py3-none-any.whl/pip/_vendor/colorama/winterm.py", line 2, in <module>
  File "/tmp/tmp7od_thjv/pip-1.5.6-py2.py3-none-any.whl/pip/_vendor/colorama/win32.py", line 7, in <module>
  File "/export/home/buildbot/64bits/3.4.cea-indiana-amd64/build/Lib/ctypes/__init__.py", line 7, in <module>
    from _ctypes import Union, Structure, Array
ImportError: No module named '_ctypes'

Since this is not a failure of ensurepip, I think this should instead be a test skip.  The easiest thing would be to do what you did with ssl.

This is a duplicate of Issue22611.

I think this was improperly closed.  #22611 was about pip.  This one is about test_venv failing today, 8 days after 22611 was closed, when optional module _ctypes is not built.  The resolution of this issue should be that either the buildbots start using the new version of pip that will not fail or that test_venv is patched to work with version of pip that is being used.

Issue22611 documents exactly the same failure so if this issue was improperly closed than Issue22611 was, too.  So I would think the earlier issue would be the place to discuss this.  But, in any case, I think the issue is that the latest version of pip hasn't been released yet and/or not yet vendored into the 3.4 and default source trees.  Donald would be the person to discuss that.

It hasn't been released yet, test_venv could be temp disabled if ctypes isn't available though.

As I understand it, the reason test_venv is failing is because of a defect in the pip vendored colorama.  The test has found the unexpected dependency of the vendored package with ctypes.  It's good that the test failed.  The right solution is to provide the updated pip with the fixed colorama and that should be happening shortly.  And when that happens, there should no longer be a test failure.  Is my understanding correct?  If so, I would argue that we should not be touching test_venv.

More or less. You could argue whether it's a defect or not but it unconditionally imports ctypes and apparently that is an optional module (I had no idea it was personally, and I can't find any documentation to say that it is). colorama doesn't really *need* ctypes on Linux it only needs it on Windows so it fixes this by just conditionally importing it.

Assigning this to myself, it'll get fixed when pip 6.0 is released and I upgrade ensurepip to it.

This should be fixed now as of https://hg.python.org/cpython/rev/651e1862dbed, https://hg.python.org/cpython/rev/651e1862dbed, and https://hg.python.org/cpython/rev/9f60d024e586.

test_venv passed on Open Indiana in the 14:10-14:22 buildbot runs triggered by the patch.  It failed with a different error on a later default run, but that looked like a different issue, if permanent.

I'm not sure how to get a link to that, can you link it and I can see if I think it's a permanent error or not?

http://buildbot.python.org/all/builders/AMD64%20OpenIndiana%203.x/builds/9012/steps/test/logs/stdio

Start with buildbot.python.org, select set of (all/stable) buildbots for version.  'Build ####' like gives commit(s) that triggered build.  Test stdio link, as above, gives test results.  Above was triggered by Serhiy's commit after yours. "No module named pip.__main__;"