| opendevreview | Andrey Pavlov proposed openstack/election master: Add Andrey Pavlov candidacy for Ec2 API https://review.opendev.org/c/openstack/election/+/891298 | 12:37 |
|---|---|---|
| *** JasonF is now known as JayF | 14:07 | |
| clarkb | gmann: with zuul we have been testing the bounds of python support and I don'tthink we've run into problems doing that yet. I don't know if that is something that should be considered now that you are looking at supporting four python versions in openstack. | 15:09 |
| frickler | sadly there's more to python version testing than python versions, since we use a different platform for each of 3.8 - 3.11, cf. https://review.opendev.org/c/openstack/nova/+/891256 | 15:37 |
| clarkb | frickler: true, but 3.8 and 3.10 are both ubuntu jammy so maybe those can be collapsed into 3.8, 3.9, and 3.11. Are the jobs for 3.9 and 3.11 running on debian now? | 15:53 |
| fungi | clarkb: 891225 proposes not testing 3.9 | 16:10 |
| fungi | "...skip running the Python3.9 testing jobs assuming that anything that works on Python 3.8 and 3.10 will also work on 3.9." | 16:11 |
| fungi | the only reason not to skip 3.10 is that it's the default on latest ubuntu lts | 16:11 |
| fungi | the only reason to test 3.9 is that it's default on debian oldstable, but we'll be testing 3.8 as default from the prior ubuntu lts for a transitional period in order to confirm upgradeability, so presumably 3.9 will also be fine | 16:12 |
| frickler | 3.8 is focal I think? 3.9 centos, 3.10 jammy, 3.11 bookworm. or maybe 3.9 on bullseye for tox testing | 16:15 |
| clarkb | oh I mixed up the ubuntu python versions | 16:18 |
| clarkb | fungi: "Based on the criteria above, all Python-based projects must target and test against, at a minimum" is at odds with the python3.9 "it is ok to skip running the Python3.9 testing" which is where I got confused | 16:19 |
| clarkb | I guess my questions is why test 3.10 at all if you are testing 3.11 | 16:19 |
| fungi | centos is also "best effort" but yes, the mandate from the pti is that we test latest ubuntu default (3.10), latest debian default (3.11), latest python upstream release if available (none presently but maybe non-voting 3.12 will get tacked on later), and ensure upgradeability from whatever versions antelope relied on | 16:20 |
| fungi | which is 3.8 and 3.9, but considering 3.8 "good enough" | 16:20 |
| clarkb | one reason would be if you are testing platforms as frickler mentions but I don't think we are doing that et. But doing so would be a good reason | 16:20 |
| fungi | anything with tight integration at the system level might still want to test on bullseye (or stretch for that matter), but the pti doesn't mandate they do so | 16:21 |
| fungi | e.g. assuming openstaclient will work on bullseye if it works on focal is probably safe | 16:22 |
| fungi | and fwiw i agree the same logic could be used to make 3.10 testing optional as well | 16:22 |
| fungi | i'd feel a little more strongly about trimming the fat there if we were currently proposing adding 3.12 tests, but seeing as how it's still rc for now that's not come up | 16:24 |
| gmann | py3.9 is on focal | 16:27 |
| gmann | we do not need to test py3.9 if we are testing py3.8 and 3.10 which is what we did in 2023.1 I think. | 16:27 |
| gmann | we can remove py310 as we are testing py311 but I feel we can test it in this cycle and in next cycle where we know everything work on both version then we can keep py3.8 and py3.11 in testing | 16:28 |
| gmann | but as support, we do support all in between versions and those can be tested explicitly by projects | 16:28 |
| gmann | but it seems py311 on bookworm need more updates on project side bindep file. adding that as non voting in template so that projects get time to make it work before it become voting in next cycle | 16:30 |
| frickler | it seems 3.9 was added to 2023.2 because the plan was to make it the minimum version? now with that reverted to 3.8, we could likely skip 3.9 testing again, too? | 16:30 |
| gmann | py3.8 was added in 2023.2 as min version so we added both testing in template | 16:31 |
| gmann | last part you meniotned is right. as we test py3.8 and py3.10 we can skip py3.9 | 16:32 |
| gmann | it does not take much time to run though but I feel that will be not much vale | 16:32 |
| gmann | value | 16:32 |
| gmann | or running in periodic | 16:33 |
| gmann | in periodic we can test all and in check/gate pipeline we can skip a few of them | 16:34 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!