Files
95019f9786943bacacfd6e97fe5d949bbd0f95dc
nova /tox.ini

151 lines
5.0 KiB
INI
Raw Normal View History

[tox]
Add constraint target to tox.ini This adds a pip install command to tox.ini that is only used when the tox env is passed with the 'constraints' factor appended onto it. As such this will not effect developer workflows or current unit tests. The initial use of this will be in a non-voting job, to verify that the constrained checks with tox are stable. DevStack is already running constrained jobs, as such problems are no expected. To run a tox with pip using constraints on a developer system a developer should run the desired tox environment with -constraints. For example: $(tox -epy27-constraints) Pip will pull the current version of the upper-constraints.txt file down from the git.openstack.org, however this method can be overriden to use a local file setting the environment variable "UPPER_CONSTRAINTS_FILE" to the local path or a different URL, it is passed directly to pip. This is currently not enabled in the default tox run, however it is possible to enable it as a default by adding it to 'envlist' in tox.ini Depends-On: I17ac389f78af241917b6da7f049085f2b13d30f2 Change-Id: I8ea1710a4e3a287405978b467e0b2dfbb025b795 Implements Blueprint: Requirements-Management
2015年07月27日 15:55:32 +10:00
minversion = 1.8
envlist = py34,py27,functional,pep8,pip-missing-reqs
skipsdist = True
[testenv]
usedevelop = True
# tox is silly... these need to be separated by a newline....
whitelist_externals = bash
find
rm
Add constraint target to tox.ini This adds a pip install command to tox.ini that is only used when the tox env is passed with the 'constraints' factor appended onto it. As such this will not effect developer workflows or current unit tests. The initial use of this will be in a non-voting job, to verify that the constrained checks with tox are stable. DevStack is already running constrained jobs, as such problems are no expected. To run a tox with pip using constraints on a developer system a developer should run the desired tox environment with -constraints. For example: $(tox -epy27-constraints) Pip will pull the current version of the upper-constraints.txt file down from the git.openstack.org, however this method can be overriden to use a local file setting the environment variable "UPPER_CONSTRAINTS_FILE" to the local path or a different URL, it is passed directly to pip. This is currently not enabled in the default tox run, however it is possible to enable it as a default by adding it to 'envlist' in tox.ini Depends-On: I17ac389f78af241917b6da7f049085f2b13d30f2 Change-Id: I8ea1710a4e3a287405978b467e0b2dfbb025b795 Implements Blueprint: Requirements-Management
2015年07月27日 15:55:32 +10:00
install_command =
constraints: {[testenv:common-constraints]install_command}
Add constraint target to tox.ini This adds a pip install command to tox.ini that is only used when the tox env is passed with the 'constraints' factor appended onto it. As such this will not effect developer workflows or current unit tests. The initial use of this will be in a non-voting job, to verify that the constrained checks with tox are stable. DevStack is already running constrained jobs, as such problems are no expected. To run a tox with pip using constraints on a developer system a developer should run the desired tox environment with -constraints. For example: $(tox -epy27-constraints) Pip will pull the current version of the upper-constraints.txt file down from the git.openstack.org, however this method can be overriden to use a local file setting the environment variable "UPPER_CONSTRAINTS_FILE" to the local path or a different URL, it is passed directly to pip. This is currently not enabled in the default tox run, however it is possible to enable it as a default by adding it to 'envlist' in tox.ini Depends-On: I17ac389f78af241917b6da7f049085f2b13d30f2 Change-Id: I8ea1710a4e3a287405978b467e0b2dfbb025b795 Implements Blueprint: Requirements-Management
2015年07月27日 15:55:32 +10:00
pip install -U --force-reinstall {opts} {packages}
setenv = VIRTUAL_ENV={envdir}
OS_TEST_PATH=./nova/tests/unit
LANGUAGE=en_US
LC_ALL=en_US.utf-8
deps = -r{toxinidir}/test-requirements.txt
commands =
find . -type f -name "*.pyc" -delete
bash tools/pretty_tox.sh '{posargs}'
passenv = http_proxy HTTP_PROXY https_proxy HTTPS_PROXY no_proxy NO_PROXY
# there is also secret magic in pretty_tox.sh which lets you run in a fail only
# mode. To do this define the TRACE_FAILONLY environmental variable.
[tox:jenkins]
downloadcache = ~/cache/pip
[testenv:common-constraints]
install_command = pip install -c{env:UPPER_CONSTRAINTS_FILE:https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt} {opts} {packages}
[testenv:pep8]
commands =
bash tools/flake8wrap.sh {posargs}
[testenv:pep8-constraints]
install_command = {[testenv:common-constraints]install_command}
commands =
bash tools/flake8wrap.sh {posargs}
[testenv:py34]
setenv = {[testenv]setenv}
commands =
find . -type f -name "*.pyc" -delete
python -m subunit.run discover -t . ./nova/tests/ --list
Use os-testr for py34 tox target os-testr has a blacklist we can use to specify which tests to avoid. It uses "testr run --parallel" so tests are run in parallel as well. We also get rid of the huge list of tests in tox.ini into a separate file. <soap_box> The reason for using a black list is that when new tests are being added, they are automatically either fixed to work under python34 or added to a well known list of tests so whoever is working on python34 can try to fix those tests over a period of time. Hoping really that this black list shrinks over time quickly. This is also a pool of low hanging tasks that folks when they have some time to pull a few tests from here and fix them. </soapbox> Bumps number of tests executed from 5606 to 7206 Depends-On: Ib5e682d0380cf7bc5e288a1e4d125379b452fa92 Change-Id: Ib641bb0f7553eb7704b419b9d00f86174f6d831d
2015年09月29日 13:54:26 -04:00
ostestr --blacklist_file tests-py3.txt
[testenv:py34-constraints]
install_command = {[testenv:common-constraints]install_command}
setenv = {[testenv]setenv}
deps = -r{toxinidir}/requirements.txt
-r{toxinidir}/test-requirements.txt
commands = {[testenv:py34]commands}
[testenv:functional]
usedevelop = True
install_command = pip install -U --force-reinstall {opts} {packages}
setenv = VIRTUAL_ENV={envdir}
OS_TEST_PATH=./nova/tests/functional
LANGUAGE=en_US
commands =
find . -type f -name "*.pyc" -delete
bash tools/pretty_tox.sh '{posargs}'
[testenv:functional-constraints]
usedevelop = {[testenv:functional]usedevelop}
install_command = {[testenv:common-constraints]install_command}
setenv = {[testenv:functional]setenv}
commands =
find . -type f -name "*.pyc" -delete
bash tools/pretty_tox.sh '{posargs}'
[testenv:genconfig]
commands = oslo-config-generator --config-file=etc/nova/nova-config-generator.conf
[testenv:cover]
# Also do not run test_coverage_ext tests while gathering coverage as those
# tests conflict with coverage.
commands =
coverage erase
Switch Nova to use oslo.concurrency Let's switch to the newly released oslo library for the processutils and lockutils. We use the config fixture(s) to specify disable_process_locking and lock_path in the CONF variable of oslo.concurrency library for correctly setting the flags. The previous attempt at updating nova to use oslo.concurrency was reverted as it stopped running any tests. lockutils-wrapper should have been used in ini/shell scripts instead of lockutils.py module as the the module is no longer runnable (__main__ has been removed). In this review we use lockutils-wrapper correctly. The test harness has since been updated to bail out if 0 tests are run as well for additional insurance. Change-Id: I14c75ef2196fd08c9465d648e5cd53777bd9c7d1 Co-Authored-By: Nikola Dipanov <ndipanov@redhat.com> Co-Authored-By: Corey Wright <corey.wright@rackspace.com>
2014年10月24日 14:18:30 -04:00
python setup.py testr --coverage \
--testr-args='{posargs}'
coverage combine
coverage html --include='nova/*' --omit='nova/openstack/common/*' -d covhtml -i
[testenv:cover-constraints]
install_command = {[testenv:common-constraints]install_command}
# Also do not run test_coverage_ext tests while gathering coverage as those
# tests conflict with coverage.
commands =
coverage erase
python setup.py testr --coverage \
--testr-args='{posargs}'
coverage combine
coverage html --include='nova/*' --omit='nova/openstack/common/*' -d covhtml -i
[testenv:venv]
commands = {posargs}
[testenv:venv-constraints]
install_command = {[testenv:common-constraints]install_command}
commands = {posargs}
[testenv:docs]
commands =
rm -rf doc/source/api doc/build api-guide/build
python setup.py build_sphinx
bash -c '! find doc/ -type f -name *.json | xargs -t -n1 python -m json.tool 2>&1 > /dev/null | grep -B1 -v ^python'
oslo-config-generator --config-file=etc/nova/nova-config-generator.conf
sphinx-build -b html api-guide/source api-guide/build
[testenv:api-guide]
# This environment is called from CI scripts to test and publish
# the API Guide to developer.openstack.org.
commands =
sphinx-build -b html -d api-guide/build/doctrees api-guide/source api-guide/build
[testenv:docs-constraints]
install_command = {[testenv:common-constraints]install_command}
commands = {[testenv:docs]commands}
[testenv:bandit]
commands = bandit -c bandit.yaml -r nova -n 5 -ll
[flake8]
# E125 is deliberately excluded. See https://github.com/jcrocholl/pep8/issues/126
# The rest of the ignores are TODOs
# New from hacking 0.9: E129, E131, H407, H405
# E251 Skipped due to https://github.com/jcrocholl/pep8/issues/301
ignore = E121,E122,E123,E124,E125,E126,E127,E128,E129,E131,E251,H405
exclude = .venv,.git,.tox,dist,doc,*openstack/common/*,*lib/python*,*egg,build,tools/xenserver*
# To get a list of functions that are more complex than 25, set max-complexity
# to 25 and run 'tox -epep8'.
# 34 is currently the most complex thing we have
# TODO(jogo): get this number down to 25 or so
max-complexity=35
[hacking]
local-check-factory = nova.hacking.checks.factory
import_exceptions = nova.i18n
[testenv:pip-missing-reqs]
# do not install test-requirements as that will pollute the virtualenv for
# determining missing packages
# this also means that pip-missing-reqs must be installed separately, outside
# of the requirements.txt files
deps = pip_missing_reqs
Fix pip-missing-reqs The gate-nova-pip-missing-reqs job on the experimental queue is failing and pointing out several missing runtime dependencies from requirements.txt. Also, we need to ignore the nova/test.py file during the scan since pip-missing-reqs doesn't include test-requirements.txt. requests -------- nova/scheduler/filters/trusted_filter.py:50 dist=requests nova/api/ec2/__init__.py:30 dist=requests prettytable ----------- nova/openstack/common/cliutils.py:29 dist=prettytable python-keystoneclient --------------------- nova/context.py:22 dist=python-keystoneclient nova/network/neutronv2/api.py:21 dist=python-keystoneclient nova/compute/manager.py:42 dist=python-keystoneclient nova/volume/cinder.py:27 dist=python-keystoneclient nova/context.py:23 dist=python-keystoneclient nova/network/neutronv2/api.py:23 dist=python-keystoneclient nova/network/neutronv2/api.py:24 dist=python-keystoneclient nova/volume/cinder.py:28 dist=python-keystoneclient nova/keymgr/barbican.py:25 dist=python-keystoneclient nova/network/neutronv2/api.py:22 dist=python-keystoneclient netifaces --------- nova/compute/utils.py:21 dist=netifaces setuptools ---------- nova/openstack/common/versionutils.py:26 dist=setuptools nova/virt/xenapi/image/bittorrent.py:18 dist=setuptools Closes-Bug: #1453857 Change-Id: If880d76cf3e47c14b370d63313330996e09f5ab8
2015年05月14日 11:37:28 -07:00
commands=pip-missing-reqs -d --ignore-file=nova/tests/* --ignore-file=nova/test.py nova