Stop running check_uptodate in the pep8 testenv

As per this discussion on the mailing list:
  http://lists.openstack.org/pipermail/openstack-dev/2014-September/047160.html

We are going to stop enforcing the correctness of the sample config
file, and move to a separate non-voting check test that notifies us when
it is no longer accurate, thus prompting a human to correct it.

This addresses the issue where config options in dependent libraries
(eg. keystone) repeatedly break our gate, without removing the sample
config file that deployers benefit from.

Change-Id: Ief88a693e4967b32f5f2f71b9a683599527a5129
This commit is contained in:
Devananda van der Veen 2014-09-29 15:59:36 -07:00
parent 771cc45f86
commit 9179a1cfc9
1 changed files with 8 additions and 1 deletions

View File

@ -20,7 +20,6 @@ downloadcache = ~/cache/pip
[testenv:pep8]
commands =
flake8 {posargs}
{toxinidir}/tools/config/check_uptodate.sh
# Check that .po and .pot files are valid:
bash -c "find ironic -type f -regex '.*\.pot?' -print0|xargs -0 -n 1 msgfmt --check-format -o /dev/null"
@ -29,7 +28,15 @@ setenv = VIRTUAL_ENV={envdir}
commands =
python setup.py testr --coverage {posargs}
[testenv:checkconfig]
sitepackages = False
envdir = {toxworkdir}/venv
commands =
{toxinidir}/tools/config/check_uptodate.sh
[testenv:genconfig]
sitepackages = False
envdir = {toxworkdir}/venv
commands =
bash tools/config/generate_sample.sh -b . -p ironic -o etc/ironic