| *** diablo_rojo_phone is now known as Guest176 | 00:26 | |
| *** Guest176 is now known as diablo_rojo_phone | 00:27 | |
| *** ysandeep|out is now known as ysandeep | 06:20 | |
| *** soniya is now known as soniya29 | 06:32 | |
| *** ysandeep is now known as ysandeep|afk | 07:42 | |
| *** elodilles_pto is now known as elodilles | 08:42 | |
| ykarel | Hi /me trying to understand why job variants not shown in https://zuul.openstack.org/job/neutron-tempest-plugin-base-nested-switch | 09:08 |
|---|---|---|
| ykarel | https://github.com/openstack/neutron-tempest-plugin/blob/master/zuul.d/base-nested-switch.yaml#L28-L32 one not visible | 09:09 |
| ykarel | suspecting if it's something to do with regex trying https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/869151 | 09:10 |
| ykarel | but it's also not working if testing in https://review.opendev.org/c/openstack/neutron/+/869146 , job is not being triggered | 09:11 |
| ykarel | can someone check on what i am missing | 09:11 |
| *** soniya29 is now known as soniya29|afk | 09:20 | |
| amorin | fungi, ack, will check | 09:41 |
| frickler | ykarel: I'm guessing that this may be because neutron-tempest-plugin is branchless. so your parent https://zuul.openstack.org/job/neutron-tempest-plugin-base doesn't have any stable/* variants | 09:56 |
| *** ysandeep|afk is now known as ysandeep | 09:59 | |
| amorin | fungi, should be good, I added some credit to your account and we are cancelling the current bill | 10:00 |
| ykarel | frickler, but branches: should create those variants, no? | 10:02 |
| frickler | ykarel: iiuc that only matches variants that are created on those branches. but I'm no zuul expert either | 10:03 |
| frickler | amorin: thanks a lot, so we avoided getting shut down this time around, good work | 10:04 |
| ykarel | frickler, ok Thanks, will wait for others, as other ex. openstack-tox have correct variants visible https://zuul.openstack.org/job/openstack-tox, it's also defined in a branchless project openstack-zuul-jobs | 10:04 |
| frickler | ykarel: I did take a quick look at scheduler logs and this seems to support my theory: No matching parents for job neutron-tempest-plugin-base-nested-switch and change <Change 0x7fd7897aa350 openstack/neutron 869146,1> | 10:28 |
| ykarel | frickler, but afaiu https://github.com/openstack/neutron-tempest-plugin/blob/master/zuul.d/base-nested-switch.yaml#L32 should have registered a variant | 10:37 |
| ykarel | like the other ex. of openstack-tox job above | 10:38 |
| frickler | maybe the difference is whether the parent is defined in the same repo or a different one. I would suggest to try to create variants of neutron-tempest-plugin-base too | 10:39 |
| ykarel | frickler, ohkk will try | 10:51 |
| *** soniya29|afk is now known as soniya29 | 10:56 | |
| *** ysandeep is now known as ysandeep|afk | 11:07 | |
| ykarel | frickler, updated https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/869151/2..3/zuul.d/master_jobs.yaml | 11:07 |
| ykarel | but still job not running | 11:07 |
| *** rlandy|out is now known as rlandy | 11:14 | |
| *** ttx is now known as ttx_ | 11:14 | |
| *** ttx[m] is now known as ttx | 11:15 | |
| *** dviroe|out is now known as dviroe | 11:32 | |
| *** dviroe is now known as dviroel | 11:32 | |
| fungi | thanks amorin! | 12:15 |
| frickler | ykarel: still the same message in the logs. so likely indeed we'll need someone with more knowledge of zuul internals to help | 12:16 |
| ykarel | frickler, Thanks, fungi can you please help with ^ | 12:23 |
| fungi | ykarel: maybe once i wake up, though i'll probably end up having to ask on the zuul matrix channel anyway. can you clearly restate: 1. what you did, 2. the behavior you expected, and 3. the behavior that was observed instead? | 12:25 |
| fungi | i'm having a bit of trouble following the discussion above, but it's probably just down to insufficient caffeine levels | 12:26 |
| ykarel | fungi, Thanks summary in my questions though https://meetings.opendev.org/irclogs/%23opendev/%23opendev.2023-01-04.log.html#t2023-01-04T09:08:56 | 12:26 |
| *** ysandeep|afk is now known as ysandeep | 12:27 | |
| fungi | ykarel: sorry i'm really not following which is why i asked you to restate the problem. i'll try to answer my own questions in that case... 1. in the zuul configuration for neutron-tempest-plugin you've created a job named neutron-tempest-plugin-scenario-nested-switch which matches branches stable/queens-ussuri, 2. you're expecting | 12:50 |
| fungi | https://zuul.openstack.org/job/neutron-tempest-plugin-base-nested-switch (a different job) to show branch variants, 3. i'm lost | 12:50 |
| fungi | separately, you've created change 869146 to try to run a neutron-tempest-plugin-scenario-ovn-ussuri job (this is a third job?) and it's not running | 12:51 |
| ykarel | fungi, sorry 1. created two job variants one for releases before ussuri and other for later releases https://github.com/openstack/neutron-tempest-plugin/blob/master/zuul.d/base-nested-switch.yaml#L11-L32 | 12:53 |
| ykarel | 2. i was expecting to see both variants in https://zuul.openstack.org/job/neutron-tempest-plugin-base-nested-switch | 12:53 |
| ykarel | 3. i don't see the other job variant in ^ and the jobs which inheriting from this job before ussuri release not running | 12:53 |
| fungi | for branches before ussuri, i guess you mean? | 12:53 |
| ykarel | yes | 12:53 |
| fungi | okay, backing up... you created two variants somewhere else i guess? i see two different job definitions in the file you just linked. one is the definition for the neutron-tempest-plugin-base-nested-switch job, the other is a definition for a neutron-tempest-plugin-scenario-nested-switch job | 12:56 |
| fungi | no variants though | 12:56 |
| ykarel | fungi, ahh right :( | 12:56 |
| fungi | did you accidentially mis-name one of them? | 12:56 |
| ykarel | totally my bad | 12:56 |
| ykarel | yes right :) | 12:57 |
| fungi | easy fix ;) | 12:57 |
| ykarel | need to check why it happened as i recall it used to work | 12:57 |
| ykarel | Thanks | 12:57 |
| fungi | no worries. just wanted to start at the beginning because i thought i was misunderstanding the premise entirely | 12:57 |
| ykarel | Yes thanks found https://github.com/openstack/neutron-tempest-plugin/commit/8988a01a96df301be2ca9a7536256a4cfec0f087 caused it | 12:58 |
| fungi | when tends to happen when i roll over in bed and pick up the computer without waking up ;) | 12:58 |
| ykarel | Totally my bad on assuming job configs are correct as they were originally :( | 12:59 |
| fungi | it happens! | 13:00 |
| opendevreview | Jeremy Stanley proposed opendev/system-config master: Upgrade to latest Mailman 3 releases https://review.opendev.org/c/opendev/system-config/+/869210 | 13:15 |
| *** bhagyashris is now known as bhagyashris|afk | 13:17 | |
| opendevreview | Merged openstack/project-config master: nodepool: remove ubuntu-bionic-arm64-large label https://review.opendev.org/c/openstack/project-config/+/868441 | 13:38 |
| *** ysandeep is now known as ysandeep|away | 13:49 | |
| opendevreview | Merged opendev/system-config master: Remove old nodepool.yaml testing variables https://review.opendev.org/c/opendev/system-config/+/868432 | 13:57 |
| *** pojadhav- is now known as pojadhav|ruck | 13:58 | |
| opendevreview | Merged opendev/system-config master: linaro: add nodepool cloud configuration https://review.opendev.org/c/opendev/system-config/+/868433 | 14:10 |
| opendevreview | Merged opendev/system-config master: Run nodepool on testing credentials change https://review.opendev.org/c/opendev/system-config/+/868436 | 14:10 |
| frickler | clarkb: I think there is still a patch missing to clean up remainders of us.linaro.cloud or did I just not look close enough https://codesearch.openstack.org/?q=us.linaro.cloud&i=nope&literal=nope&files=&excludeFiles=&repos= | 14:33 |
| *** dviroel is now known as dviroel|lunch | 14:54 | |
| rosmaita | fungi: looks like that python-cinderclient-functional-py38 problem is a real thing | 15:32 |
| rosmaita | don't know if this is relevant, but the "console" tab for -py38 and -py39 are different | 15:32 |
| rosmaita | the -py39 one (which is working fine) shows 3 pre playbook, a run playbook, and 3 post playbook | 15:32 |
| rosmaita | the -py38 one only has pre and post playbook, no run playbook | 15:32 |
| rosmaita | -py38 results: | 15:32 |
| rosmaita | https://zuul.opendev.org/t/openstack/build/6997323310894f48855e4b9139b26f10 | 15:32 |
| rosmaita | -py39 results: https://zuul.opendev.org/t/openstack/build/9ba34208232b4db49c48ceac72716c98 | 15:32 |
| fungi | rosmaita: missing a playbook in the console view is usually a sign that it was killed, most often by a timeout | 15:35 |
| rosmaita | oh, ok, i was hoping i was onto something | 15:35 |
| rosmaita | fungi: eric found something in the cinder tox.ini that might apply here, am trying it now | 15:38 |
| rosmaita | https://review.opendev.org/869226 | 15:38 |
| fungi | rosmaita: in the log, you can see the timeout recorded... | 15:39 |
| fungi | 2023-01-04 15:05:20.963106 | RUN END RESULT_TIMED_OUT: [untrusted : opendev.org/openstack/devstack/playbooks/tox/run-both.yaml@master] | 15:39 |
| fungi | that killed the ansible process executing the run playbook, so the json representation of its results was truncated and zuul's console view skips it as unparseable | 15:40 |
| fungi | probably something that could be improved in the console viewer but would likely require doctoring the json output from the ansible process to turn it into valid json in such cases | 15:41 |
| rosmaita | fungi: yeah, i was just grasping at straws, the run playbook had to be executed because otherwise the tests wouldn't be running! | 15:42 |
| fungi | exactly. something the run playbook executes after stestr probably hung or took way too long. like i said in the meeting, often that's because you ended up with orders of magnitude more logs or subunit than expected | 15:43 |
| *** dviroel|lunch is now known as dviroel | 16:06 | |
| *** marios is now known as marios|out | 16:39 | |
| Clark[m] | frickler: I don't think those changes exist yet as we are still running the builder on it. Next step is to spin up new builder and shut things down? | 16:40 |
| fungi | yes, nb03 is still running there | 16:42 |
| fungi | the openstack tc (based on today's meeting) seems to really really want to pin tox<4 on stable branches. where were the examples of tox auto-upgrading itself when there's a minversion line in tox.ini? | 16:43 |
| Clark[m] | fungi: I think I hit it in zuul-jobs nested tox.ini files for testing roles | 16:47 |
| Clark[m] | And it's not min version but the env requirements iirc | 16:48 |
| fungi | oh | 16:49 |
| Clark[m] | When it creates the nested venv to install those deps it always upgrades tox to latest. Maybe it does the same if the running tox is less than min version? | 16:51 |
| fungi | where does it create the venv? | 17:01 |
| rosmaita | fungi: i think in .tox/.tox | 17:02 |
| fungi | does it delete it afterward? | 17:02 |
| rosmaita | i think it does, not sure though | 17:02 |
| fungi | i see it has created a .tox/.tmp/ which contains only an empty package/ directory | 17:02 |
| rosmaita | no, it doesn't delete the .tox/.tox | 17:03 |
| Clark[m] | fungi: https://review.opendev.org/c/zuul/zuul-jobs/+/866935/7..8/test-playbooks/python/tox.ini I think that is handling the issue there | 17:08 |
| Clark[m] | I want to say elsewhere I just made v4 work | 17:08 |
| Clark[m] | That dep (tox-bindep) only works with <4 so the pin was the only way to make that work | 17:09 |
| frickler | Clark[m]: ah, o.k., I was stumbling about that when looking for where to turn off the cert check | 17:12 |
| Clark[m] | https://review.opendev.org/c/zuul/zuul-jobs/+/866945/10/test-playbooks/python/tox.yaml is the update made to handle tox v4 running there | 17:13 |
| Clark[m] | Since some newer tox v4 requires --'s before posargs | 17:13 |
| frickler | gthiemonge: tweining: fungi: fyi this seems to be the issue for what octavia saw https://github.com/tox-dev/tox/issues/2811 | 17:31 |
| tweining | frickler: thanks. exactly | 17:32 |
| fungi | Clark[m]: rosmaita: thanks, i was able to reproduce the behavior. any tox.requires set will cause tox to upgrade itself to latest regardless of whether tox.min_version is already satisfied or even specified at all | 18:15 |
| rosmaita | fungi: hmmm ... i wonder whether we can use tox<4 in the requires list in the [tox] section to set a ceiling | 18:17 |
| rosmaita | fungi: looks like that could work | 18:20 |
| rosmaita | here's what i see: | 18:20 |
| rosmaita | in my tox.ini i have: | 18:20 |
| fungi | rosmaita: yep, i get the same | 18:20 |
| rosmaita | [tox] | 18:20 |
| rosmaita | distribute = False | 18:20 |
| rosmaita | envlist = py3,pep8 | 18:20 |
| rosmaita | minversion = 3.18.0 | 18:20 |
| rosmaita | # specify virtualenv here to keep local runs consistent with the | 18:20 |
| rosmaita | # gate (it sets the versions of pip, setuptools, and wheel) | 18:20 |
| rosmaita | requires = | 18:20 |
| rosmaita | virtualenv>=20.17.1 | 18:20 |
| rosmaita | tox<3.28 | 18:20 |
| fungi | output says... | 18:20 |
| fungi | .tox installdeps: requestsexceptions, tox<4 | 18:20 |
| fungi | and then it proceeds | 18:21 |
| rosmaita | and then i get: | 18:21 |
| rosmaita | [check-func-jobs] wha'ppen? .tox/.tox/bin/tox --version | 18:21 |
| rosmaita | 3.27.1 imported from /home/brosmait/repos/openstack/python-cinderclient/.tox/.tox/lib/python3.10/site-packages/tox/__init__.py | 18:21 |
| fungi | but my original point was that "pinning" tox for stable branches is going to still require merging tox.ini changes for at least some of them | 18:21 |
| rosmaita | ok, so it looks like we can have a minversion as long as we include a cap | 18:22 |
| rosmaita | fungi: right, but at least these changes are minimally invasive | 18:22 |
| fungi | actually it turns out that tox.min_version is irrelevant (as long as it's already satisfied) | 18:22 |
| fungi | it's when tox.requires is set that this becomes a problem | 18:22 |
| rosmaita | i don't know how many people use tox.requires | 18:23 |
| rosmaita | we use it in cinder so that we could be sure to get the correct version of pip locally to reproduce problems when the pip resolver was rewritten | 18:23 |
| fungi | some projects use it to install tox plugins | 18:24 |
| rosmaita | ok | 18:25 |
| Clark[m] | Running into this was why I decided to focus on nox elsewhere instead of keeping tox alive. I'm ok with bugs and working through them but auto upgrading to latest when not necessary ensuring you hit all the new bugs is not very user friendly | 18:29 |
| rosmaita | Clark[m]: i could not agree more! | 18:35 |
| fungi | running some stats over gerrit activity across our different namespaces... opendev/.* repositories merged 5.2% more changes in 2022 than in 2021 | 19:45 |
| fungi | er, nevermind, we didn't. my eyes compared the wrong lines | 19:46 |
| fungi | though we did have changes committed by 2.5% more contributors in 2022 than in 2021 | 19:47 |
| fungi | also we merged changes to 79% more opendev/.* repos in 2022 than in 2021, granted i expect most of that was retiring old puppetry | 19:48 |
| *** dviroel is now known as dviroel|ourt | 21:09 | |
| opendevreview | Jeremy Stanley proposed opendev/system-config master: Feature our cloud donors on opendev.org https://review.opendev.org/c/opendev/system-config/+/869091 | 21:58 |
| opendevreview | Ade Lee proposed openstack/project-config master: Add FIPS job for ubuntu https://review.opendev.org/c/openstack/project-config/+/867112 | 22:07 |
| *** dasm is now known as dasm|off | 22:14 | |
| *** rlandy is now known as rlandy|out | 23:19 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!