test_always_copy_option() fails #530

Arfrever opened this Issue Jan 6, 2014 · 8 comments


None yet

4 participants

Arfrever commented Jan 6, 2014

test_always_copy_option() fails with all Python versions (2.6, 2.7, 3.1, 3.2, 3.3).

$ nosetests-2.7
ERROR: Should be no symlinks in directory tree
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/nose/case.py", line 197, in runTest
  File "/tmp/virtualenv/tests/test_virtualenv.py", line 131, in test_always_copy_option
    virtualenv.create_environment(ve_path, symlink=False)
  File "/tmp/virtualenv/virtualenv.py", line 984, in create_environment
    install_wheel(to_install, py_executable, search_dirs)
  File "/tmp/virtualenv/virtualenv.py", line 952, in install_wheel
    'PIP_NO_INDEX': '1'
  File "/tmp/virtualenv/virtualenv.py", line 894, in call_subprocess
    % (cmd_desc, proc.returncode))
OSError: Command /tmp/tmp_As_WG/venv/bin/python2.7 -c "import sys, pip; pip...ll\"] + sys.argv[1:])" setuptools pip failed with error code 1

Ran 8 tests in 0.623s

FAILED (errors=1)
qwcode commented Jan 7, 2014

looks like it's due to #524
it's failing to create a virtualenv for itself.
will close this, when #524 closes.

qwcode commented Jan 7, 2014

well, it being #524 doesn't really make sense, since that's just for easy_install'd virtualenvs.
hmm, it doesn't fail locally for me or in travis.

I guess it's posssible the interpreter running nosetests didn't have access to the virtualenv.py in the src tree, and was importing one that was easy_install'd?

Arfrever commented Jan 7, 2014

This test fails in the same way even after deleting virtualenv installed (by setup.py, not easy_install) in /usr/lib64/python*/site-packages.

@dstufft dstufft referenced this issue Jan 5, 2015

Rewrite virtualenv #697

0 of 5 tasks complete
blueyed commented Mar 2, 2015

I assume this has been fixed in the meantime?

Is it still an issue for you?

blueyed commented Mar 2, 2015

For reference, it currently fails with pypy 2.5.0 - but with a different error: #725

Arfrever commented Mar 3, 2015

Error is still reproducible in virtualenv trunk.


I seem to see this testing locally, but not in Fedora rpm builds of virtualenv in koji. Failing command seems to be:

/tmp/tmpRyOd9Y/venv/bin/python -c "import sys, pip; sys.exit(pip.main(["install", "--ignore-installed"] + sys.argv[1:]))" setuptools pip

error is:

ImportError: No module named time


Scratch that - 12.1.1 is failing in koji as well.

This was referenced May 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment