As per the current release tested runtime, we
need to test till python 3.11 so adding the test
and updating the same in python classifier in setup.cfg
Change-Id: I231c176a30793b1ff038352b2e74ad3ff52b1b43
The tempest does not support py36 and py37, therefore
we cannot support it in tempest-stress.
This patch removes the py36 and py37 jobs.
Change-Id: I51a80feb6d4a2e9647805d29f20c31cf9cfed8fc
Tempest used to have logging.conf sample which included
stress logging, it was removed from tempest adding more
up date version here.
Also test cases can fail with an assert method
which considered failure not error.
Having the test case exceptions logged.
Stop overriding the working logger name,
as no other action does such override.
Change-Id: I46898b705b58ae5921a4c2e6b95ab4c841dbc9af
The stress section is not visible in the non proxy version
tempest.config.CONF, using the proxy version with stress section.
Change-Id: I862262b9957cdf80db6420b2f810c88bef4ac68d
The template which is used to test runtime for the Zed cycle added
python 3.10 as a non-voting job [1]. So this patch follows the same
thing here.
[1] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/831633
Change-Id: I65f28213bd98ab03751ab910cb5ce4626de8aabc
In Yoga testing, we are making py3.9 job to run as voting, so
adding py3.9 job as voting.
Also, as Tempest is branchless and needs to support older
supported stable branches, let's test it with all the
python version supported in those supported stable branches.
For that, we need to explicitly dd the py jobs instead of using
the template. This way, we will explicitly know that we are testing
all supported python versions when the new release template bumps the
min python version in the template.
Change-Id: Ib147eb983a0635d6f14f0d0fb8ca537224729d89
doc. job is failing as requires some font 'tgtermes.sty'
to generate pdf doc. This patch adds that required
package in bindep.txt to fix doc job.
Change-Id: I77ea8b9dc6c130dcb2d90c8bd6a278a365ec4435
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: I37ff140503eaceee4b7d5e87dcbd4c7921373052
Tempest provides stable library interfaces under tempest.lib.
This patch switches to use it for data_utils.
Tempest will remove the deprecated version of data_utils
in https://review.opendev.org/c/openstack/tempest/+/499869
Change-Id: I82621da3b9fe33063827f4f662b8fe9b07d6acee
This patch enables building .pdf documentation using new 'pdf-docs'
tox environment. The newly created tox environment creates latex
source codes using sphinx-build and then builds the pdf
documentation using make.
Story: 2006070
Task: 35475
Change-Id: Iea3e848b5b914dd837a8fcef154d967ba9fa7008
Switch to openstackdocstheme 2.2.1 version. Using
this version will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: I04809a3cbfaaea711509f4a16548e4813780ddfc
flake8 new release 3.8.0 added new checks and gate pep8
job start failing. hacking 3.0.1 fix the pinning of flake8 to
avoid bringing in a new version with new checks.
Though it is fixed in latest hacking but 2.0 and 3.0 has cap for
flake8 as <4.0.0 which mean flake8 new version 3.9.0 can also
break the pep8 job if new check are added.
To avoid similar gate break in future, we need to bump the hacking min
version.
- http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html
Change-Id: Icc83c54147697b5fd5e1383ad6b23eb19488df13
This commit adds publish-openstack-docs-pti to .zuul.yaml so that we can
verify the document in the gate.
Change-Id: I9ca4f08bc512adde72fdead4d44a86b28f06706a
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove python 2.7 stanza from setup.py
- Remove obsolete sections from setup.cfg
- Update classifiers
- Switch to using sphinx-build, switch to use
openstackdocstheme and update requirements
Change-Id: I67ba5ceb1728ee16b866ecf1b71cbf545a01b7d9
The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.
Fix problems found.
Change-Id: Ib7870977e5aa66d1eb2e41d698ed058ebb65b4c1
With python3.6 and python3.7 jobs added to the Zuul jobs, it makes sense
to add this to the tox config too.
Change-Id: I05055a387877c1be107a88f2d8b96a6e85440939
Remove the support of python3.4, because
in Ubuntu Xenial only (python3.4 is
restricted to <= Mitaka).
In setup.cfg file the python 3.5 is added
In tox.ini the python 3.5 is added
Change-Id: I32cb3c55ce1303ee20738a35724c2e33857e57f0
Closes-Bug: #1801855
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: I4631177d8bc714e8ed4e27d6fab662a99fe6b96c