Tuesday, 2023-08-29

opendevreviewOpenStack Proposal Bot proposed openstack/requirements master: update constraint for taskflow to new release 5.4.0  https://review.opendev.org/c/openstack/requirements/+/89303511:31
opendevreviewOpenStack Proposal Bot proposed openstack/requirements master: update constraint for glance_store to new release 4.6.1  https://review.opendev.org/c/openstack/requirements/+/89303611:44
opendevreviewOpenStack Proposal Bot proposed openstack/requirements master: update constraint for heat-translator to new release 2.8.0  https://review.opendev.org/c/openstack/requirements/+/89303711:46
opendevreviewOpenStack Proposal Bot proposed openstack/requirements master: update constraint for kuryr-lib to new release 2.8.0  https://review.opendev.org/c/openstack/requirements/+/89303812:09
opendevreviewOpenStack Proposal Bot proposed openstack/requirements master: update constraint for keystonemiddleware to new release 10.4.1  https://review.opendev.org/c/openstack/requirements/+/89303912:11
opendevreviewOpenStack Proposal Bot proposed openstack/requirements master: update constraint for monasca-common to new release 3.8.0  https://review.opendev.org/c/openstack/requirements/+/89304012:21
kubajjHi frickler, is it possible to test the failing tests for upper constraints locally? Do I need any particular set up?12:26
kubajjI know these questions might be a bit basic, but I do not want to waste zuul power by pushing everything to gerrit for testing.12:27
opendevreviewOpenStack Proposal Bot proposed openstack/requirements master: update constraint for oslo.middleware to new release 5.2.0  https://review.opendev.org/c/openstack/requirements/+/89304212:36
opendevreviewOpenStack Proposal Bot proposed openstack/requirements master: update constraint for oslo.db to new release 14.0.0  https://review.opendev.org/c/openstack/requirements/+/89304312:36
opendevreviewOpenStack Proposal Bot proposed openstack/requirements master: update constraint for keystoneauth1 to new release 5.3.0  https://review.opendev.org/c/openstack/requirements/+/89306013:21
fricklerkubajj: not sure what tests you are talking about. for a cross-project job, you can run tox locally and manually install the bumped requirements into your tox env13:30
kubajjfrickler: yeah, I meant the cross-project jobs.13:31
fricklerkubajj: those in general are only unit tests, though some projects still require a special setup for those, let me know if you run into any specific issues13:38
kubajjfrickler: I am just trying to setup a reliable environment for testing which packages cause the issues. From my understanding, the problem lies in conflicts between global requirements and upper constraints or am I wrong?13:40
fricklerkubajj: no, such conflicts should be detected and resolved by pip. the failures mostly are due to real changes in behavior for updated packages. some just need tests to be amended, some may also need actual code changes, for example if deprecated functions got removed13:42
fricklerkubajj: most of the time as a first step it will be good enough if you can single out a specific update that is causing tests to fail13:44
fricklerkubajj: maybe one idea would be to split the upper-constraints bump into a series of single-line changes, so that one could run git-bisect against the result13:45
fricklerthat could even be automated I think. then in theory for each failing cross-project job that would identify at least the first failing bump13:46
opendevreviewMerged openstack/requirements master: update constraint for oslo.policy to new release 4.2.1  https://review.opendev.org/c/openstack/requirements/+/89292318:08
opendevreviewMerged openstack/requirements master: update constraint for oslo.versionedobjects to new release 3.2.0  https://review.opendev.org/c/openstack/requirements/+/89294618:08
*** melwitt_ is now known as melwitt18:34

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!