openstack/neutron
Code Issues Proposed changes
af1f994787
neutron/tox.ini

97 lines
3.1 KiB
INI
Raw Normal View History

Getting ready for the client split. Change-Id: Ic2e7d637d2c116dfda3d7ad958ccba39a8da7751
2012-01-10 17:44:27 -08:00
[tox]
Update default tox envlist to match voting gate checks Remove not-yet supported py3* environments. Note the removed environments (py33,py34) are still supported via explicit `tox -e`, it's only the default set that is changed here. ObPoliticalDisclaimer: This in no way diminishes the importance of py3 support. In fact, the intention is quite the opposite: One day py3x will be supported and the py3x test will be expected to pass. Meanwhile, if everyone has been trained to run selective `tox -epy27` tests then they will be unaware of the py3x status change and won't be testing their code against py3 - or alternatively they will believe that py3x failures are "normal" and to be ignored. The hope with doing this change now is that we will (re)train people that the default list of tox tests are expected to pass, and any failures need to be investigated. Change-Id: I992e1d6b35aa7c516c9ce14e606bbe32e895a4f0
2015-02-27 13:51:17 +11:00
envlist = py27,pep8
Un-break tox for unit tests Running 'tox -e py27 $some_unit_test' is always failing now with tox 1.6.0, with this being printed at the beginning: ERROR: InvocationError: could not find executable 'dsvm-functional:' Seems commit 540e4d791ff2573aae38810f4c39f2d6f46d8898 (Automate host configuration for functional testing) added some code to tox.ini that requires version 1.8 or later, so make that the minimum. Change-Id: I56313d0a22dbc4007142b8bb4890d1ac8bebff94
2015-02-17 15:57:10 -05:00
minversion = 1.8
Updates tox.ini to use new features tox 1.6 allows us to skip the sdist step, which is slow. This does that. It also allows us to override the install line. In this case, it's important as it allows us to stop getting pre-release software we weren't asking for. Original patch by Monty Taylor, talked about here: http://lists.openstack.org/pipermail/openstack-dev/2013-September/015495.html Change-Id: I87f172cfcc44c9afff9c5162791d6c6b31972702
2013-12-09 14:02:49 +00:00
skipsdist = True
Getting ready for the client split. Change-Id: Ic2e7d637d2c116dfda3d7ad958ccba39a8da7751
2012-01-10 17:44:27 -08:00
[testenv]
Set python hash seed to 0 in tox.ini New tox (>=1.7.0) sets a random python hash seed by default. This is generally good for testing because it will help keep projects working regardless of the hash seed, but neutron unittests don't currently pass with a random hash seed so set it to the python default seed. This change will allow us to use new tox again and remove the restriction on tox<=1.6.1 to run unittests. Note this change will need to be backported to the stable branches to keep unittests there working with new tox as well. Change-Id: If151efeb8caae3111515191e238d6e6ae491cd44
2014-07-25 13:30:00 -07:00
# Note the hash seed is set to 0 until neutron can be tested with a
# random hash seed successfully.
Split out pip requires and aligned tox file. Align tox.ini file with standards. Align setup.py with openstack-common standards. Change-Id: I333bbd66648c865a5c97ec2661359ab849274446
2012-02-29 09:39:03 -08:00
setenv = VIRTUAL_ENV={envdir}
Set python hash seed to 0 in tox.ini New tox (>=1.7.0) sets a random python hash seed by default. This is generally good for testing because it will help keep projects working regardless of the hash seed, but neutron unittests don't currently pass with a random hash seed so set it to the python default seed. This change will allow us to use new tox again and remove the restriction on tox<=1.6.1 to run unittests. Note this change will need to be backported to the stable branches to keep unittests there working with new tox as well. Change-Id: If151efeb8caae3111515191e238d6e6ae491cd44
2014-07-25 13:30:00 -07:00
PYTHONHASHSEED=0
Updates tox.ini to use new features tox 1.6 allows us to skip the sdist step, which is slow. This does that. It also allows us to override the install line. In this case, it's important as it allows us to stop getting pre-release software we weren't asking for. Original patch by Monty Taylor, talked about here: http://lists.openstack.org/pipermail/openstack-dev/2013-September/015495.html Change-Id: I87f172cfcc44c9afff9c5162791d6c6b31972702
2013-12-09 14:02:49 +00:00
usedevelop = True
install_command = pip install -U {opts} {packages}
Rename requires files to standard names. Rename tools/pip-requires to requirements.txt and tools/test-requires to test-requirements.txt. These are standard files, and tools in the general world are growing intelligence about them. Fixes: bug #1179008 Change-Id: I6f8a11988982133249d443403f63b4f8724e156e
2013-05-30 13:36:22 +08:00
deps = -r{toxinidir}/requirements.txt
-r{toxinidir}/test-requirements.txt
pretty_tox.sh: Portablity improvement A recent change (commit 0d5a11d9c722870f9c5e31a993219c7e240b4e19) introduced bash dependency. It broke my environment, where bash is not available. This change aims to restore it. As far as I undestand, the change in question requires bash for the "pipefail" feature. Fortunately there's a more portable well-known trick for the purpose. Closes-Bug: #1398266 Change-Id: Id3561d81462923d20ad39584ba4cf8e1a294a8a8
2014-12-02 13:18:48 +09:00
whitelist_externals = sh
Update tox.ini to support RHEL 6.x. In order to support running unit tests on RHEL 6.x we need to patch eventlet with contrib/redhat-eventlet.patch. We already have support for this in the tools/install_venv_common.py but we need to make a couple changes to allow tox to consume this: 1) Sync in the latest intall_venv_common.py from oslo. This changes patch to use the -N option (ignore already applied patches) and makes it safe to call the patching function more than once. 2) Add a new patch_tox_venv.py script in tools. 3) Update tox.ini to call patch_tox_venv.py before it runs tests and coverage. NOTE: This will hopefully go away eventually once this patch lands: https://bitbucket.org/eventlet/eventlet/issue/89/add-a-timeout-argument-to-subprocesspopen#comment-3342969 Change-Id: I3e2b07c3f718e4aede5c5f231ff0cdb7721ec885
2013-03-07 12:41:30 -05:00
commands =
Automate host configuration for functional testing This change adds a new script, configure_for_func_testing.sh, that automates configuration of a host to support functional testing. The script's functionality is consumed by a refactored version of gate_hook.sh, and both minimizes runtime and removes the previous dependency on the devstack-gate repo. Additionally, the dsvm-functional tox env is no longer dependent on devstack to deploy neutron's rootwrap configuration system-wide. Rootwrap configuration is now deployed to the target tox venv on each tox invocation. Change-Id: Iaf43be458bdf3c4535f95ee5a3a3b47a744020a0
2015-01-09 15:02:59 +00:00
dsvm-functional: {toxinidir}/tools/deploy_rootwrap.sh {toxinidir} {envdir}/etc {envbindir}
pretty_tox.sh: Portablity improvement A recent change (commit 0d5a11d9c722870f9c5e31a993219c7e240b4e19) introduced bash dependency. It broke my environment, where bash is not available. This change aims to restore it. As far as I undestand, the change in question requires bash for the "pipefail" feature. Fortunately there's a more portable well-known trick for the purpose. Closes-Bug: #1398266 Change-Id: Id3561d81462923d20ad39584ba4cf8e1a294a8a8
2014-12-02 13:18:48 +09:00
sh tools/pretty_tox.sh '{posargs}'
Show progress output while running unit tests This patch imports some magic to enable showing test output as the tests run. Seeing output showing tests as they execute is reassuring that the test run is continuing to make progress. This originated in tempest and was then brought over to Nova in this commit: https://review.openstack.org/#/c/121914/ Note the justification in that commit to just copy it instead of move it to a shared repo. To get the old behavior where you only get output when something fails, you can set the TRACE_FAILONLY env var. That originated in this commit in Nova: https://review.openstack.org/#/c/123801/ Change-Id: I6a079ad5f630383650c0f9dee09e04250d0e2c5a
2014-11-20 21:01:14 +00:00
# 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.
Fix up test running to match jenkins expectation. Change-Id: I215cd92d707f81ed481897704b31188017a5a8b8
2012-06-08 19:46:37 -04:00
Add a tox test environment for random hashseed testing The newer versions of tox by default enable a random PYTHONHASHSEED. However, this breaks many Neutron unit tests, so PYTHONHASHSEED=0 is currently hard- coded for Neutron's unit test environments. We want to clean up the unit test cases that break with a random hashseed (there are many). To be able to find the broken tests and then verify them, we need to have an easy way of enabling random hashseed testing. Partial-bug: #1348818 Change-Id: I51f05cdfa9f8728baabaf315b71e5defb26426b1
2014-08-04 08:47:08 -04:00
[testenv:hashtest]
# This is the same as default environment, but with a random PYTHONHASHSEED.
# You can also specify a specific hashseed (for test repeatability) as follows:
# tox --hashseed 1235130571 -e hashtest
setenv = VIRTUAL_ENV={envdir}
Add support for retargetable functional api testing This patch introduces the concept of a 'retargetable' functional api test. Such a test targets an abstract client class, and by varying the implementation of the client, the test can target multiple backends. The test added by this patch (test_network_lifecycle) can be run against the programmatic plugin api (for configured plugins) via both tox -e functional and tox -e dsvm-functional. The latter env is used by the gating neutron-dsvm-functional job. The test can also be run against a live Neutron service via 'tox -e api' which will soon be run as part of the check queue by the neutron-dsvm-api job [1]. Running this tox env requires devstack-deployed Neutron and Tempest. The intention is to refactor the existing plugin tests (e.g. NeutronDbPluginV2TestCase) to use this model. Functional tests don't have to isolate functionality - they just need to exercise it - so fewer tests will be required. The new tests will be able to target plugins directly rather than through the wsgi stack, so execution time will be decreased. The refactored tests should be easier to maintain and take less time to run. Perhaps best of all, since the same tests will be able to target a deployed service in the neutron-dsvm-api job, the deployed behaviour of api changes will finally be able to gate merges to the Neutron tree. Notable parts of the change: - tests/api - base_v2 - defines the client interface (BaseNeutronClient) and the base class (BaseTestApi) for the retargetable test (test_network_lifecycle) - test_v2_rest - implements the client interface for the tempest rest client and configures the retargetable test with scenarios for json serialization - tests/functional/api - test_v2_plugin - implements the client interface for the programmatic plugin api and configures the retargetable test with scenarios targeting the linuxbridge and openvswitch plugins - tests/unit - refactor bits of the existing plugin tests for reuse 1: https://review.openstack.org/#/c/82226/ Implements: bp retargetable-functional-testing Change-Id: Ib5470040c0fa91ec143f38d273e1e259b3adfb2e
2014-03-25 01:04:50 -07:00
[testenv:api]
setenv = OS_TEST_PATH=./neutron/tests/api
Set TEMPEST_CONFIG_DIR in the api tox env TEMPEST_CONFIG_DIR needs to be set for the api job to execute successfully. Previously this was being set by the gate but local execution required manually setting the variable. Change-Id: Ic1364388e812a5fca26f37049242f7d09ee75fef
2015-03-13 18:17:29 +00:00
TEMPEST_CONFIG_DIR={env:TEMPEST_CONFIG_DIR:/opt/stack/tempest/etc}
Add support for retargetable functional api testing This patch introduces the concept of a 'retargetable' functional api test. Such a test targets an abstract client class, and by varying the implementation of the client, the test can target multiple backends. The test added by this patch (test_network_lifecycle) can be run against the programmatic plugin api (for configured plugins) via both tox -e functional and tox -e dsvm-functional. The latter env is used by the gating neutron-dsvm-functional job. The test can also be run against a live Neutron service via 'tox -e api' which will soon be run as part of the check queue by the neutron-dsvm-api job [1]. Running this tox env requires devstack-deployed Neutron and Tempest. The intention is to refactor the existing plugin tests (e.g. NeutronDbPluginV2TestCase) to use this model. Functional tests don't have to isolate functionality - they just need to exercise it - so fewer tests will be required. The new tests will be able to target plugins directly rather than through the wsgi stack, so execution time will be decreased. The refactored tests should be easier to maintain and take less time to run. Perhaps best of all, since the same tests will be able to target a deployed service in the neutron-dsvm-api job, the deployed behaviour of api changes will finally be able to gate merges to the Neutron tree. Notable parts of the change: - tests/api - base_v2 - defines the client interface (BaseNeutronClient) and the base class (BaseTestApi) for the retargetable test (test_network_lifecycle) - test_v2_rest - implements the client interface for the tempest rest client and configures the retargetable test with scenarios for json serialization - tests/functional/api - test_v2_plugin - implements the client interface for the programmatic plugin api and configures the retargetable test with scenarios targeting the linuxbridge and openvswitch plugins - tests/unit - refactor bits of the existing plugin tests for reuse 1: https://review.openstack.org/#/c/82226/ Implements: bp retargetable-functional-testing Change-Id: Ib5470040c0fa91ec143f38d273e1e259b3adfb2e
2014-03-25 01:04:50 -07:00
Add an explicit tox job for functional tests This change is in support of adding a new jenkins job dedicated to functional testing. Functional tests will no longer be run as part of the unit tests. Change-Id: Ia99940f7e5a2165720ae2a74aadf62ff17ad3d75
2014-01-14 18:43:22 +00:00
[testenv:functional]
setenv = OS_TEST_PATH=./neutron/tests/functional
Set timeout for functional job As functional jobs take more time to finish than unit tests and also there is a chance that test will hang due to system interaction, this patch sets maximum execution time to 90 seconds per test. Change-Id: Ib58a1b53ace178e1bf99150628fa5576b079e8bc
2014-12-12 18:39:56 +01:00
OS_TEST_TIMEOUT=90
Move DB TestModelsMigrations from unit to functional The tests to check that DB migrations and models are in sync depends on the mysql and postgresql backends being available with a specific DB user and database created. This violates the principles for unit tests and therefore these tests should be moved to functional tests. For these tests to work in the functional job in the gate, the backends must be installed and the DB user and database created. We do this via the functional gate hook. Closes-bug: #1372981 Change-Id: I7b89feef3f19ca07dbfb05acfaa30529a5bf683d
2014-10-05 01:23:50 -04:00
deps =
{[testenv]deps}
-r{toxinidir}/neutron/tests/functional/requirements.txt
Add an explicit tox job for functional tests This change is in support of adding a new jenkins job dedicated to functional testing. Functional tests will no longer be run as part of the unit tests. Change-Id: Ia99940f7e5a2165720ae2a74aadf62ff17ad3d75
2014-01-14 18:43:22 +00:00
Add a gate-specific tox env for functional tests The functional gate jobs (*-neutron-dsvm-functional) need special configuration (e.g. OS_SUDO_TESTING, OS_ROOTWRAP_CMD) to run tests. This patch adds a new gate-specific tox env (tox -e dsvm-functional) that sets the appropriate values and allows easy duplication of the results of the upstream job on a host that has successfully run devstack with neutron enabled. A new configuration option, OS_FAIL_ON_MISSING_DEPS, is also set by the dsvm-functional tox env to ensure that dependency failures will result in failures rather than skips when run in the gate. Change-Id: Idbfef1ba72ed129a3021509c7969e2685b8a6d09 Partial-bug: #1336172
2014-07-02 00:35:12 +00:00
[testenv:dsvm-functional]
setenv = OS_TEST_PATH=./neutron/tests/functional
OS_SUDO_TESTING=1
Automate host configuration for functional testing This change adds a new script, configure_for_func_testing.sh, that automates configuration of a host to support functional testing. The script's functionality is consumed by a refactored version of gate_hook.sh, and both minimizes runtime and removes the previous dependency on the devstack-gate repo. Additionally, the dsvm-functional tox env is no longer dependent on devstack to deploy neutron's rootwrap configuration system-wide. Rootwrap configuration is now deployed to the target tox venv on each tox invocation. Change-Id: Iaf43be458bdf3c4535f95ee5a3a3b47a744020a0
2015-01-09 15:02:59 +00:00
OS_ROOTWRAP_CMD=sudo {envbindir}/neutron-rootwrap {envdir}/etc/neutron/rootwrap.conf
Add rootwrap daemon mode support This patch introduces support for rootwrap daemon mode. It adds a new config option, AGENT.root_helper_daemon with no default. To enable, set to something like: root_helper_daemon = sudo neutron-rootwrap-daemon /etc/neutron/rootwrap.conf The patch currently assumes that the root_helper_daemon value, and specifically the rootwrap config, will not change once calls to execute() happen. While it would not be hard to generate a rootwrap daemon client for each new config, I couldn't think of a legitimate reason to support it and left it out as YAGNI. This patch does change the behavior of the addl_env argument to create_process and execute. Previously, an environment dict would be passed to Popen. If a root helper was used, this environemnt would actually be passed to 'sudo' which would filter it before passing it to the underlying command. In the case of daemon mode, this would cause a problem as the enviornment is filtered by sudo only once, at daemon startup. Any environment variables added at execute time would then just be passed directly to the underyling command unfiltered. oslo.rootwrap 1.6.0 fixes this issue by denying the passing of environment variables to the daemon altogether. Instead, anything using rootwrap and needing to pass additional environment variables should define an EnvFilter and run the command with env var=val cmd. utils.execute/create_process have been modified to run code in this way (which netns.execute already did). No code in neutron currently uses both run_as_root=True and addl_env, so this change does not require any change in code or filters. DocImpact Implements: blueprint rootwrap-daemon-mode Change-Id: I567334bb611253c7b9d830d50c5be308a5153baf
2015-02-23 14:56:44 -06:00
OS_ROOTWRAP_DAEMON_CMD=sudo {envbindir}/neutron-rootwrap-daemon {envdir}/etc/neutron/rootwrap.conf
Add a gate-specific tox env for functional tests The functional gate jobs (*-neutron-dsvm-functional) need special configuration (e.g. OS_SUDO_TESTING, OS_ROOTWRAP_CMD) to run tests. This patch adds a new gate-specific tox env (tox -e dsvm-functional) that sets the appropriate values and allows easy duplication of the results of the upstream job on a host that has successfully run devstack with neutron enabled. A new configuration option, OS_FAIL_ON_MISSING_DEPS, is also set by the dsvm-functional tox env to ensure that dependency failures will result in failures rather than skips when run in the gate. Change-Id: Idbfef1ba72ed129a3021509c7969e2685b8a6d09 Partial-bug: #1336172
2014-07-02 00:35:12 +00:00
OS_FAIL_ON_MISSING_DEPS=1
Set timeout for functional job As functional jobs take more time to finish than unit tests and also there is a chance that test will hang due to system interaction, this patch sets maximum execution time to 90 seconds per test. Change-Id: Ib58a1b53ace178e1bf99150628fa5576b079e8bc
2014-12-12 18:39:56 +01:00
OS_TEST_TIMEOUT=90
Set dsvm-functional job to use system packages The functional job was breaking due to the interaction between devstack installing neutron system-wide in editable mode (pip install -e) and tox packaging in the same path. Installing in editable mode meant that neutron.egg-info/PKG_INFO could be updated (in this case by tox) to change the installed version of the neutron package without updating scripts that depended on the installed version (e.g. rootwrap). This fix is to set the dsvm-functional env to use system packages and avoid having tox update PKG_INFO. Change-Id: Icc38cacd69bc5843ccfcc60237a7102df6d8597f Closes-bug: #1370347
2014-09-17 19:48:41 +00:00
sitepackages=True
Move DB TestModelsMigrations from unit to functional The tests to check that DB migrations and models are in sync depends on the mysql and postgresql backends being available with a specific DB user and database created. This violates the principles for unit tests and therefore these tests should be moved to functional tests. For these tests to work in the functional job in the gate, the backends must be installed and the DB user and database created. We do this via the functional gate hook. Closes-bug: #1372981 Change-Id: I7b89feef3f19ca07dbfb05acfaa30529a5bf683d
2014-10-05 01:23:50 -04:00
deps =
{[testenv:functional]deps}
Add a gate-specific tox env for functional tests The functional gate jobs (*-neutron-dsvm-functional) need special configuration (e.g. OS_SUDO_TESTING, OS_ROOTWRAP_CMD) to run tests. This patch adds a new gate-specific tox env (tox -e dsvm-functional) that sets the appropriate values and allows easy duplication of the results of the upstream job on a host that has successfully run devstack with neutron enabled. A new configuration option, OS_FAIL_ON_MISSING_DEPS, is also set by the dsvm-functional tox env to ensure that dependency failures will result in failures rather than skips when run in the gate. Change-Id: Idbfef1ba72ed129a3021509c7969e2685b8a6d09 Partial-bug: #1336172
2014-07-02 00:35:12 +00:00
Fix up test running to match jenkins expectation. Change-Id: I215cd92d707f81ed481897704b31188017a5a8b8
2012-06-08 19:46:37 -04:00
[tox:jenkins]
sitepackages = True
downloadcache = ~/cache/pip
Getting ready for the client split. Change-Id: Ic2e7d637d2c116dfda3d7ad958ccba39a8da7751
2012-01-10 17:44:27 -08:00
[testenv:pep8]
Move pylint checks to pep8 testenv This change proposes to move pylint violation checks to the pep8 testenv. This changes make pylint gating within Neutron as it would participate in the vote. Having pylint executed on a separate job makes it difficult to handle potential unexpected breakages, because we need to get infra involved. When we need to renable the job, it is equally painful. Furthermore, it also causes us to spin an extra node, when the checks can easily be handled by the node for the pep8 job. Finally, having pylint running with tox -epep8 "helps" developers become aware of pylint violations sooner rather than later, if they "forget" to run the pylint testenv too before submitting the change. In order to make this patch succeed, a couple of pylint violation checks were skipped, as they slipped in, whilst the job was non-voting. We'll tackle them in due course. Change-Id: Ida6ae44a837d1761f5ce3e8a92f8850407f5cd16
2015-02-25 09:07:18 -08:00
deps =
{[testenv]deps}
pylint
commands=
Clean-up sanity checks done via shell scripts Move the various checks done via shell into a single file; this is cleaner and we'll have a lot more space to explain what is going on. Related-bug: #1404605 Change-Id: Ibb451c6a25217f37b73983c30891f55b35f143cd
2014-12-22 13:02:14 -08:00
# If it is easier to add a check via a shell script, consider adding it in this file
sh ./tools/misc-sanity-checks.sh
Add ability to run pylint check on modified files only Change c0aa0b fused pylint with the checks done with the pep8 testenv. This has the drawback of increasing the execution time of the command 'tox -epep8' fourfold. This change introduces the ability to execute the pylint check on just the list of python files affected by a specific patch. For instance, this can be done with the following command: tox -epep8 HEAD~1 A kind reminder is added, so that folks who end up noticing the spike of time execution when they run tox -epep8 without posargs, can learn how they can get their precious minutes back. Change-Id: Ie2a2b3a0171908d8d8aa8713baaa875adccb7efe
2015-02-25 21:53:27 -08:00
# Checks for coding and style guidelines
Revert "Fix ./run_tests.sh --pep8" We are explicitly trying to get rid of scripts like this and flake8 makes this one non-necessary. Fix run_tests.sh to run flake8 properly. This reverts commit 42243d6eb221d52bf6f62f835726cbe026e43447 Change-Id: I435e34b6acde7931a75f456ccc88da6476581643
2013-05-17 02:18:56 +00:00
flake8
Add ability to run pylint check on modified files only Change c0aa0b fused pylint with the checks done with the pep8 testenv. This has the drawback of increasing the execution time of the command 'tox -epep8' fourfold. This change introduces the ability to execute the pylint check on just the list of python files affected by a specific patch. For instance, this can be done with the following command: tox -epep8 HEAD~1 A kind reminder is added, so that folks who end up noticing the spike of time execution when they run tox -epep8 without posargs, can learn how they can get their precious minutes back. Change-Id: Ie2a2b3a0171908d8d8aa8713baaa875adccb7efe
2015-02-25 21:53:27 -08:00
sh ./tools/coding-checks.sh --pylint '{posargs}'
add HEAD sentinel file that contains migration revision This change wraps the command to generate a migration with code to update a file called HEAD. The HEAD file will contain the revision ID of the head of the migraton timeline. Additionally, check migrations has been altered to verify the contents of this file against the timeline head. This file helps the OpenStack gate detect potential migration branches without running alembic via git merge conflicts. Closes-Bug:1288427 Change-Id: If382c57baea061753d3f4fcd6faec1a31fbfb7ed
2014-03-07 15:07:43 -05:00
neutron-db-manage check_migration
tox.ini: Avoid using bash where unnecessary Switch to sh, which is hopefully more ubiquitously available than bash. A recent change (commit 085a35d657cf0fa41a402f2af66c4beaa0f60db2) introduced bash dependency for "tox -e pep8". It broke my environment, where bash is not available. This change aims to restore it. As far as I undestand, the change in question doesn't actually need the specific shell dialect. So switch to sh, which is expected to be available for any POSIX-like systems, would improve the situation. Closes-Bug: #1382327 Change-Id: Ie023d2265d9949a3e3721f03e865e4acfb460de2
2014-10-17 12:30:38 +09:00
whitelist_externals = sh
Make tox config work. Change-Id: Ic81c7bb0fa2fe5c73200a9195630a0d5bb999e7d
2012-01-25 01:23:12 -08:00
[testenv:cover]
Parallelize quantum unit testing: This change switches run_tests.sh to use testr in parallel mode, instead of nosetests, in order to enable unit tests to run in parallel. By default, the number of parallel test processes is set to the number of cores on the test machine. A similar change was recently merged to nova: https://review.openstack.org/#/c/15078/ Some tests required updating to remove inter-testcase dependencies. bug #1099694 Change-Id: Idfb923d424342a07dcba88d70b971683f549f763
2013-03-10 15:23:46 -07:00
commands =
Migrate to oslo.concurrency Namespaces are not used anymore, so imports are for oslo_concurrency, not oslo.concurrency. lockutils direct call is not supported anymore, so using shipped lockutils-wrapper instead. Use ExternalLockFixture to set lock_path for unit testing. Updated cache and cache/_backends module from oslo-incubator to use oslo.concurrency and not incubator version of lockutils module. Dropped lockutils incubator module that is now moved to oslo.concurrency. Not dropping fixture module that includes lockutils fixture since other fixtures are still used in the tree. Closes-Bug: #1387092 Change-Id: I2ba2295f8f5d55f272a9d23555940586b25b5a1c
2014-12-05 18:17:15 +01:00
python setup.py testr --coverage --testr-args='{posargs}'
Getting ready for the client split. Change-Id: Ic2e7d637d2c116dfda3d7ad958ccba39a8da7751
2012-01-10 17:44:27 -08:00
Fix up test running to match jenkins expectation. Change-Id: I215cd92d707f81ed481897704b31188017a5a8b8
2012-06-08 19:46:37 -04:00
[testenv:venv]
Split out pip requires and aligned tox file. Align tox.ini file with standards. Align setup.py with openstack-common standards. Change-Id: I333bbd66648c865a5c97ec2661359ab849274446
2012-02-29 09:39:03 -08:00
commands = {posargs}
Revert "Fix ./run_tests.sh --pep8" We are explicitly trying to get rid of scripts like this and flake8 makes this one non-necessary. Fix run_tests.sh to run flake8 properly. This reverts commit 42243d6eb221d52bf6f62f835726cbe026e43447 Change-Id: I435e34b6acde7931a75f456ccc88da6476581643
2013-05-17 02:18:56 +00:00
Add specific docs build option to tox Add doc venv to align with other OpenStack projects (such as keystone, heat and nova) who are using 'docs' for there doc builds. Change-Id: I0094130224ec2667cdd76f497edf595f09a86d12
2014-08-21 21:24:51 +02:00
[testenv:docs]
devref: consider sphinx warnings as failures We previously introduced issues in our documentation due to not checking for sphinx warnings [1], so let's enforce documentation validation. This commit also fixes minor syntax issues caught by sphinx. Among those, contribute.rst is now properly attached to ToC. [1]: I48ab899077458d99eee6f643577d574106c1ca88 Change-Id: I9170883a20137c343f03d8b052399eacab4ae130
2015-02-20 15:05:07 +01:00
commands = sphinx-build -W -b html doc/source doc/build
Add specific docs build option to tox Add doc venv to align with other OpenStack projects (such as keystone, heat and nova) who are using 'docs' for there doc builds. Change-Id: I0094130224ec2667cdd76f497edf595f09a86d12
2014-08-21 21:24:51 +02:00
Revert "Fix ./run_tests.sh --pep8" We are explicitly trying to get rid of scripts like this and flake8 makes this one non-necessary. Fix run_tests.sh to run flake8 properly. This reverts commit 42243d6eb221d52bf6f62f835726cbe026e43447 Change-Id: I435e34b6acde7931a75f456ccc88da6476581643
2013-05-17 02:18:56 +00:00
[flake8]
# E125 continuation line does not distinguish itself from next logical line
Updated from global requirements Added exclusions for newly triggered errors. Change-Id: I580c4a6a3861c399e010f435c0b92ed719d6a418
2014-06-10 14:35:46 +00:00
# E126 continuation line over-indented for hanging indent
# E128 continuation line under-indented for visual indent
# E129 visually indented line with same indent as next logical line
# E265 block comment should start with ‘# ‘
# H305 imports not grouped correctly
Remove TODO for H404 There is no timeline or intention to fix this - it's a non-functional formatting change. Change-Id: Ib8e75bca41dbcd9dbb188ba8ee03ef51a479d9cc
2014-12-09 13:04:38 -07:00
# H404 multi line docstring should start with a summary
Updated from global requirements Added exclusions for newly triggered errors. Change-Id: I580c4a6a3861c399e010f435c0b92ed719d6a418
2014-06-10 14:35:46 +00:00
# H405 multi line docstring summary not separated with an empty line
hacking: enable H238 (old style class declaration, use new style) The rule was added in hacking 0.10 and is useful for migration to Python 3. Change-Id: I8b45413cf34e5a9db8074f9029410e3b22a92640
2015-01-12 17:27:14 +01:00
ignore = E125,E126,E128,E129,E265,H305,H404,H405
Revert "Fix ./run_tests.sh --pep8" We are explicitly trying to get rid of scripts like this and flake8 makes this one non-necessary. Fix run_tests.sh to run flake8 properly. This reverts commit 42243d6eb221d52bf6f62f835726cbe026e43447 Change-Id: I435e34b6acde7931a75f456ccc88da6476581643
2013-05-17 02:18:56 +00:00
show-source = true
builtins = _
Add script to copy neutron api tests from tempest This change adds a script to automate the copying of api tests from tempest in the style of oslo_incubator. The target path will be neutron/tests/tempest and no manual modifications should be made to this path until such time as neutron api test development is frozen in tempest and development can proceed in the neutron tree. Until that occurs, a policy of manual once-daily synchronization is suggested. The target path includes the name 'tempest' as a clear indication that this is not part of neutron, and that once development is allowed to proceed, its contents should be rewritten and removed until there is nothing left. So long as the tests exist in both the tempest and neutron trees, testing effort will be duplicated. The larger goal is to have the tests in question removed from tempest as per the qa guidelines [1], so this should be temporary. 1: https://wiki.openstack.org/wiki/QA/Tempest-test-removal Change-Id: I3cd55983e610a1d61aae565f88fe5017edba1090
2015-02-21 00:15:12 +00:00
# neutron/tests/tempest needs to be excluded so long as it continues
# to be copied directly from tempest, since tempest and neutron do not
# share a flake8 configuration.
exclude = ./.*,build,dist,neutron/openstack/common/*,neutron/tests/tempest
Add missing translation support Update a number of files to add missing translation support. The patch adds a new hacking check - N320. This ensures that all log messages, except debug ones, have translations. A '# noqa' indicates that the validation will not be done on the specific log message. This should be used in cases where the translations do not need to be done, for example, the log message is logging raw data. Change-Id: I3e1fdd04d87b09dff50950b5e85f5cacfb29afdc Closes-bug: #1314994
2014-05-01 06:10:57 -07:00
[hacking]
Migrate to oslo.i18n Mostly trivial import changes. - oslo.i18n no longer provide install() method to inject _() into globals(), so removed all calls to it; - removed Babel from dependencies (it will now be grabbed by oslo.i18n); - updated tox.ini to ignore import violations for oslo.i18n. Change-Id: I6623d551f512fb7fe9bf35ee734ed6d4c6cbc287
2014-11-21 22:01:08 +01:00
import_exceptions = neutron.i18n
Add missing translation support Update a number of files to add missing translation support. The patch adds a new hacking check - N320. This ensures that all log messages, except debug ones, have translations. A '# noqa' indicates that the validation will not be done on the specific log message. This should be used in cases where the translations do not need to be done, for example, the log message is logging raw data. Change-Id: I3e1fdd04d87b09dff50950b5e85f5cacfb29afdc Closes-bug: #1314994
2014-05-01 06:10:57 -07:00
local-check-factory = neutron.hacking.checks.factory
Copy Permalink