[09:20:40] hashar: o/ if you have a moment, any suggestion about the what's failing in https://integration.wikimedia.org/ci/job/inference-services-pipeline-langid/16/console ? [09:21:30] it is probably a pebcak on my side but I don't see anything clear, except something in plib-run-wo2rbpqr [09:21:38] ROOT: HandledError| could not recognize config file tox.ini [09:22:29] so well hmm no clue :/ [09:22:58] maybe try to send a dummy patch and check whether that is working [09:24:34] ack thanks! [09:24:51] if the dummy patch fails, there is something off in the infra somewhere (maybe blubber / pipelinelib) [09:25:23] do we know what the plib-run-wo2rbpqr does? [09:26:05] that is the generated image [09:26:43] the commands used to create it are above in the output [09:27:15] #18 68.74 Collecting tox (from -r requirements-test.txt (line 2)) [09:27:15] #18 68.74 Using cached tox-4.6.3-py3-none-any.whl (152 kB) [09:27:16] ahhh okok [09:27:30] so it is missing the tox.ini file [09:28:57] ah yeah from the code review: The tox.ini was missing from the image. I just added it. [09:29:00] then it is not in the patch [09:29:05] (but maybe it is already in the repo) [09:29:09] or has to be COPY into the image [09:32:49] it is yes we have a main one that we share among all images [09:33:53] maybe that can be reproduced locally `docker buildx` shouldl be able to build the image if the .pipeline/blubber.yaml has `# syntax: docker-registry.....` . But I can't find the doc :\ [09:34:49] I think that Ilias in my team has an idea, the missing bit for me was to understand what the plib-etc.. was doing [09:36:21] there are a few layers of inception for sure and I ma not familiar with all of them :-\ [09:37:01] thanks for the help! [09:37:09] elukey: there are some lead with scap https://gitlab.wikimedia.org/repos/releng/scap/-/blob/master/Makefile [09:37:31] which uses docker buildkit to craft an image after the definition in https://gitlab.wikimedia.org/repos/releng/scap/-/blob/master/.pipeline/blubber.yaml [09:37:43] which is made possible by the comment `# # syntax=docker-registry.wikimedia.org/repos/releng/blubber/buildkit:v0.16.0` [09:38:00] and that lets one have the images build locally and run the integration tests locally [09:38:03] the same way CI does [09:38:54] * elukey nods [11:23:18] claime, effie: shall we try disabling parsoid PC writes in an hour or so, before the backport window? Or should we do it during the window? [11:23:29] ...would you give a +1 on https://gerrit.wikimedia.org/r/c/operations/mediawiki-config/+/933453 ? [11:25:01] let me check if we got hit like last night :p [11:25:48] looks good [11:26:07] I think you're right, it's when there's a template edit that we get backlogged [11:27:17] I'd rather do it during the backport window or right after if you don't mind, I don't know about effie but I'll be in the middle of lunch in an hour :) [12:14:51] I was out. duesen lets do the window [12:15:03] ok. i'll add it to the calendar [12:17:18] did you add hardware to the jobrunner cluster? [13:06:28] duesen: Not yet, but we should be fine [15:28:51] hello on-call friends. i need to run a quick batphone test to test/dry-run our escalation settings for the holiday. PLMK when a good time would be. I would be removing americas from the rotation and escalating test via klaxon. [15:30:40] denisse mutante after the test i would enable it back. just want to test that it goes to batphone basically [15:31:41] lmata: No blockers from my side. :) [15:34:08] hello SRE friends i'm running a quick batphone test via klaxon in prep for next week. please disregard [15:40:35] moritzm: if around, [15:40:35] pbuilder-satisfydepends-dummy : Depends: architecture-is-64-bit which is a virtual package and is not provided by any available package [15:40:53] I can simply update the architecture explicitly but since this is more cleaner, how do I resolve this? [15:41:24] (moritz.m or if someone else has run into this when building a deb) [15:41:45] fwiw, backporting a sid build to bullseye (not that it should matter here?) [15:45:23] that's a new package, only in bookworm: https://tracker.debian.org/pkg/architecture-properties [15:45:41] you can simply drop it from build deps for a backport since we only use amd64 anyway [15:46:15] yeah [15:46:36] I was like maybe I will stick to this though so that it's easier to keep sync with upstream debian changes, but this is simpler one [15:46:42] thanks [23:04:48] nothing to report from on-call