Commit Graph

5 Commits (db4066912b91d9fed410f6c1da8839700706f837)

Author SHA1 Message Date
Martin Kopec dc84423b72 Inclusive jargon
Following stestr's example where arguments such as --blacklist-file,
--black-regex and --whitelist-file are deprecated since its
3.1.0 release, let's do the change here as well in order to
get tempest consumers some time for the transition.

This change deprecates the following arguments and replaces them
by new ones which are functionally equivavelnt:
* --black-regex is replaced by --exclude-regex
* --blacklist-file is replaced by --exclude-list
* --whitelist-file is replaced by --include-list

For now, Tempest will accept both (new and old) arguments to make
the transition smoother for all consumers.

The patch also bumps min version of tox to 3.18.0 in order to
replace tox's whitelist_externals by allowlist_externals option:

Change-Id: I3e09b31f63d2cd7ea41c48e62432bd3bc54fcf44
2 years ago
Ghanshyam Mann 721aeca8ef Unskip Device detach compute tests on Focal
During migrating the testing to Ubutnu Focal,
we skipped few device detach tests due to bug#1882521

Now Nova bug#1882521 is fixed so let's unskip those tests.

Change-Id: I9e48d72fc1192a775671ca339e0339e8ec1afa17
Related-Bug: #1882521
Related-Bug: #1894804
3 years ago
Ghanshyam Mann 1ca760cd29 Migrate tempest jobs to focal
As per victoria cycle testing runtime and community goal[1]
we need to migrate upstream CI/CD to Ubuntu Focal(20.04).

Most of the Tempest jobs will be migrate automatically once devstack
base job start running on Focal(Depends-On).

Few job like tempest-full-multinode and plugin sanity job needs to override
the nodeset. multinode job needs to run on Bionic till stable/ussuri and
on focal from master(victoria) onwards.

stable jobs testing stable branch needs to keep running on their supported
distro version which is bionic from stein till ussuri.

Keep 'tempest-integrated-compute' to run on bionic until is fixed.



Change-Id: I51fbd32a60c931d404e59e975049f7b01ed900dc
3 years ago
Luigi Toscano abc06c36e8 Integrated gate storage/swift: blacklist more tests
Add all the scenario network tests which mainly involves network
and compute.
Also, fix an incorrect entry which most likely has no matches
( are different
files at the same level).

Change-Id: I936f263b4c1d96689d276ecfcf25ef1560d66ced
3 years ago
Ghanshyam Mann a699445d28 Define the Integrated-gate-storage gate template
tempest-full job run all services API and scenario tests (non slow)
and this job is part of Integrated-gate gate template which run on
multiple services (nova, neutron, cinder, glance, placement) check
and gate pipeline.

But there are many unrelated tests run on each project gate. For example,
neutron gate run cinder only tests and fail due to cinder bugs. There is
no point of breaking the neutron gate due to cinder only test failure and
slow down the neutron development phase.

This is what we dicussed in Train PTG in denver to improve the integrated
gate[1] and came up with idea of split the integated-gate template into
much logical way so that only dependent services tests run on their gate.

One way was to move the service only tests to service tempest plugin side
but Tempest is used by interop as well as on production cloud testing so
moving the test is not good idea.

This commit propose the idea of defining the 'Integrated-gate-storage'
gate template for cinder gate which will run Cinder, Glance, Swift and
Nova tests.

ML discussion:

Next step will be to replace the Integrated-gate-py3 template with new
Integrated-gate-storage template on cinder and glance gate.


Change-Id: Iae7d26325228aad0edb94f7e191c8fd0d60e1362
4 years ago