19:00:00 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 19:00:00 Meeting started Thu Jan 21 19:00:00 2021 UTC. 19:00:00 This meeting is logged and archived in a public location. 19:00:00 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:00 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:00:00 #chair mboddu nirik smooge pingou mobrien 19:00:00 #meetingname fedora_infrastructure_ops_daily_standup_meeting 19:00:00 #info meeting is 30 minutes MAX. At the end of 30, its stops 19:00:00 Current chairs: mboddu mobrien nirik pingou smooge 19:00:00 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:00:01 #info agenda is at https://board.net/p/fedora-infra-daily 19:00:03 #topic Tickets needing review 19:00:05 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 19:01:05 hello 19:01:17 .ticket 9594 19:01:18 nirik: Issue #9594: Fedpkg container-build: The node was low on resource: ephemeral-storage - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9594 19:01:54 med/med/ops? and perhaps mention mobrien and Saffronique since they last worked on osbs? 19:02:36 one seq 19:02:36 smooge: you want to mod tickets? 19:02:45 * mboddu is here 19:02:46 mboddu: you around for releng tickets? 19:02:51 Yes, I am 19:02:57 I was in a meeting but now I am back 19:03:39 ok done 19:05:03 so, thats it for infra 19:05:06 any releng ones? 19:05:17 I have a couple 19:05:24 Or one 19:05:29 .releng 19:05:29 mboddu: (releng ) -- Alias for "showticket https://pagure.io/releng/issue/%s $1". 19:05:34 .releng 9955 19:05:36 mboddu: Issue #9955: Git hook checking availability of sources in look-a-side cache - releng - Pagure.io - https://pagure.io/releng/issue/9955 19:05:56 Looks, high, high, ops+dev? 19:06:12 Or maybe file it against pagure-dist-git and close this? 19:06:32 I'm not sure how this could easily work. ;( 19:06:57 Hence the high trouble part, I dont have any idea either 19:06:57 i know pdc 19:07:04 it seems like it would have to be pretty complex... 19:08:02 I'm sure it's high trouble... might be low or med gain tho? 19:08:56 i have marked it high/med/dev/ops 19:09:17 That works, thanks smooge 19:09:39 of course I could make it high/high/med/med/ops/dev 19:09:48 but thats just crazy talk 19:10:08 my irc client seems to have a studder. ;) 19:10:13 anyhow, anymore? 19:10:48 that looks like it 19:10:56 Nope, thats all I got 19:11:05 Oh, I have an update 19:11:12 On mass rebuild 19:11:18 first back list one is 9821 19:11:25 ah ok 19:12:04 So, compiler team is thinking of not including binutils 2.36 for the mass rebuild (still debating), if that is the case, I might start the mass rebuild today or tomorrow 19:12:07 I'm trying to stablize the armv7 builders. 19:12:27 Yes, which is what I wanted to check with you ^ 19:12:35 nirik: How's arm looking? 19:12:43 I'd prefer to make sure those are happy before we start mass rebuild... but I know it may be hard to fix. 19:12:58 wlel, I lowered memory and am doing a test build 19:15:00 if that doesn't do it, not sure... will have to think up more ideas I guess. 19:15:04 nirik: Okay, just now they confirmed that they dont want to include binutils 2.36 for f34 19:15:39 ok, then will let you know when 32bit arm is ready 19:15:53 Lets wait and see for arm stuff 19:16:14 nirik: Also, you asked a question on releng about boost and tagging it to rebuild tag 19:16:32 yeah 19:16:49 I didn't get "On the minus side it means we will need to regen it to pick up any changes in rawhide that land during the mass rebuild..." 19:16:54 [10:42:17] mboddu: I wonder... what would you think of making the rebuild a normal sidetag, but telling kojira to not to do newrepos for it. This would allow us to tag say boost into it and regen the repo and not mess up rawhide while the mass rebuild is going. On the minus side it means we will need to regen it to pick up any changes in rawhide that land during the mass rebuild... 19:17:32 so, as you would do it now, it inherits from f34-build... so when someone builds something in rawhide, kojira does a newrepo and it's in the build root... 19:17:56 so if someone builds something in the middle of the mass rebuild in rawhide it appears in the buildroot. 19:18:16 Right 19:18:32 Which was always the case 19:18:34 if we do this, the buildroot is seperate... so it would only update if we manually tell it to. 19:20:41 we don't have to decide now, just when we make the side tag. ;) 19:21:58 Yeah, I am thinking whether its really useful or not 19:22:03 Just weighing in the options 19:22:20 well, the plus side is that boost won't break things for N days until we tag in the mass rebuild. 19:22:30 but it might not be worth the trouble, I am not sure what breaks 19:22:39 Right 19:22:55 and we might wait for monday anyhow, since we asked fesco already and people are expecting it. 19:22:56 I dont think its worth the trouble 19:23:25 Should we wait or if we figure out the arm 32 bit issue, should we go ahead? 19:24:09 lets just consider and take it one thing at a time... once we solve the 32bit arm thing, we can look then... 19:25:10 nirik: ack 19:27:16 so, anything else to discuss? or should we close out? 19:28:26 Thats all I got 19:29:31 ok, thanks all 19:29:32 all done 19:29:35 #endmeeting