Unable to run tox tests, install_command error

Bug #1546664 reported by Dane Fichter
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Glance
Invalid
Undecided
Unassigned

Bug Description

I'm starting from a new install of Ubuntu 14.04, I'm able to run tests via the ./run_tests.sh script, but am unable to run the tests via tox. Whenever I attempt to, I get the following error:

Traceback (most recent call last):
  File "/usr/bin/tox", line 9, in <module>
    load_entry_point('tox==1.6.0', 'console_scripts', 'tox')()
  File "/usr/lib/python2.7/dist-packages/tox/_cmdline.py", line 25, in main
    config = parseconfig(args, 'tox')
  File "/usr/lib/python2.7/dist-packages/tox/_config.py", line 44, in parseconfig
    parseini(config, inipath)
  File "/usr/lib/python2.7/dist-packages/tox/_config.py", line 236, in __init__
    config)
  File "/usr/lib/python2.7/dist-packages/tox/_config.py", line 335, in _makeenvconfig
    "'install_command' must contain '{packages}' substitution")
tox.ConfigError: ConfigError: 'install_command' must contain '{packages}' substitution

I believe it's an error in tox.ini, but after checking on IRC, I don't see anyone else experiencing the same error.

Revision history for this message
Bathri Ajay Raj (bathri-s) wrote :

Hi Dane, please try it by updating the tox version. Current tox version is 2.3.1 and I believe you are using 1.6.0. Also try running tox after updating your pbr to the latest version.

Revision history for this message
Dane Fichter (dane-fichter) wrote :

Thanks for your help Bathri.

For others who hit this issue; upgrading the tox install via the usual routes (sudo pip install --upgrade tox or sudo apt-get update python-tox) didn't work. Both of these options failed to remove tox 1.6.0 because it is "owned by the OS". I resolved this by manually removing tox 1.6.0 (sudo rm -rf /usr/lib/python2.7/dist-packages/tox-1.6.0.egg-info/), then uninstalling via both pip AND the debian package manager, and then reinstalling with both the debian package manager and pip.

Revision history for this message
Cyril Roelandt (cyril-roelandt) wrote :

Should we mark this as "invalid", then?

Revision history for this message
Dane Fichter (dane-fichter) wrote :

Done.

Changed in glance:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.