A month ago a flake8 3.6.0 version was released and it's been causing
pep8 check gate fail since then.
This patch
* removes flake8 dependency from tox.ini file, because otherwise
version defined in test-requirements.txt is not taken into account.
* flake8==2.0 version is too old so the version is bumped, however, it's
limited for versions < 3.6.0
* pyflakes version needs to be bumped too otherwise it doesn't work
with newer flake8 versions
Change-Id: I470d1e8ae69aff87dcc9bf9dfa988370efb2817d
Usage: $ refstack-client config --use-test-accounts <path to test
accounts file>
If not accounts.yaml is passed then:
$ refstack-client config
It will generate accounts.yaml and tempest.conf in etc folder
* It adds support for the above command
* Added zuul based devstack job to run the same
* let setup_env handles the installation of tempestconf
* updated git url for tempest
* It also generates accounts.yaml if no account file is
passed
* we can --overrides flag to overrides the tempest.conf
value.
* volume-feature-enabled.api_v2=True is added as default
in overrides as it is deprecated in Rocky cycle but needed
for interop tests.
Depends-On: https://review.openstack.org/589260
Story: 2001696
Task: 19758
Change-Id: I9cabfc52672e7a8a54792ca9d867c62babf12cb7
Implement optional cleanup to support the new PTI jobs
for documentation which won't use tox anymore.
Docs tox environment will still available for developers but
it is no loger used in the gate to construct the documentation.
See http://lists.openstack.org/pipermail/openstack-dev/2017-December/125710.html
Change-Id: Ib26b711365389c59658f9d7f6cafd5acb736dfce
* Let tox auto handles the setting for LANG variables in order to
fix py35 tox venv creation and installation.
* Use OS_TEST_PATH in tox variables and re-use it
Change-Id: I534ed66d154b6b05a03a06eb0baa0ff23d851f4e
* As stestr is the successor of testr, it's time to switch to
stestr for running refstack unit tests.
Change-Id: I3b9c0e2b4363dec24bad43bf5cfbeef4ecc7a37c
Running py2* post py3* tests results in error. Add
'rm -f .testrepository/times.dbm' command in testenv to
resolve this.
Change-Id: I29d6247e11f1c9c207e9b89c0ae41f590141d281
Added feature to upload test results in to Refstack API signed with
your personal RSA key. Just do upload with key '-i PATH_TO_PRIVATE_KEY'.
You can use your general OpenSSH key ~/.ssh/id-rsa or
generate a new one with 'ssh-keygen -b 4096'.
Change-Id: Icce6d7146f0fa9de892d1f4785ef24f17fc9b286
Previously, after the run_tempest script, was run, all post-processing
was done only if the returncode was 0. If it was non-zero, an error message
was given. This was an oversight, as the run_tempest script will return a code
of 1 when any test case fails. This leaves the unintended side effect of refstack
not parsing the results or producing the output json when Tempest successfully
runs, but a test case fails.
Checking for the existence of the expected subunit file will at least validate
that the Tempest test was at least started successfully, and didn't fail to run
due to some misconfiguration in the environment.
Change-Id: I541b798db41b713525efeb8dedfb9347be780a3f
