Commit Graph

24 Commits

Author SHA1 Message Date
Ghanshyam Mann e326856965 Update gate jobs as per the 2023.1 cycle testing runtime
As per 2023.1 testing runtime[1], we need to test on Ubuntu
Jammy (which will be taken care by tempest and devstack patches
to move base jobs to Jammy) and at least single job to run on
Ubutnu Focal (for smooth upgrade). Also, python 3.10 testing is
voting now.

This commit makes python 3.10 functional job as voting and python 3.10
unit test job are voting via generic template. Python 3.8/3.9 jobs are
running on Focal and python 3.10 on Jammy.

[1] https://governance.openstack.org/tc/reference/runtimes/2023.1.html

Change-Id: I97b82399af9a640353ba979965c202afcb224163
2022-11-22 19:47:01 +00:00
OpenStack Release Bot 4d53be7bad Switch to 2023.1 Python3 unit tests and generic template name
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for antelope. Also,
updating the template name to generic one.

See also the PTI in governance [1].

[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html

Change-Id: Ieb6339cd677c76f0158cc19c9a0bf32b2237594d
2022-09-14 09:25:53 +00:00
Takashi Natsume 9101797227 Add Python3 zed unit tests
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for zed.

See also the PTI in governance [1].

I needed to squash in another change that is dropping the py36 and py37
support. We cannot do that separately as those jobs are already failing.

[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html

Change-Id: I378d5c3c1f3e96696670a4865caf5901269a5ee4
2022-06-01 14:08:13 +02:00
Takashi Natsume 73e496ff6c Add Python3 yoga unit tests
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for yoga.

See also the PTI in governance [1].

[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html

Change-Id: I711896a5855fdf881106819b9d05c0b048d46627
2022-02-16 14:44:33 +00:00
Ghanshyam Mann 0c24adb61e Updating python testing as per Yoga testing runtime
Yoga testing runtime[1] has been updated to add py39
testing as voting. Unit tests update are
handled by the job template change in openstack-zuul-job

- https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/820286

this commit makes other required changes in zuul.yaml and
update the classifier in setup.cfg file.

[1] https://governance.openstack.org/tc/reference/runtimes/yoga.html


Change-Id: Ia2caf2508604743cfddbdc76bc520641d1c647d1
2021-12-14 02:26:24 +00:00
Zuul 37e47afc88 Merge "Add openstackclient-plugin-jobs" 2021-05-20 13:00:41 +00:00
Zuul f7c8443c65 Merge "Add functional-py39 tox target" 2021-05-14 15:20:09 +00:00
Zuul 011780a71f Merge "Add Python3 wallaby unit tests" 2021-03-26 09:07:10 +00:00
Takashi Kajinami 714d4e6059 Add openstackclient-plugin-jobs
... to ensure that osc-placement is co-installable with
python-openstackclient and the other plugins.

Change-Id: I9e1bc722e77d181ad2ad8b515538ad01edf85d53
2021-03-15 23:26:10 +09:00
Balazs Gibizer 8def9e82eb Add functional-py39 tox target
This patch also adds a non voting job calling the new target

Depends-On: https://review.opendev.org/760932

Change-Id: I37a2cded4f1685cfe433efe53154da12fedadce6
2020-11-04 13:44:36 +01:00
OpenStack Release Bot 826bc1f97b Add Python3 wallaby unit tests
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for wallaby.

See also the PTI in governance [1].

[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html

Change-Id: I48c0331e297c34ca39fa0090323c2e7d53c6e494
2020-09-11 15:22:00 +00:00
Tetsuro Nakamura e662e51f23 Add to functional-py38 test to check/gate
The gate had py36 and py37 functional tests, but it didn't have py38
functional test. This patch adds functional-py38 tests to the gate.

Change-Id: I4c7f484eedfebe5472c6f360b62459ae17989d7d
2020-09-11 06:10:23 +00:00
OpenStack Release Bot 67e53d5bf2 Add Python3 victoria unit tests
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for victoria.

See also the PTI in governance [1].

[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html

Change-Id: I556e592dcefad3efb9f460bd85e7e42fb52d3126
2020-04-11 18:59:22 +00:00
Tetsuro Nakamura 52ef27a8ce [ussuri][goal] Drop python 2.7 support and testing
OpenStack is dropping the py2.7 support in ussuri cycle.

"osc-placement" is ready with python 3 and ok to drop the
python 2.7 support.

Complete discussion & schedule can be found in
- http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html
- https://etherpad.openstack.org/p/drop-python2-support

Ussuri Communtiy-wide goal:
https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html

Change-Id: Ibd9d1c839f820d8c8ea0ad0979d5dca9223d11dc
2019-11-23 15:57:43 +00:00
Corey Bryant 75f2480427 Add Python 3 Train unit tests
This is a mechanically generated patch to ensure unit testing is in place
for all of the Tested Runtimes for Train.

See the Train python3-updates goal document for details:
https://governance.openstack.org/tc/goals/train/python3-updates.html

Change-Id: I530fcaba664cd21e46ddf8011919954281a04865
Story: #2005924
Task: #34236
2019-07-05 15:43:06 -04:00
Ghanshyam Mann f15d7ad55b Dropping the py35 testing
All the integration testing has been moved to
Bionic now[1] and py3.5 is not tested runtime for
Train or stable/stein[2].

As per below ML thread, we are good to drop the py35
testing now:
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005097.html

[1] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004647.html
[2]
https://governance.openstack.org/tc/reference/runtimes/stein.html
https://governance.openstack.org/tc/reference/runtimes/train.html

Change-Id: I15db8bfd2309814979a72e2a52d88514d9ec4e74
2019-05-10 17:06:21 +00:00
Chris Dent da8cd4d68b Use PlacementFixture in functional tests
Change the functional tests to use the PlacementFixture instead
of devstack as the source of a placement API. This speeds up
the tests considerably and lowers the number of dependencies.

There are four primary changes:

* For each test a PlacementFixture is instantiated, using the
  usual in-RAM db and in-process placement.

* Because of some exceedingly confusing optimizations in
  osc_lib and python-openstackclient, done to improve start
  up time, a session to placement was caching the service
  url. This meant that after a first test succeeded, every
  subsequent one would not because it was trying to talk
  to a fake hostname that was no longer being intercepted.

  The workaround for this was to monkeypatch the method
  in the ClientCache class which provides access to a client (per
  service-type). The replacement method makes a new client
  every time.

* The previous tests would subprocess out to a real call of
  the openstack command and then interpret the results.

  Now, a run() method on OpenStackShell is called instead.
  This accepts arguments in the same way, but we need to
  a) capture stderr and stdout, b) make a try/except for
  SystemExit to get some error responses (mostly from
  the argparse lib which has a tendency to exit for you
  instead of politely telling you it wants to), c) deal
  with errors from commands ourself rather than using
  exceptions from the subprocess module.

  Switching to this form means that logging becomes in-process
  and more visible. To accomodate this the Capture fixture
  from placement is used. This was chosen because we are already
  pulling in the PlacementFixture. If this seems icky, I can fix
  it with a local one. This was the shorter path.

* The legacy dsvm jobs have been removed in favor of "standard"
  functional jobs for 2.7 and 3.6 that require openstack/placement.
  The playbooks associated with the legacy jobs are removed.

  tox.ini is adjusted to reflect this new setup. Because tox-siblings
  functional is being used, we don't want to share tox envs with the unit
  tests. The 3.5 functional job is removed because we no longer target
  that.

After running these for a while it became clear that there were
intermittent failures being caused by subunit attachments being too
large. This was eventually traced back to logging from all packages
being set to DEBUG even when something else was requested. That was
traced back to a poor interaction between the way that osc does
logging and the way oslo_logging does logging (used by placement and
thus the placement fixture). The workaround, embodied in the
RESET_LOGGING list in osc_placement/tests/functional/base.py, is to
get and reset the log level for a subset of the packages that are
used.

Change-Id: I7deda200b372ff6a7ba67b0c4fa0e53c4fa16ffc
Story: 2005411
Task: 30428
2019-05-03 15:04:56 -06:00
OpenDev Sysadmins f79dbf7277 OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
2019-04-19 19:32:00 +00:00
Corey Bryant 7b65cd6e4c add python 3.7 unit test job
This is a mechanically generated patch to add a unit test job running
under Python 3.7.

See ML discussion here [1] for context.

[1] http://lists.openstack.org/pipermail/openstack-dev/2018-October/135626.html

Change-Id: I0d5ea51a27023f13a4fc237a5a3591f3663eec2d
Story: #2004073
Task: #27433
2019-02-15 15:02:54 -05:00
Doug Hellmann 918c20e2ba add python 3.6 unit test job
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: Ibff1da1c23bc3501440f931740d0335809eb57b9
Story: #2002586
Task: #24315
2018-09-09 05:56:03 -04:00
Doug Hellmann 76b9674684 switch documentation job to new PTI
This is a mechanically generated patch to switch the documentation
jobs to use the new PTI versions of the jobs 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: I5a5955166f7531e95efcd159ecb6ae0b1525f300
Story: #2002586
Task: #24315
2018-09-09 05:55:58 -04:00
Doug Hellmann f0c3b122f5 import zuul job settings from project-config
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.

Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.

Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.

See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html

Change-Id: If6658def44e09bc1c7a84eac9c2bb030308f2859
Story: #2002586
Task: #24315
2018-09-09 05:55:20 -04:00
Matt Riedemann c9de308d00 Add osc-placement-dsvm-functional-py3 job
This adds a py3 variant of the functional dsvm job.
This still uses devstack-gate (not native zuulv3) because
I'm not yet cool enough to know how to do native zuulv3 things.

Swift has to be disabled since it doesn't support py3 (this is
something all other py3 jobs are doing right now too).

Change-Id: I9a0074d9658eab76b7c73b820f498d61b89545e7
2018-03-05 09:00:49 -05:00
Matt Riedemann 2e8b471759 Migrate legacy-osc-placement-dsvm-functional job in-tree
This migrates the legacy-osc-placement-dsvm-functional job
from openstack-zuul-jobs and renames it to drop the legacy part
and branch override stuff.

Change-Id: I6dfcd4e327ea535fdee3ce740c9b817ed790de7e
2018-03-05 08:57:56 -05:00