There are multiple issues with the gate. This patch combines the fixes
to unblock the gate.
1. Zuul deprecated (and removed) declaring shared queues at a pipeline
level [1]. This patch fixes the syntax to make the gate work again for
freezer.
2. Zuul CI jobs default nodeset is now Ubuntu 22.04 Jammy Jellyfish,
that does not provide anymore python2 binary, so python-dev needs to be
removed from bindep.txt
3. Latest tox does not allow to list the passed environment variables
in one line separated by space. One option is to list them in separate
lines. Also, external command allowing variable name changed.
basepython as python3 is also conflicts now and it is not necessary.
It looks like tox requires now to install now explicitly all the
requirements listed in requirements.txt.
tox.ini is updated accordingly to the above listed problems.
[1] https://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html
Change-Id: I3c95bb48c7fdd0c752db121f1745f64a53b5a0e5
Tox trying to install latest versions for building docs which may
not be supported by stable and lower branches, so should be
restricted by respective version's upper-constraints.txt
Change-Id: I47416c166d07104ddf647cbbdb17525614311673
The docs requirements migrated to doc/requirements.txt
we need not install things from requirements.txt.
Change-Id: I593e1d17d54690764b8c43c34b19adbdba07ee65
Update to newest hacking version, it has only minimal changes and full
support for Python 3.
Python modules related to coding style checks (listed in blacklist.txt in
openstack/requirements repo) are dropped from lower-constraints.txt
as they are not actually used in tests (other than pep8).
Change-Id: Id4b5f045563640f4b9c73ecafd4ebf8d3ff2c269
Sphinx 1.8 introduced [1] the '--keep-going' argument which, as its name
suggests, keeps the build running when it encounters non-fatal errors.
This is exceptionally useful in avoiding a continuous edit-build loop
when undertaking large doc reworks where multiple errors may be
introduced.
[1] https://github.com/sphinx-doc/sphinx/commit/e3483e9b045
Change-Id: I18032bd40489c4b1c511713b0f1c5bb1aca7c1d2
This is a mechanically generated patch to add a unit test job running
under Python 3.6 as part of the python3-first goal.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I0381da9ffe40299f55a31a1c499b509b3eba05ef
Quotes around {posargs} cause the entire string to be combined into one
arg that gets passed to stestr. This prevents passing multiple args
(e.g. '--concurrency=16 some-regex')
Change-Id: I60a754d28ca56fb7f995d0af5c03a7734c5ba8b1
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: I9df9ee69b590e2589b7e687a7062bbfb19b6efbd
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Co-Authored-By: Nguyen Hai <nguyentrihai93@gmail.com>
Co-Authored-By: Trinh Nguyen <dangtrinhnt@gmail.com>
According to Openstack summit session [1],
stestr is maintained project to which all Openstack projects should migrate.
Let's switch to stestr as other projects have already moved to it.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: I0ec7bc7926e57b243e38b2c696815e648d0b3f61
This patch adds doc8 check for .rst files to pep8.
Files that fail doc8 check are also fixed.
Ignores D000, D001 of doc8 check. This requires lot of changes
and should be done in a separated patch.
Change-Id: I7d021e6fee3e12feff7c219e09c545da5274c354
Create a tox environment for running the unit tests against the lower
bounds of the dependencies.
Create a lower-constraints.txt to be used to enforce the lower bounds
in those tests.
Add openstack-tox-lower-constraints job to the zuul configuration.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Change-Id: Ic5f68cd606f5dd17e4cca2facf3141960180be26
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Some of the available checks are disabled by default, like:
[H106] Don’t put vim configuration in source files
[H203] Use assertIs(Not)None to check for None
Change-Id: Ifed3a0b3514ac10a4c2b49b904f39a3faf2f15b5
We do not have python 3.4 in setup.cfg which declares the explicit
supported versions and we support py35 now.so it is no need to keep
the supoort for py34.
Change-Id: Idbf148074438ef058dbcbff0b97ce27fcf1663ca
This patch adds pep8 check on freezer/tests and fixes all
code style problems.
Change-Id: I178e4cbdfcbe610fbee1e6257b0d2b2b922d5411
Closes-Bug: #1643952
Signed-off-by: Ruslan Aliev <raliev@mirantis.com>
Openstack infra now supports upper constraints for all jobs.
Update tox.ini to use upper constraints for all jobs.
Change-Id: I524b0a31ecf2253bedee52b56109f5ff79b428cb
Closes-bug: #1614361
Remove select line in tox.ini.
Currently checks are not being run.
Run pep8 checks.
Fix code to pass pep8 checks.
Change-Id: Iacef4386b1214f95b1bd106c17a5f714f948a1a1
Closes-Bug: #1593452
When Development environment is under a proxy then tox is failed even if environment variables of the proxy are set.
Change-Id: Ia59a522f9ed9250e7b754eca49af600b381554fd
Because python creates pyc files during tox runs, certain
changes in the tree, like deletes of files, or switching
branches, can create spurious errors.
Change-Id: I7908520f6e2935ffacf5d914a01078939392e2e2
Closes-Bug: #1368661
With this patch the scripts are generated by automatically
only from setuptools. The /bin/freezerc script is removed
and the content is incorporated in freezer.main
This patch should make more portable freezer on
win32 platform.
Unfortunately in order to support win32 platforms
we need to use a version of PBR >= 1.0.0,
to support env markers. Now requirements.txt reflects that
Change-Id: I31a4a13711f8c042072e3cc8785078fdbb971cb7
Freezer currently uses pytest to execute unittests.
As we need to be consistent with the frameworks by the
other OS project, we are porting our tests to tests.
Change-Id: Ib755771efe496e467079dc2e990ca89a2e513eb6
Implements blueprint: swift-to-testr
Currently the deps of oslo.i18n wasn't aligned with
Kilo global-requirements.
Now tests are not execute by runtests.py but tox
call directly py.test, as there was a bug in the exec
of runtests.py. This is a temporary solution as
testr will be used soon as testing framework
Close bug: 1498078
Change-Id: I07daddb14ab75fe089c98c8e00c24ecb550ada82
The test provided in the tests/integration directory
execute the command line version of the freezer-agent.
The tests execute backups and restores, passing the parameters
on the command line, and check the results.
Types of integration tests depend on the environment variables defined.
Local storage tests are enabled by default and use temporary
files and directories, while SSH and Swift storage testing need
also access to existing external resources.
To enable the ssh storage testing, the following environment
variables need to be defined:
- FREEZER_TEST_SSH_USERNAME
- FREEZER_TEST_SSH_KEY
- FREEZER_TEST_SSH_HOST
- FREEZER_TEST_CONTAINER
To enable the swift storage testing, the following environment
variables need to be defined:
- FREEZER_TEST_OS_USERNAME
- FREEZER_TEST_OS_TENANT_NAME
- FREEZER_TEST_OS_REGION_NAME
- FREEZER_TEST_OS_PASSWORD
- FREEZER_TEST_OS_AUTH_URL
Tests involving LVM snapshots are executed only with superuser
privileges and if the following env variable is not defined:
- FREEZER_TEST_NO_LVM
Change-Id: I39f0c9bf62f7c82f81ad95f19cf0f7aefb059633
Elod Illes