Thursday, 2021-06-24

prometheanfireianw: ack00:02
ianwhttps://nb02.opendev.org/centos-8-stream-0000125109.log timed out00:03
ianwi can't see any obvious reason why00:03
ianw2021-06-23 21:54:49.212 | Updating cache of https://opendev.org/airship/airshipctl.git in /opt/dib_cache/source-repositories/airshipctl_6f1e843d56659249749fcf04437fbc7625bd9af9 with ref *00:04
ianw2021-06-23 22:14:23.855 | Cloning from zuul-website-media cache and applying ref *00:04
ianwthat's about ... 20 minutes to check and update the opendev cache.  i'm not sure if that's longer than usual00:04
opendevreviewIan Wienand proposed openstack/diskimage-builder master: cache-url : turn down verbose curl  https://review.opendev.org/c/openstack/diskimage-builder/+/79779100:11
*** ysandeep|out is now known as ysandeep00:32
ianwlooks like the command that is hanging is "udevadm trigger --sysname-match=hw_random --settle"00:38
ianwafaics that must be coming from rng-tools; i've filed a bug https://bugzilla.redhat.com/show_bug.cgi?id=197558801:28
opendevreviewIan Wienand proposed openstack/diskimage-builder master: Revert "Install rng-tools in Red Hat family distro images"  https://review.opendev.org/c/openstack/diskimage-builder/+/79779401:32
*** ykarel|away is now known as ykarel04:31
*** marios is now known as marios|ruck05:01
*** bhagyashris_ is now known as bhagyashris05:13
opendevreviewIan Wienand proposed openstack/project-config master: nodepool: pause centos-8-stream builds  https://review.opendev.org/c/openstack/project-config/+/79780606:32
*** rpittau|afk is now known as rpittau07:21
opendevreviewMerged openstack/project-config master: nodepool: pause centos-8-stream builds  https://review.opendev.org/c/openstack/project-config/+/79780607:22
*** jpena|off is now known as jpena07:36
*** ykarel is now known as ykarel|lunch08:34
*** sshnaidm|afk is now known as sshnaidm08:45
*** marios is now known as marios|ruck09:48
*** bhagyashris_ is now known as bhagyashris09:48
opendevreviewFlorian Haas proposed opendev/git-review master: Doc updates for Git "core.hooksPath" option support  https://review.opendev.org/c/opendev/git-review/+/79764310:06
*** ykarel|lunch is now known as ykarel10:21
opendevreviewAnanya Banerjee proposed opendev/elastic-recheck master: Run elastic-recheck container  https://review.opendev.org/c/opendev/elastic-recheck/+/72962310:44
opendevreviewAnanya Banerjee proposed opendev/elastic-recheck master: Run elastic-recheck container  https://review.opendev.org/c/opendev/elastic-recheck/+/72962311:10
*** dviroel|out is now known as dviroel11:32
*** jpena is now known as jpena|lunch11:39
fungii'll send a status notice here shortly about our upcoming 14:00 utc zuul outage11:52
fungistatus notice Our Zuul gating CI/CD services will be offline briefly starting around 14:00 UTC (in roughly two hours from now) in order to apply some critical security updates, and is not expected to last more than 30 minutes; another notice will follow closer to the maintenance window.11:56
fungisomething like that11:56
fungistatus notice Our Zuul gating CI/CD services will be offline starting around 14:00 UTC (in roughly two hours from now) in order to apply some critical security updates, and is not expected to remain offline for more than 30 minutes.11:59
fungipolished slightly and dropped the bit about the second notice, since it's superfluous12:00
fungisending12:00
fungi#status notice Our Zuul gating CI/CD services will be offline starting around 14:00 UTC (in roughly two hours from now) in order to apply some critical security updates, and is not expected to remain offline for more than 30 minutes.12:00
opendevstatusfungi: sending notice12:00
-opendevstatus- NOTICE: Our Zuul gating CI/CD services will be offline starting around 14:00 UTC (in roughly two hours from now) in order to apply some critical security updates, and is not expected to remain offline for more than 30 minutes.12:00
fungimmm, technically should have been "are not expected"12:01
fungipre-coffee grammar12:02
mordredfungi: ok. I started reading a bit more through the pep 517 stuff and I think I'm starting to form a concrete idea about what a pep517 pbr looks like12:03
opendevstatusfungi: finished sending notice12:03
fungiawesome12:03
fungiwould pep-517 pbr become a setuptools wrapper, rather than being wrapped by setuptools?12:04
opendevreviewMerged opendev/git-review master: Doc updates for Git "core.hooksPath" option support  https://review.opendev.org/c/opendev/git-review/+/79764312:05
mordredit occurs to me that since build-time requirements don't have to be feared with existential dread - we could do neat things, like, for instnace, have pbr517 depend on bindep and do a bindep check for a build tag and print an error message if your project declares system build depends but doesn't have them yet tries to build a wheel12:05
fungineat12:05
fungiyeah, not a terrible idea12:05
mordredfungi: I *actualy* think it would be nicer to just ditch setuptools completely. there is a lot of complexity in setuptools to support things we simply don't do12:06
mordredand the few methods we actually need to implement would be much more straightfoward if we weren't also asking setuptools to do things12:06
fungifair, but there's also a lot of complexity in setuptools we rely on and wouldn't necessarily want to have to replicate12:06
mordredpossibly12:06
mordredit's possible we'd still want to use it - I think a step-wise implementation DEFINITELY would keep setuptools12:07
fungii suppose we could replace it with something like flit, but it only creates wheels and not sdists12:07
mordredthing is - creating sdists for us shouldn't be terribly hard - we already override a lot of what setuptools thinks about that12:07
mordredthat's one of the benefit of only supporting one way of doing things :)12:07
mordredI might, of course, be horribly wrong and setuptools might continue existing for forever12:08
fungiit's compelling. not having to deal with setuptools and its constant treadmill of compatibility changes would be pleasant12:09
mordredI think step one is making a proper build backend interface12:09
mordred++12:09
fungii guess the bigger question is whether there are projects using pbr and also relying on some setuptools features directly, and whether a fully-independent pbr build backend would make that impossible12:10
mordredalso - flit does make sdists now12:10
fungioh neat12:10
mordredthat is a good question. openstack projects shouldn't be doing that :) ... but others might12:11
mordredI kind of think we might need to make a pbr2 or something for safety12:11
mordred(or honestly call it pbr517 :) )12:11
fungisure12:11
mordredalso - if we did ditch setuptools in the backend, it would be really hard to also keep non-517 backwards compat12:12
fungigood point, so would require a fairly new pip12:12
mordredBUT ... I think if we start with a pep517 interface that's basically just the current setuptools wrapper12:13
mordredthen people could adopt that without changing anything else and it would still also be 100% backwards compat12:13
mordredthen we fork that into a new thing to work on setuptools-ectomy12:13
mordredand if it ever works - neat. if it doesn't - neat12:13
fungieither one gives people new reasons to drink12:14
mordredyou weren't running out of those were you?12:14
funginot in openstack! ;)12:14
mordredfungi: oh. OH - this is actually going to be both very easy and very nice12:21
fungii don't suppose you've found a way to avoid the need for pyproject.toml files12:35
*** jpena|lunch is now known as jpena12:36
mordrednope13:01
mordredbut - I believe I've given up fighting that one. it's super lame - but short of quitting python completely, I think there's nothing to be done about it13:02
mordredand rust (where I'd go if I didn't do python) uses toml files too - so ridiculous that it is to me that it exists, I believe continuing to try to fight it is only providing myself with angst and no value13:03
avass[m]mordred: I don't really understand why there's so much hate against yaml and why people like toml so much13:04
avass[m]the best argument I've seen is that "yes/no" can produce weird behaviour and I agree with that, but I don't think that makes the entire language bad13:04
mordredthe reason tom wrote toml is "the yaml spec is too big and I don't want to read it"13:05
mordredlike - that's actually a published reason13:05
avass[m]I feel like that just leads to xkcd 92713:06
*** sboyron_ is now known as sboyron13:07
fungiespecially if you follow the ensuing explosion of the toml spec to reach v113:07
fungitime for someone to write yet another serialization language (yasl) because they couldn't be bothered to read the toml spec13:07
avass[m]or USL ( universal serial language :)13:08
fungii like that one. soon to be followed by usl2 because usl wasn't universal enough13:08
*** marios|ruck is now known as marios|ruck|call13:19
*** marios|ruck|call is now known as marios|ruck13:49
opendevreviewAnanya Banerjee proposed opendev/elastic-recheck master: Run elastic-recheck container  https://review.opendev.org/c/opendev/elastic-recheck/+/72962313:51
zbravass[m]: every time i see/read toml I do raise a brow, i hate how it was introduced to python but at the same time I cannot fight it, i accepted defeat on that area.13:53
fungi#status notice Our Zuul gating CI/CD services are being taken offline now in order to apply some critical security updates, and are not expected to remain offline for more than 30 minutes.13:55
opendevstatusfungi: sending notice13:55
fungisnapshotting pipelines now13:55
-opendevstatus- NOTICE: Our Zuul gating CI/CD services are being taken offline now in order to apply some critical security updates, and are not expected to remain offline for more than 30 minutes.13:55
fungii've downed the zuul-scheduler container on zuul.opendev.org now13:56
zbrclarkb: my folks old me that you suggested a more reliable way to load the constraints, from local disk instead of URL, do you have an example? They only made comment w/o details, so now i need to backtrack it.13:57
fungizbr: clarkb isn't around today, can you elaborate? happy to help if i know more what you're looking for13:58
opendevstatusfungi: finished sending notice13:58
zbrhttps://99e02e92a26472cf4bfd-76db863cb86d059bc445c2f80e5d4947.ssl.cf5.rackcdn.com/772571/26/check/tripleo-ci-centos-8-containers-multinode-ussuri/4503771/job-output.txt13:58
zbrpip._vendor.requests.exceptions.ConnectionError: HTTPSConnectionPool(host='opendev.org', port=443): Max retries exceeded with 13:59
fungizbr: https://opendev.org/openstack/nova/src/branch/master/tox.ini#L2714:01
fungiuse something like that and then set $TOX_CONSTRAINTS_FILE to the local path for the requirements project checked out on the job node as a required-projects entry14:01
fungithat way you get the local copy in ci or if someone wants to override it in their dev env to speed things up, but still fall back on fetching over the internet if not14:02
zbrokey, so my guess was right, i only need to investigate why that particular job was not using the optimized path14:02
zbrdid anyone considered using `PIP_CONSTRAINT` instead of `TOX_CONSTRAINTS_FILE` when this was initially implemented?14:03
zbrbecause defining PIP_CONSTRAINT does make pip respect it everywhere, regardless if is in tox or not.14:03
fungii have no idea, but suspect that envvar may not have been implemented in pip at the time14:03
zbrin fact envvars were implemented in tox for a very long time, but not documented well even today.14:04
jrosseri had a fairly big adventure with using the local constraints file and you might be able to take some of this https://github.com/openstack/openstack-ansible-repo_server/blob/master/tasks/repo_install_constraints.yml14:04
zbrevery pip option has an envvar, but you will not find a doc page with them :D14:04
zbrjrosser: thanks! i guessed it may be bit of an adventure due to extra layers14:05
jrosseryeah, making it sensible inside/outside CI was tricky14:05
zbrmy guess is outside ci, it should just use URL14:06
jrosserthat relies on having a url to the UC repo, which in CI is rewritten elsewhere to be file://<locally cached repo>14:06
zbrunless someone really defines that var14:06
fungionce image uploads are confirmed complete in #zuul i'm planning to run this as root on bridge:14:08
fungiansible-playbook -f 20 -v /home/zuul/src/opendev.org/opendev/system-config/playbooks/zuul_pull.yaml14:08
fungiinfra-root: ^14:08
corvusfungi: ++14:08
fungipulling images now14:30
fungiokay, new images pulled successfully on all zuul servers14:32
fungiinfra-root: i'm planning to run this as root on bridge next:14:33
fungiansible-playbook -f20 /home/zuul/src/opendev.org/opendev/system-config/playbooks/zuul_restart.yaml14:33
fungidoes that look right?14:33
corvusfungi: zuul_start i think14:33
fungiwell, i only stopped the scheduler. i can stop all the other services too i suppose14:33
corvusfungi: oh yes please stop everything14:34
fungidoing the zuul_stop playbook now in that case14:34
corvusmost of the changes are actually in the executor14:34
fungisure,li just figured they couldn't be exploited as long as the scheduler was offline, but still expected to restart everything14:35
fungiokay, stop playbook completed. do i need to wait before applying the zuul_start playbook?14:35
fungispot checks of the executors show they terminated already14:36
fungiso i'll start everything now14:36
opendevreviewJames E. Blair proposed zuul/zuul-jobs master: Prevent leaks of buildset registry credentials  https://review.opendev.org/c/zuul/zuul-jobs/+/79790914:36
opendevreviewJames E. Blair proposed opendev/base-jobs master: Update promote/publish secrets and jobs  https://review.opendev.org/c/opendev/base-jobs/+/79791014:37
fungionce the cat jobs clear, i'll make sure those ^ job fixes are queued before i reenqueue the saved pipeline snapshot14:41
fungialmost there looks line14:43
fungii don't see either queued, so i'll approve them now14:44
opendevreviewgnuoy proposed openstack/project-config master: Add Ceph Dashboard charm to OpenStack charms  https://review.opendev.org/c/openstack/project-config/+/79791114:53
opendevreviewMerged opendev/base-jobs master: Update promote/publish secrets and jobs  https://review.opendev.org/c/opendev/base-jobs/+/79791014:55
*** diablo_rojo__ is now known as diablo_rojo14:57
fungicorvus: you mentioned needing a secrets update similar to ^ in openstack/project-config... do you have a handle on which jobs need updating? if not i'll start trying to work them out15:01
fungipresumably shouldn't reenqueue the saved snapshot until we do15:01
corvusfungi: probably anything that publishes to afs15:10
fungiokay, i'll see if i can replicate what you did in 79791015:10
corvusfungi: these secrets: afsdocssecret-tox-docs afsdocssecret-tox-docs-direct afsdocssecret-tox-docs-infra afsdocssecret-deploy-guide afsdocssecret-tox-docs-special afsdocssecret-tox-docs-site afsdocssecret-releasenotes afsdocssecret-stx-apiref afsdocssecret-stx-tox-docs afsdocssecret-stx-tox-docs-site are all affected15:13
fungii find three matches for `git grep '{{ afs\.'` one of which is in a comment15:13
fungione each in playbooks/publish/install-guide.yaml and playbooks/publish/openstack-afs.yaml15:13
corvusfungi: the issue is in the secrets15:15
fungibut 797910 seems to update how they're being referenced in those sorts of jinja expansion15:15
fungianyway, it looks like we need to pick some associative array subkeys to move the values into within the secrets15:16
fungicorvus: looks like matrix might have eaten the underscores in your earlier message, assuming you meant e.g. afsdocs_secret-tox-docs rather than afsdocssecret-tox-docs15:18
corvusfungi: yep i'll resend15:18
corvusfungi: these secrets: afsdocs_secret-tox-docs afsdocs_secret-tox-docs-direct afsdocs_secret-tox-docs-infra afsdocs_secret-deploy-guide afsdocs_secret-tox-docs-special afsdocs_secret-tox-docs-site afsdocs_secret-releasenotes afsdocs_secret-stx-apiref afsdocs_secret-stx-tox-docs afsdocs_secret-stx-tox-docs-site are all affected15:18
fungithanks15:18
corvusfungi: the secrets and playbooks both need adjusting; you may be able to find the playbooks by grepping, but also should be able to find them by starting with the secrets and identifying which playbooks use them15:20
opendevreviewTristan Cacqueray proposed opendev/base-jobs master: submit-logstash-jobs: fix the new location of the zuul log_url  https://review.opendev.org/c/opendev/base-jobs/+/79796015:24
fungicorvus: thanks, i've worked through fixing afsdocs_secret-tox-docs from the example in opendev-zuul-docs and think i have a pretty good handle on this, will just take some time to apply similar transformations to the others and then ferret out all the uses in playbooks15:29
opendevreviewMerged opendev/base-jobs master: submit-logstash-jobs: fix the new location of the zuul log_url  https://review.opendev.org/c/opendev/base-jobs/+/79796015:30
opendevreviewJames E. Blair proposed zuul/zuul-jobs master: Prevent leaks of buildset registry credentials  https://review.opendev.org/c/zuul/zuul-jobs/+/79790915:31
*** ysandeep is now known as ysandeep|out15:36
opendevreviewJames E. Blair proposed zuul/zuul-jobs master: Prevent leaks of buildset registry credentials  https://review.opendev.org/c/zuul/zuul-jobs/+/79790915:40
fungicorvus: i'm a little lost on afsdocs_secret-tox-docs-special and afsdocs_secret-tox-docs-site, are the vars for those going to need to be set as facts?15:45
fungithey're not referencing zuul namespaced vars15:46
fungii've got the secrets retooled, working on finding uses of them now15:47
corvusfungi: looks like they're set in job vars; so you'll need to add "specialpublishdirectory" as a kwarg to the format function in the playbook (but it may not always exist if it's the same playbooks used by the other jobs, so that may need a '.get()' call too)15:49
corvuslemme see if i can come up with something15:50
corvuswow that's amazing, no special handling is needed even if the variable doesn't exist15:51
corvusfungi: so you should just be able to do .format(zuul=zuul, special_publish_directory=special_publish_directory) in those playbooks15:52
fungiokay, thanks!15:53
fungialso as luck would have it, most of the secrets seem to be passed to opendev-promote-docs-base as a parent15:53
opendevreviewTobias Henkel proposed zuul/zuul-jobs master: Fix reading buildset_registry from results.json  https://review.opendev.org/c/zuul/zuul-jobs/+/79796315:53
fungiwhich should already be addressed in 79791015:54
opendevreviewTobias Henkel proposed zuul/zuul-jobs master: Fix reading buildset_registry from results.json  https://review.opendev.org/c/zuul/zuul-jobs/+/79796315:54
*** rpittau is now known as rpittau|afk16:09
fungicorvus: trying to unwind your .format() suggestion, i've managed to get lost, sorry... that var is being subbed in a secret which is then passed to a parent which doesn't explicitly reference special_publish_directory, specifically playbooks/docs/promote.yaml in opendev/base-jobs, do i add the .format() at the end of the target_dir definitions in that playbook?16:10
fungii guess adding those variable names to the existing .format(zuul=zuul) there?16:10
opendevreviewJeremy Stanley proposed openstack/project-config master: Update promote/publish secrets and jobs  https://review.opendev.org/c/openstack/project-config/+/79797116:13
fungiinfra-root: config-core: that's ^ my first try at the project-config fixes16:13
opendevreviewJeremy Stanley proposed openstack/project-config master: Update promote/publish secrets and jobs  https://review.opendev.org/c/openstack/project-config/+/79797116:22
opendevreviewAnanya Banerjee proposed opendev/elastic-recheck master: Run elastic-recheck container  https://review.opendev.org/c/opendev/elastic-recheck/+/72962316:22
opendevreviewAlbin Vass proposed zuul/zuul-jobs master: Add _zuul var that can be overriden when including role  https://review.opendev.org/c/zuul/zuul-jobs/+/79797716:25
opendevreviewJames E. Blair proposed zuul/zuul-jobs master: Prevent leaks of buildset registry credentials  https://review.opendev.org/c/zuul/zuul-jobs/+/79790916:26
*** jpena is now known as jpena|lunch16:30
*** jpena|lunch is now known as jpena16:30
corvusfungi: that looks good for the secrets; it'll need some playbook updates too16:30
fungicorvus: the playbooks seemed to be from parents in opendev/base-jobs16:30
fungiwhich ones did i overlook?16:30
*** jpena is now known as jpena|off16:31
corvusfungi: oh neat16:31
corvusthen nevermind16:31
fungiwell, i mean i won't guarantee that i didn't miss some, but i thought i checked that they were all parented to the promote job in base-jobs which was already updated to use that pattern16:32
fungicorvus: except for the aforementioned special_publish_directory and publish_site vars which are similarly being passed to the same parent, hence my request for clarification on the .format() suggestion16:33
fungibut if i interpreted your suggestion correctly, i'll need to patch that into base-jobs anyway16:34
corvusfungi: oh sorry, i missed that...but yes, i think that's the thing to do16:34
fungithanks, change on the way for that as well16:35
corvusfungi: it's important to make sure that a secret that includes special_publish_directory in a template var isn't used in a job that runs in a pre-review pipeline, and that we trust the people who approve changes for the projects where it runs.16:36
corvus(i don't think this is a change in behavior from before though, so presumably whoever set that up originally made that determination)16:37
fungiyeah, it can't be used outside jobs in openstack/project-config in that case, right?16:37
fungier, used by jobs defined outside16:37
opendevreviewJeremy Stanley proposed opendev/base-jobs master: Allow publish_site and special_publish_directory  https://review.opendev.org/c/opendev/base-jobs/+/79798016:44
fungicorvus: ^ like that then?16:44
opendevreviewJames E. Blair proposed zuul/zuul-jobs master: Prevent leaks of buildset registry credentials  https://review.opendev.org/c/zuul/zuul-jobs/+/79790916:48
corvusfungi: lgtm16:49
fungithanks16:49
opendevreviewMerged openstack/project-config master: Update promote/publish secrets and jobs  https://review.opendev.org/c/openstack/project-config/+/79797116:56
opendevreviewJames E. Blair proposed zuul/zuul-jobs master: Prevent leaks of buildset registry credentials  https://review.opendev.org/c/zuul/zuul-jobs/+/79790916:56
opendevreviewJames E. Blair proposed zuul/zuul-jobs master: Re-add buildset-registry jobs  https://review.opendev.org/c/zuul/zuul-jobs/+/79798616:57
opendevreviewJeremy Stanley proposed opendev/system-config master: Stop updating Gerrit RDBMS for repo renames  https://review.opendev.org/c/opendev/system-config/+/79799017:03
opendevreviewMerged opendev/base-jobs master: Allow publish_site and special_publish_directory  https://review.opendev.org/c/opendev/base-jobs/+/79798017:08
fungiinfra-root: now that 797971 and 797980 have merged, i'll reenqueue the saved pipeline snapshot from prior to the service restart17:09
fungireenqueuing is now underway17:12
fungiand now it's complete17:21
opendevreviewMerged zuul/zuul-jobs master: Prevent leaks of buildset registry credentials  https://review.opendev.org/c/zuul/zuul-jobs/+/79790917:23
fungii guess this needs fixing for new zuul as well: https://zuul.opendev.org/t/openstack/build/f37fbb11e7284dc18fc54921d78dc044/console#1/0/5/localhost17:24
fungii think i see where the secret needs updating in project-config, though there will need to be a corresponding change in base-jobs i think17:30
corvusfungi: this looks like the same turing-complete-secret pattern, so probably the format() fix again17:31
fungiyeah17:32
fungion the base-jobs side17:32
opendevreviewJeremy Stanley proposed openstack/project-config master: Do var subst in openstack-github-mirroring secret  https://review.opendev.org/c/openstack/project-config/+/79799217:33
fungithat's the project-config half17:33
opendevreviewJeremy Stanley proposed opendev/base-jobs master: Use python string formatting for upload-git-mirror  https://review.opendev.org/c/opendev/base-jobs/+/79799317:38
fungiand the base-jobs half ^17:38
fungicorvus: when you get a moment, please lmk if that pair of changes looks right17:42
corvuslgtm17:42
fungihah, thanks!17:42
corvusfungi: i +2d; probably makes sense for you to +w17:43
fungiyep, i'll be keeping an eye on it after it runs again17:43
opendevreviewJames E. Blair proposed zuul/zuul-jobs master: Fix default value for zuul_artifacts  https://review.opendev.org/c/zuul/zuul-jobs/+/79800017:51
opendevreviewMerged opendev/base-jobs master: Use python string formatting for upload-git-mirror  https://review.opendev.org/c/opendev/base-jobs/+/79799317:51
fungimordred: back on the pbr517 topic, you may also may want to review in progress peps 660 and 662 about handling editable installs18:06
fungithough if pbr becomes a setuptools wrapper that's probably not terribly urgent until we try to drop setuptools18:06
opendevreviewMerged zuul/zuul-jobs master: Fix default value for zuul_artifacts  https://review.opendev.org/c/zuul/zuul-jobs/+/79800018:14
opendevreviewMerged openstack/project-config master: Do var subst in openstack-github-mirroring secret  https://review.opendev.org/c/openstack/project-config/+/79799218:18
fungihopefully any github mirror jobs started after 18:18 should succeed now18:20
fungiopenstack-upload-github-mirror seems to be passing as of the builds which completed for a couple of projects at 18:2618:42
opendevreviewJames E. Blair proposed opendev/system-config master: Update Zuul job semaphore usage  https://review.opendev.org/c/opendev/system-config/+/79802020:21
opendevreviewJames E. Blair proposed openstack/project-config master: Update Zuul job semaphore usage  https://review.opendev.org/c/openstack/project-config/+/79802120:22
*** dviroel is now known as dviroel|afk20:25
*** dviroel|afk is now known as dviroel20:54
opendevreviewMerged zuul/zuul-jobs master: Re-add buildset-registry jobs  https://review.opendev.org/c/zuul/zuul-jobs/+/79798621:28
*** dviroel is now known as dviroel|out21:29
mordredfungi: neat (re 660/662) - seem reasonable for once we have overthrown our setuptools overlords- but I agree, not urgent21:31
ianwo/ thanks corvus/fungi for dealing with the security rollout21:39
fungiianw: you get to hit all the things we missed ;)21:42
ianwfungi: do you have any top-of-head thoughts on why the bullseye wheel job takes hours and times out?  https://zuul.opendev.org/t/openstack/build/cd4503d0ca8f49cba83958f771f229e0/logs23:00
fungiianw: gut instinct is that almost no projects on pypi publish wheels for py3923:01
fungido we build py39 wheels for any other platforms (recent fedora maybe)?23:02
ianwahh, is 3.9 default or installable?  we don't build fedora wheel.  23:03
fungidefault23:03
ianwok, we might have to do like the arm64 build and trim to build only the latest two releases23:04
fungiit could either be that we end up building lots of extra pure python wheels specifically for py39, when abi3 would do, or that the lack of so many wheels on pypi for it is hamstringing pip's dep solver23:04
ianwthis is wrt to https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/797808/ ... i'm not sure we've been testing it 23:04
fungibut sure, i also highly doubt year+ old stable branches of openstack are going to want to run jobs on bullseye23:05
opendevreviewIan Wienand proposed openstack/project-config master: Add python-path to Debian bullseye ARM64 images  https://review.opendev.org/c/openstack/project-config/+/79802923:52

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