Tuesday, 2022-10-04

*** rlandy|bbl is now known as rlandy|out01:51
*** pojadhav|sick is now known as pojadhav04:16
*** soniya29|ruck is now known as soniya29|ruck|afk04:32
*** ysandeep|out is now known as ysandeep04:37
*** raukadah is now known as chandankumar04:48
*** marios is now known as marios|ruck05:14
*** jpena|off is now known as jpena07:20
*** ysandeep is now known as ysandeep|lunch08:08
*** soniya29|ruck|afk is now known as soniya29|ruck08:21
*** marios|ruck is now known as marios08:26
*** ramishra_ is now known as ramishra09:38
*** ysandeep|lunch is now known as ysandeep10:18
*** rlandy|out is now known as rlandy10:39
*** dviroel|afk is now known as dviroel11:30
*** ravlew is now known as Guest225611:38
*** ravlew5 is now known as ravlew11:52
*** frenzyfriday is now known as frenzyfriday|food12:22
*** dasm|off is now known as dasm13:49
*** ysandeep is now known as ysandeep|out14:04
*** dviroel is now known as dviroel|lunch14:50
fungisome strange bitrot in bindep's docs job: https://zuul.opendev.org/t/opendev/build/5e40df1ecaec41a7aa2b12f6dd001104/log/job-output.txt#851-85314:58
*** marios is now known as marios|out15:22
clarkbfungi: I think testtools is only in test-requirements and not in the normal requirements or the docs requirements. I'm guessing some dependency was pulling it in previously but not anymore15:24
fungioh, that would definitely explain it15:25
clarkbits trying to autodoc the tests15:25
clarkbI think maybe we don't need to autodoc the tests and that should avoid the problem15:25
fungiyeah, i wonder if we should just drop autodoc entirely there15:26
fungihttps://docs.opendev.org/opendev/bindep/latest/15:26
fungii don't see where we're actually linking any autodoc-generated content15:26
clarkbya either we add test requirements to the docs builds or we drop autodoc of the tests15:26
clarkbI think both are valid fixes. I lean towards dropping autodoc of tests as I doubt anyone uses that info15:27
fungiwell, i mean drop the autodoc extension15:27
fungii don't see where we've got any toc linking it15:27
fungiscratch that, it's in the contributing chapter15:27
fungihttps://docs.opendev.org/opendev/bindep/latest/contributing.html#python-api15:28
fungiand we were previously autodoc'ing bindep.tests too15:29
fungiso yes, we can just add testtools to doc/requirements.txt i guess15:29
clarkbyes, but is there value to having a page that autodocs the tests?15:29
clarkbthat seems unnecessary15:29
fungiit's in the contributor documentation, so i can see it being relevant there, but perhaps we can also expect contributors to just read the source15:30
clarkbyes exactly15:30
clarkbautodoc to me is useful for where you have third party integrations for things like libraries15:30
clarkbthe internal unittests of an appliaction don't really need that imo15:31
clarkbbut if we keep them updating the docs requirements is also easy15:32
opendevreviewJeremy Stanley proposed opendev/bindep master: Drop unit tests autodoc from contributor docs  https://review.opendev.org/c/opendev/bindep/+/86027415:33
*** rlandy is now known as rlandy|biab15:40
opendevreviewMerged opendev/bindep master: Drop unit tests autodoc from contributor docs  https://review.opendev.org/c/opendev/bindep/+/86027416:06
opendevreviewMerged opendev/bindep master: Add support for popos  https://review.opendev.org/c/opendev/bindep/+/84344416:12
clarkbfungi: I'll bring this up in the team meeting today, but yuo'ev been poking at mm3 with me so may want to get a head start. https://review.opendev.org/c/opendev/system-config/+/860157 is a "lightweight" fork of the upstream mm3 docker images. The only change I've made between the upstream and this change is to add lynx to the image. We have the opportunity to do a heavier fork and16:17
clarkbmove some of the bind mounted workarounds in the role to the image. We can change uids and gids. We can port in the PR fix for uwsgi buffer sizes you linked to on the upstream mailing lsit and so on. I think we should probably make a decision on 1) whether or not we want to fork and 2) how fokred do we want to get :)16:17
*** jpena is now known as jpena|off16:18
fungiyes, i agree that's a good topic for the meeting16:18
clarkbI'm hoping that having a change up will help people see what is involved here. I am wary of building our own images from scratch instead of forking becuase there appears to be a lot of inside baseball knowledge for what versions of libraries and tools all fit together to make this work.16:18
fungii do feel like trying not to fork farther than we need to would leave us the ability to reintegrate upstream images if maintenance of those resumes16:19
clarkbyup exactly16:19
clarkbI guess this really comes down to "do we want to maintain our own images long term or attempt to realign with upstream if it becomes more active again"16:20
fungiit's not been lying dormant for long enough yet that i'm expecting the work is abandoned16:20
fungiand the maintainer has been semi-around in the mm3 community fairly recently16:20
clarkband if we start here we can shift to a bigger fork later with little effort16:20
clarkbgoing the other direction is potentially more problematic16:20
*** dviroel|lunch is now known as dviroel16:21
*** rlandy|biab is now known as rlandy16:22
opendevreviewJames E. Blair proposed zuul/zuul-jobs master: WIP: Add ensure-pip-localhost job  https://review.opendev.org/c/zuul/zuul-jobs/+/86029318:21
opendevreviewJames E. Blair proposed zuul/zuul-jobs master: More narrowly tailor the ensure-pip Debian workaround  https://review.opendev.org/c/zuul/zuul-jobs/+/86029418:21
opendevreviewJames E. Blair proposed zuul/zuul-jobs master: More narrowly tailor the ensure-pip Debian workaround  https://review.opendev.org/c/zuul/zuul-jobs/+/86029418:36
opendevreviewJames E. Blair proposed zuul/zuul-jobs master: Combine ensure-pip playbooks into a test role  https://review.opendev.org/c/zuul/zuul-jobs/+/86029618:46
opendevreviewMerged zuul/zuul-jobs master: More narrowly tailor the ensure-pip Debian workaround  https://review.opendev.org/c/zuul/zuul-jobs/+/86029418:52
fricklerRL9 builds are broken with some mirror issue it seems19:16
clarkb[MIRROR] systemd-udev-250-6.el9_0.1.x86_64.rpm: Interrupted by header callback: Server reports Content-Length: 107 but expected size is: 154731220:18
clarkb4168812 is the size I get back from the rackspace mirror20:20
clarkbI wonder if it will work on the next round and previous ones had half snyced mirrors or something20:20
*** rlandy is now known as rlandy|out20:26
*** dviroel_ is now known as dviroel|afk20:37
clarkbno it looks like more recent builds are still failing. Maybe something wrong with a specific mirror? cc NeilHanlon 20:55
clarkbI need to pop out for a bit but will try to look more when I return20:56
*** dasm is now known as dasm|off22:32
clarkbok I ran `dnf install -y findutils util-linux sudo python3 NetworkManager` in a docker container using rockylinux:9 and that succeeded (it installed the same set of packages too)23:03
clarkbunfortunately dnf doesn't say what it was talking to that errored just that some MIRROR errored23:05
clarkb(I wonder if this is a dnf bug)23:05
clarkbthe container image's yum.repos.d lists mirrorlist=https://mirrors.rockylinux.org/mirrorlist?arch=$basearch&repo=BaseOS-$releasever$rltype for the baseos mirror23:07
clarkbif I `curl 'https://mirrors.rockylinux.org/mirrorlist?arch=x86_64&repo=BaseOS-9'` I consistently get back the dfw mirror23:10
clarkbwhich makes sense23:10
clarkband if I wget https://dfw.mirror.rackspace.com/rocky/9.0/BaseOS/x86_64/os/Packages/s/systemd-udev-250-6.el9_0.1.x86_64.rpm I get what appears to be a full size result back. I wonder if we aren't hitting some dib cache issue now23:11
clarkblike maybe it was broken and we cached the broken23:11
clarkbhrm I'm not seeing rockylinux content in /opt/dib_cache/yum23:13
clarkbfetching 404'd content results in 196 bytes which is larger than the 107 it is complaining about23:14
clarkbheh I havne't been the only one confused by dnf's lack of logging https://unix.stackexchange.com/questions/252538/dnf-how-to-show-which-mirror-url-has-been-chosen23:16
clarkb"FYI, DNF actually does not know the URLs. It just knows the URL of the "metalink" and the file name (and some other metadata) of the package." this might be where I get of the train and go do something else23:17

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