All normal CI jobs use wheels that have been built previously, but
possibly are no longer buildable with the current set of requirements.
Add jobs that do not use these wheels to the experimental pipeline for
now.
Change-Id: Id2a5bca02ad37b5fbe3391ece9944112234ac52a
The OpenDev team is looking towards removing CentOS 7 and Ubuntu Xenial
test nodes from Zuul and Nodepool. In the case of Xenial this distro
release has been EOL for some time now, and in the case of CentOS 7 will
go EOL in the near future. Removing these distro releases will allow the
OpenDev team to focus on building images for modern releases as well as
freeing up space on our mirror filesystems for additional mirror
content.
At this point OpenStack should largely be on CentOS Stream and Ubuntu
Bionic, Focal, and Jammy. We don't expect this to create a major impact.
Change-Id: I1ca9403525df470a7da8c1f02bdfb8d4ea90c670
In order to allow better test coverage for version updates that are
known to be critical (like dnspython or eventlet), add some more jobs to
the experimental list:
- nova-ceph-multinode
- nova-next
- tempest-integrated-storage
Change-Id: Id9540ae53a98a9a782ce753c92e31b6ad6e09534
Debian buster is the old old release of Debian (succeeded by bullseye
and bookworm). The OpenDev team is attempting to clean up the old debian
release which means dropping the wheel cache and wheel cache checks.
Note this change may need to be backported.
Change-Id: I37d36459368826deebdf0920690155f307249a67
mypy is a linter, not something that is used at runtime. Move it to the
blacklist.
This also reverts commit 2bbbdb9991 as a
cross-project job no longer makes sense with the newly blacklisted
dependency.
Change-Id: Iaf6d2c4aed92f35240b393939bbf76fd7d5d9aa2
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
There are some issues with testing masakari, make the cross job
non-voting for now so we can proceed with the release.
Change-Id: I4082a0b7d096cb62aed90e8ff4eb642cfc4aa030
This reverts commit 0416165ee2.
Reason for revert: seems a lot of projects still depend on python 3.8 in certain CI scenarios, we should try to keep u-c compatible with that, possibly by reintroducting version specific reqs
Made this a partial revert, don't restore the arm job.
Change-Id: I608d76fe40185723247d373d2394e59f1c7fe0ad
Start checking requirements on python3.11 to get early warnings about
upcoming issues. Non-voting for now.
Change-Id: I7713029b95beb69d87f5cba66997fd4ba422c6b0
Python3.8 is no longer part of the PTI and some libraries are dropping
support for it in new releases. Make our life easy and stop generating
and checking constraints for it rather than reintroducing python_version
specific constraints again.
Change-Id: Iee6b65ad1cac13df33ea96119f3cf4b70e2e307e
Python3.8 is no longer covered according to the PTI. Use python3.10 for
the cross-swift test just like for everyone else.
Change-Id: I40ce9acc7a3672afd2e4e0c0b62c639957097ddc
The upper-constraint for mypy was raised recently via generate-
constraints by change Ifaf60a747200 without there being a test
that ensures such a raise doesn't break anything. We can use
the cinder mypy job for this purpose, which has been a voting
job in cinder since change Ib6c8a7a1a8eb (July 2022).
Change-Id: I4d68d8abb48b4179dfd5e838837b2406fd90913b
Requirements repo tox.ini is fixed for tox4 things:
- https://review.opendev.org/q/I7bc7c98954395765f16cc943e5c826983db5dba0
But requirements gate run amny other projects checks job which are
failing and need tox4 fix on projetc side tox.ini. Instead of keeping
requirements gate broken until projects fix the things, let's pin
tox<4 until then. There are many projects in those failing list which
fix can take time due to holidays season and less acrtive contributors.
Change-Id: I79e65a25efe9b3ef9f4df14e9fa4d42b3cc6ef87
As the base job (unittests job) moved to the ubuntu-jammy
nodeset, requirement-checks job also start running on
ubuntu-jammy which is right thing for master but for stable
branch also it run on ubuntu-jammy which is incorrect and
start failing:
- https://zuul.opendev.org/t/openstack/build/811ca9311b894b97bfae4438070e5e22
Setting the correct nodeset as per the master/stable branch.
Change-Id: Ie676079c0b798335ab2a82c03fe4715e0eee4d57
firefox on jammy looks to be broken. Wheil we figureout how to fix it
we have 3 options:
1) Do nothing and be unable to merge anything ;
2) Make the npm job non-voting ; or
3) Switch back to focal
Clearly the change goes for option 3
Change-Id: I211333a6da03282feba82cbcdf9309f1a17ee7af
The PTI has dropped python3.8 as a platform for the 2023.1 cycle, switch
all cross testing jobs to use python3.10 instead.
Swift doesn't support Ubuntu 22.04 yet so keep them running on py38
instead until they are compliant with 2023.1 testing requirements.
Change-Id: I039171301da04f5005eee8d6c4ff8d94bec6b165
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: Ic857b96ac940d76b5e908fa23c5a412515ea9799
Requirements for confluent-kafka-python are behind what Debian offers so
there is no point in building librdkafka anymore.
Change-Id: Iebb88900ba9a78ba3c2b0348bdc3fca67279bfdf
This change introduces cross-project tests for telemetry services(Aodh
and Ceilometer), so that we can detect any issue caused by change in
u-c file earlier.
Change-Id: I9830e9c8339c19e1bd4a6b878f8839f0a2e88e5a
This change introduces cross-project tests for Heat, so that we can
detect any issue caused by change in u-c file earlier.
Change-Id: I8672ed403db5f4b72a4fba589828ab8ccabe8c16
CentOS 8 has reached EOL and OpenDev is beginning the process to remove
these nodes. We do have CentOS 8 Stream nodes so jobs have been switched
over to use those instead.
Note this change will likely need to be backported if we run centos-8
jobs on older branches.
Change-Id: Ibcfacb7289a05556228ff5c2f1cc6a2679291fc0
This reverts part of [0] which was necessary since the tempest job did
not actually test the proposed upper-constraints check.
[0] I62350b017f91f827b7a20c78b8c4fee9113d659f
Change-Id: I308be2ec7c21c9e6a4ecfe94ece3ae27f29e67ff
Neutron tox jobs are getting ever slower, neutron itself has therefore
recently increased their tox job timeout to 1h[0]. Do the same here in
order to avoid failures.
[0] I415c1d67757354243855ac44862f245eb08887c8
Change-Id: Icad8e95cbb78338b2e2d93a1af0de9ece04f09f0
Jens Harbott
OpenStack Release Bot
yatinkarel