16:00:17 <jednorozec> #startmeeting RELENG (2022-01-25)
16:00:17 <zodbot> Meeting started Tue Jan 25 16:00:17 2022 UTC.
16:00:17 <zodbot> This meeting is logged and archived in a public location.
16:00:17 <zodbot> The chair is jednorozec. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
16:00:17 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:00:17 <zodbot> The meeting name has been set to 'releng_(2022-01-25)'
16:00:17 <jednorozec> #meetingname releng
16:00:17 <jednorozec> #chair nirik sharkcz pbrobinson pingou pmoura mboddu dustymabe ksinny jednorozec
16:00:17 <jednorozec> #topic init process
16:00:17 <zodbot> The meeting name has been set to 'releng'
16:00:17 <zodbot> Current chairs: dustymabe jednorozec ksinny mboddu nirik pbrobinson pingou pmoura sharkcz
16:00:59 <nirik> morning
16:01:02 * mboddu is here but also in other meeting
16:06:17 <jednorozec> so first thing sfirst
16:06:21 <jednorozec> .releng 10538
16:06:22 <zodbot> jednorozec: Issue #10538: Fedora 36 Mass Rebuild - releng - Pagure.io - https://pagure.io/releng/issue/10538
16:06:39 <jednorozec> mass rebuild of packages and modules is done
16:07:10 <nirik> awesome. So did you all have a chance to read up on the devel list?
16:07:15 <jednorozec> yup
16:07:27 <jednorozec> so are we resubmitting tasks on thursday?
16:08:04 <nirik> yeah, that was the plan. I haven't read up today yet tho.
16:08:12 <nirik> can we id the ones that just failed on ppc64le?
16:08:17 <jednorozec> oh I red it in the morning
16:08:23 <jednorozec> let me check again
16:09:20 <jednorozec> I seee nothing new there
16:10:03 <nirik> well, the thought was to resubmit the ppc64le failures after gcc-12.0.1-0.3.fc36 finishes...
16:10:20 <nirik> (since it has at least 2 fixes for ppc64le failures that were thought to be somewhat widespread)
16:11:53 <nirik> but I'm not sure how widespread they are really.... ;)
16:12:15 <jednorozec> well
16:12:22 <nirik> we could just do another resbumit/merge
16:12:41 <jednorozec> wel will see, I can check for ppc64le fails
16:13:41 <jednorozec> and write comment in the tracking ticket
16:14:20 <nirik> yeah, we should keep people posted on whats going on.
16:14:45 <nirik> perhaps another devel announce post saying the main part is done and we are going to do one more round after gcc.
16:15:33 <nirik> I'm happy to, or you're welcome to... :)
16:16:12 <jednorozec> well I dont mind, but you already announced this mass rebuild
16:16:35 <jednorozec> so its probably good idea to do this as well
16:17:27 <nirik> sure, can do.
16:17:36 <jednorozec> thanks
16:18:43 <jednorozec> moving on
16:18:54 <jednorozec> .releng 10555
16:18:55 <zodbot> jednorozec: Issue #10555: Decommission epel8-playground in koji and bodhi - releng - Pagure.io - https://pagure.io/releng/issue/10555
16:19:34 <jednorozec> so what exactly is needed for this?
16:19:53 <jednorozec> remove koji stuff, remove -playground from bodhi
16:20:01 <jednorozec> and update ansible?
16:22:07 <nirik> well, not sure it needs to remove from bodhi...
16:22:17 <nirik> it doesn't use bodhi I don't think
16:22:32 <jednorozec> aha no it does not
16:22:33 <nirik> and yeah, the cron job that does the compose... perhaps signing config.
16:23:34 <jednorozec> so remove koji stuff and cleanup ansible. phsmoura we can do this together if you want.
16:24:31 <jednorozec> moving onto next ticket
16:24:37 <jednorozec> .releng 10546
16:24:38 <zodbot> jednorozec: Issue #10546: ejected builds in epel9-stable push - releng - Pagure.io - https://pagure.io/releng/issue/10546
16:25:02 <jednorozec> so we can close this, question is why was this happening.
16:25:12 <nirik> yeah, that I am not sure about... ;(
16:25:31 <nirik> It was a compose(s) that got into a weird state. I dunno if it was a network thing or what
16:25:58 <jednorozec> hm
16:26:38 <jednorozec> talking updates this isk interesting
16:26:39 <jednorozec> https://bodhi.fedoraproject.org/updates/FEDORA-2022-ccd3d5cdb9
16:26:47 <jednorozec> update from sidetag that fwas deleted
16:26:59 <jednorozec> in a weird state
16:28:06 <nirik> it hit the 30day limit
16:28:35 <nirik> we delete side tags over 30days.
16:28:46 <nirik> "oscar" is the koji-gc user. ;)
16:28:58 <jednorozec> oh!
16:29:31 <jednorozec> so upstream bodhi should implement garbage collection for such updates
16:30:11 <nirik> that would be nice yeah... not sure how it would work exactly tho.
16:30:35 <nirik> I guess if the sidetag wasn't there anymore, revoke the update?
16:30:56 <jednorozec> well now it can say that the update was from side-tag, it has the build it queries koji the build are not in that side tag. Delete the update
16:31:13 <nirik> well, we don't delete updates, but sure... revoke it.
16:31:19 <jednorozec> yeah
16:32:12 <jednorozec> I will put that into upstream ticket.
16:32:31 <jednorozec> so can we close 10546
16:32:46 <jednorozec> ?
16:34:11 <nirik> yeah, I think so. +1
16:36:45 <jednorozec> so how this happened?
16:36:47 <jednorozec> .releng 10564
16:36:48 <zodbot> jednorozec: Issue #10564: BuildError: package perl-Test-Name-FromLine not in list for tag epel9-testing-candidate - releng - Pagure.io - https://pagure.io/releng/issue/10564
16:37:07 <jednorozec> they requested epel9 branch the branch was created normally.
16:37:38 <nirik> likely they built it too quickly before the job could add it to koji?
16:38:16 <jednorozec> well that was my initial idea but the was a day delay between the request approval and build
16:39:02 <jednorozec> I can see the package in epe9 tag now
16:39:11 <nirik> yep.
16:39:27 <jednorozec> so I will ask them to rebuild and close if ok.
16:39:27 <nirik> Thu Jan 20 02:52:02 2022 perl-Test-Name-FromLine-0.13-22.fc36 tagged into f36-updates-candidate by eseyman
16:39:28 <nirik> Fri Jan 21 06:14:12 2022 package list entry created: perl-Test-Name-FromLine in epel9 by bodhi [still active]
16:39:43 <nirik> so it didn't add it until fri morning.
16:40:10 <nirik> sorry, didn't mean to paste the first line there. ;)
16:40:42 <nirik> but the failed build was 20UTC thursday night.
16:40:51 <nirik> I am not sure why it was so slow there.
16:41:02 <jednorozec> hm
16:42:07 <nirik> might have been mass rebuild commits? it was processing them all and got behind?
16:42:24 <jednorozec> oooo
16:42:26 <jednorozec> yes
16:42:33 <jednorozec> that would explain it
16:43:56 <nirik> I guess the mass rebuild tagging is still ongoing? you taged into signing pending so it's going thru signing again?
16:44:21 <jednorozec> hmm SOP sais f**-pending
16:45:32 <nirik> yeah... but perhaps next time we should go direct. This is gonna take a while. ;) No biggie tho...
16:45:42 <jednorozec> yeah
16:45:48 <jednorozec> so I can update the SOP
16:45:55 <jednorozec> directly to f36?
16:46:07 <jednorozec> or relevant tag for release...
16:46:54 <nirik> yeap
16:47:04 <nirik> https://admin.fedoraproject.org/collectd/bin/graph.cgi?hostname=rabbitmq_slash_pubsub;plugin=queues;plugin_instance=robosignatory;type=messages;begin=-43200
16:48:06 <jednorozec> let me update the SOP right now
16:48:10 <jednorozec> meanwhile
16:48:21 <jednorozec> #topic Open Floor
16:50:34 <nirik> nothing in particular from me today.
16:51:36 <jednorozec> the SOP is updated
16:53:15 <nirik> jednorozec++
16:53:40 <jednorozec> If there is nothing more to discuss I will give you back 5minutes of your day
16:55:22 <jednorozec> #endmeeting