14:01:48 #startmeeting FESCO (2020-08-26) 14:01:48 Meeting started Wed Aug 26 14:01:48 2020 UTC. 14:01:48 This meeting is logged and archived in a public location. 14:01:48 The chair is dcantrell. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:48 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:01:48 The meeting name has been set to 'fesco_(2020-08-26)' 14:01:48 #meetingname fesco 14:01:48 #chair nirik, ignatenkobrain, decathorpe, zbyszek, sgallagh, mhroncok, dcantrell, cverna, Conan_Kudo, Pharaoh_Atem, Son_Goku, King_InuYasha, Sir_Gallantmon, Eighth_Doctor 14:01:48 The meeting name has been set to 'fesco' 14:01:48 Current chairs: Conan_Kudo Eighth_Doctor King_InuYasha Pharaoh_Atem Sir_Gallantmon Son_Goku cverna dcantrell decathorpe ignatenkobrain mhroncok nirik sgallagh zbyszek 14:01:51 #topic init process 14:01:52 .hello2 14:01:52 zbyszek: zbyszek 'Zbigniew Jędrzejewski-Szmek' 14:01:56 .hello ngompa 14:01:57 King_InuYasha: ngompa 'Neal Gompa' 14:01:58 .hello2 14:01:58 .hello kevin 14:02:00 dcantrell: dcantrell 'David Cantrell' 14:02:03 nirik: kevin 'Kevin Fenzi' 14:02:34 nirik: did something happen? You didn't say "morning". 14:02:42 hello all 14:03:29 hello everyone 14:03:33 mhroncok said he' 14:03:36 d be late to the meeting 14:03:42 I count 5 here, so I guess we can proceed 14:03:45 ha. morning. :) 14:03:56 .hello2 14:03:57 sgallagh: sgallagh 'Stephen Gallagher' 14:04:04 greetings, sgallagh 14:04:15 Hello all 14:04:36 so I did some digging through the queue and put some things on the agenda that I wanted us to talk about and see if we can make a decision or not. some things seemed to have run out of energy and might just need a final discussion to close out. we will see 14:04:46 #topic #2454 Proposal: Force compiler / annobin updates to use side tags / rawhide gating 14:04:49 dcantrell: famous last words 14:04:51 .fesco 2454 14:04:52 dcantrell: Issue #2454: Proposal: Force compiler / annobin updates to use side tags / rawhide gating - fesco - Pagure.io - https://pagure.io/fesco/issue/2454 14:05:50 My understanding is that pretty much everyone is for this, except the gcc maintainers who are somewhat reluctant. 14:06:29 yep 14:06:33 that's my understanding 14:06:37 King_InuYasha: what if we downgraded "MUST" to "SHOULD"? 14:06:41 no 14:06:50 well, there's been no comment from them the last 2 weeks... 14:06:52 If it breaks, we can tell the people "told you so" 14:07:22 what do we do in that scenario beyond "told ya"? 14:07:29 I think maintainers would be more open to this if the process was easier for them 14:07:31 zbyszek: a SHOULD in a policy is equivalent to not writing that policy. 14:07:32 because right now, I don't see what that would change 14:07:40 I think this feels like a lot of work on their end 14:07:56 which might explain the reluctance 14:08:17 yeah. 14:08:28 for the record, I think this is a good idea 14:08:29 perhaps someone would be willing to write/test the gating tests? 14:08:52 hey, sorry for being late o/ 14:08:55 nirik: https://src.fedoraproject.org/rpms/gcc/pull-request/11 14:09:24 bookwar took the tests I wrote for CentOS and ported it to Fedor 14:09:28 *Fedora 14:10:33 What is the current status with sidetags: how much slower would a build of gcc in sidetag be than straight in koji for rawhide? 14:10:53 Why should it be any slower? It's the same builders, isn't it? 14:11:08 There's some overhead to request the tag, etc. 14:11:09 I think the only difference would be the initial wait time for newRepo 14:11:10 there was slowness with newrepos for a while. 14:11:11 yeah, I don't think it takes any longer, it's just more process 14:11:17 ahh 14:11:17 but as far as I know all those are solved. 14:11:22 hey 14:11:56 hi, mhroncok 14:12:21 sorry for being late, had to walk the dogs after the previous meeting and it has ended exactly when this one started 14:12:27 the waitrepo time is the same for chaining the build cycle 14:12:39 since you have to wait for kojira to finish before it's available anyway 14:12:55 sure, but for gcc maintainer, there's no wait or chain, just... gcc build 14:13:01 annobin -- let's add the gating tests and them figure the best workflow for that whatever they want side tags or double builds? 14:13:16 *and let them 14:13:17 well, they won't merge the tests either 14:13:29 but why 14:13:30 * nirik doesn't like forcing people to do things... it's much better to convince them. 14:13:31 they don't like the idea of gating tests 14:13:39 I agree with nirik 14:13:49 that's why jakub implemented that weird thing in %check instead that's non-blocking 14:14:04 we're in a no-win scenario right now 14:14:34 it's hard to convince when they don't answer direct questions 14:14:55 voting to the force the team to do something isn't going to work. I think this ticket should be closed and a different approach taken for compiler gating 14:15:19 we have no other approach to compiler gating 14:15:25 dcantrell: why? this is what we have and it works for anybody else 14:15:33 sorry, I mean a different approach to implement the change 14:15:45 I'm fine with closing it if we can't realistically get a policy in place 14:15:56 I agree that we should not force, but I don't think this works 14:16:14 should this go through as a change proposal for F34? 14:16:18 we can modify fedpkg to do the whole side tag thing internally if package == "gcc" 14:16:23 I agree with what mhroncok said above: the gating test is the important part. Sidetags or not are the maintainer's choice. 14:16:23 with an owner and people signed up to do the work? 14:16:28 perhaps we could invite them to a meeting? or some other higher BW discussion? 14:16:37 decathorpe: we could even just block gcc and llvm from direct merging if we must 14:16:45 only allow them in from a side tag 14:16:55 (that was supposed to be a joke bust sure :)) 14:16:56 but those are all painful options 14:17:27 * King_InuYasha is just tired of compiler being broken every release cycle because of annobin 14:17:36 yes, just because the GCC maintainers dont want to cooerate? 14:17:37 proposal: refocus 2454 on gating tests only for the compiler and annobin, followup with maintainers for next meeting 14:17:53 dcantrell: so refocus to what it already is? 14:18:16 remove "side tags" from the title 14:18:16 btw, if a gating test is implemented, they *must* use side tags to merge because their builds will be rejected otherwise 14:18:23 dcantrell: +1 14:18:28 King_InuYasha: i don't agree 14:18:34 King_InuYasha: no 14:18:38 King_InuYasha: How do you figure? 14:18:59 because at least based on what fedora CI folks told me, if a test fails, it's supposed to not be able to be tagged into the buildroot 14:19:09 if it's a "gating test" 14:19:10 the gating test will either pass and will go in 14:19:23 or it will fail and they will need to rebuild in side tag 14:19:36 right 14:19:51 so that means the tests will force side tags anyway 14:19:55 with what they are saying (it works 99% of the time) this will work 14:20:18 so, there's mention of making it less dependent on each other... do we know how much thats happened? perhaps we could ask nickc about that? 14:20:21 Right, it should mean that they only have to deal with a side-tag in the event that the gating test fails 14:20:27 I'm fine with taking that statement at face value if the entire compiler stack is gated 14:20:31 King_InuYasha: the side tags would only be needed if annobin needs to be rebuilt. 14:20:33 llvm, gcc, annobin 14:20:48 zbyszek: which is every time gcc and llvm change 14:20:55 Question: would they be able to tag the succeeded-but-gated GCC into the side-tag? 14:20:58 and if indeed it no longer needs to be built in sync, they won't need to use side tags ever 14:21:00 nirik: that work has not been done 14:21:02 Or would this necessitate rebuilding it again? 14:21:03 but the check would still be in place 14:21:29 well, it seems like it's ongoing in that bug... 14:21:33 sgallagh: they could tag it in, but I am afraid bodhi won't allow the new joined update to have the same build in it 14:21:37 nirik: there's a disagreement on the effectiveness of the approach 14:21:55 well, the check is useful in and of its own, even if annobin isn't the cause of potential compiler issues 14:21:59 sgallagh: but I'm not entirely sure 14:22:00 mhroncok: Afraid because you don't know if it will or afraid because you DO know it will refuse it? 14:22:27 sgallagh: I think it will refuse, but it's not confirmed 14:22:32 dcantrell: I'm fine with your proposal, since I really don't care beyond them not breaking the distro every cycle 14:22:37 so... 14:22:40 dcantrell: +1 14:22:55 mhroncok: Presumably gating tests can be rerun without doing another build 14:23:01 sgallagh: they cannot 14:23:03 If not... that's a bad situation 14:23:04 sgallagh: yes, they can 14:23:09 ...? 14:23:15 sgallagh: by asking ci folks 14:23:24 human overrides don't count :) 14:23:30 * sgallagh sighs 14:24:04 I'd call that a blocker to gating for any package that takes a long time to build 14:24:06 * King_InuYasha mumbles something about zuul not being wired into the CI control mechanism in pagure to rerun pipelines 14:24:39 ok, clearly plenty to discuss here and we need the package maintainers for the packages in question for further discussion 14:24:46 I count +3 for my proposal, if that even matters 14:24:47 agreed 14:25:04 * nirik looks back for the proposal 14:25:27 Proposal: Invite the tools maintainers to next week's meeting, informing them that not showing up means they forfeit the right to an opinion. 14:25:33 dcantrell: +1 from me 14:25:33 sgallagh: +1 14:25:37 you can have my +1 as well, side tags are an "implementation detail" and if they want to rebuild GCC in case of failure I don't care 14:25:44 dcantrell: +1 14:25:46 sgallagh: -1 14:25:53 if we do nothing here, it will eventually be the same as approving the proposal 14:26:07 mhroncok: yep 14:26:26 I believe that defaulting for side tag is the right thing to do, but if they'd rather rebuild for the second time if the test fails, whatever 14:26:47 so that's... 14:26:51 0 14:26:55 the important bit is to get the gating test in place and my impression is that they don't want to do that for resons I don't understand 14:26:56 (for dcantrell's) 14:27:04 mhroncok: they don't like gating tests 14:27:22 King_InuYasha: I have figured that out. but why, that's what I don't understand 14:27:39 King_InuYasha: jakub said that they might not be effective (because no arm64 tests). But apart from that? 14:27:46 My guess is that failure means a really long rebuild 14:27:49 yes 14:27:53 jakub said as much 14:28:06 ok, shall we move on? do I mark this with an agree or anything? I don't know. 14:28:07 he also implied that they expect this failure to happen often 14:28:14 I'm not accepting the Nirvana Fallacy as a valid argument here 14:28:20 sgallagh: only if they don't start the build in a side to begin with ... 14:28:50 one other issue they could have with side tags is making the update at the end... 14:29:10 dcantrell: I think we just try and discuss more and move on... 14:29:20 nirik: noted 14:29:31 let's move on to something less controversial 14:29:37 #topic #2430 Send notifications of new FESCo tickets to fedora-devel (or daily/weekly digests) 14:29:40 .fesco 2430 14:29:41 dcantrell: Issue #2430: Send notifications of new FESCo tickets to fedora-devel (or daily/weekly digests) - fesco - Pagure.io - https://pagure.io/fesco/issue/2430 14:29:51 this still seems redundant 14:30:07 * mhroncok has reconnected, not sure if still receiving messages here 14:30:16 welp 14:30:28 I mean, if we send stuff for tickets that are not caused by anything that happened on the list first anyway, that's fine with me 14:30:42 I thought we'd basically agreed not to bother with this and just do it manually when appropriate. 14:30:48 sgallagh: +1 14:30:54 sgallagh: +1 14:31:02 sgallagh: +1 14:31:08 +1, I thought so too 14:31:11 (I'm not sure if we agreed so, but it sounds like a reasonable course of action.) 14:31:20 +1 14:31:26 yeah, I can't remember if we agreed or not, but I'm fine with that 14:31:27 +1 14:31:31 * mhroncok has lost the connection apparently, what is the proposal? 14:31:33 I don't think we voted on it, but I also don't recall anyone disagreeing with it 14:31:48 I'll phrase it formally: 14:32:24 Proposal: We won't automate this process. Instead, FESCo members will manually alert the fedora-devel list when appropriate. 14:32:32 +1 14:32:46 +1 14:32:49 +1 14:32:53 +1 14:33:33 +1 14:33:54 +1 14:34:14 +1 14:34:26 #agree (+8, 0, -0) 14:34:52 way less discussion :) 14:34:54 #topic #2416 Update 3rd party repo policy 14:34:55 .fesco 2416 14:34:56 dcantrell: Issue #2416: Update 3rd party repo policy - fesco - Pagure.io - https://pagure.io/fesco/issue/2416 14:35:45 so that is about https://pagure.io/fesco/fesco-docs/pull-request/34 14:36:15 I talked with aday, and I'll open a ticket to notify the Council once we're done with the process here, so that they are aware of the changes. 14:36:51 * nirik hasn't had a chance to review the latest. 14:36:57 * mhroncok neither 14:37:10 ok, review and vote in the ticket again? 14:37:17 is it ready for review? 14:37:25 there seem to be some discussion going on still 14:37:51 Yes, it's ready. 14:37:54 oh I was looking at the fesco ticket 14:38:48 let's vote in the ticket, I did not review the latest too 14:39:16 Same 14:39:31 ok, let's all vote in the fesco ticket then 14:39:41 fine with me 14:39:54 #topic #2410 RFE: Rename dist-git "master" branch to "rawhide" 14:39:55 .fesco 2410 14:39:56 dcantrell: Issue #2410: RFE: Rename dist-git "master" branch to "rawhide" - fesco - Pagure.io - https://pagure.io/fesco/issue/2410 14:40:19 there's nothing actionable there 14:40:32 I'm cool with the idea of renaming the repo branch from master to rawhide 14:40:41 that's what I thought. in that case I will close the ticket 14:40:48 +1 to close 14:40:51 +1 14:40:54 * nirik hasn't had a chance to put together a change proposal, but plans to try 14:41:00 I don't understand why we should approve the idea before they even submit a change proposal 14:41:02 nirik: +1 14:41:25 I think we may want to go with 'main' as thats what many places are doing. 14:41:41 but thats something we could discuss with the change discussion. 14:41:51 that makes no sense. rawhide should be rawhide, if we change it :) 14:41:59 decathorpe: +1 14:42:10 decathorpe: +1 14:42:12 well, that makes it 'special' 14:42:15 so? 14:42:33 increased work on tooling and expectation of users. 14:42:34 how so? 14:42:34 if rawhide is the default branch, then it should be fine 14:42:37 ok, I'll close it. last one on my list: 14:42:40 but I will stop now 14:42:44 #topic #2452 F34 Self-Contained Change: Policy for Modules in Fedora and Fedora ELN 14:42:47 .fesco 2452 14:42:48 dcantrell: Issue #2452: F34 Self-Contained Change: Policy for Modules in Fedora and Fedora ELN - fesco - Pagure.io - https://pagure.io/fesco/issue/2452 14:43:13 meh ... what do we need to talk about here? 14:43:28 I don't know. I was going through all open tickets picking out things that are kinda sitting around 14:43:33 is there anything to discuss here? 14:43:37 does the ticket need to stay open? 14:43:39 I don't know 14:43:53 * King_InuYasha is tired 14:44:10 I think it's perhaps down to just voting... if all the feedback from the list is merged back in? 14:44:12 I have answered the questions posed on the mailing list 14:44:16 I think there were some votes in ticket already? 14:44:30 (To the best of my ability) 14:44:31 yep. 14:44:32 though mine is a rather weak +1 ... 14:44:52 sgallagh: since it's been clarified on the mailing list that this policy should only apply to ELN, can you adjust the text to make that clear? Current wording is misleading. 14:44:52 * nirik is +1, I guess I will add that to the ticket. 14:44:53 yeah I voted in the ticket 14:45:01 same 14:46:23 zbyszek: I thought I had, but if you want to suggest better phrasing, please do 14:46:41 Yeah, I'm rereading. 14:47:03 I'll read over all of the updates and current proposal and vote in the ticket 14:47:17 Yeah, same here. 14:47:20 I think my vote should be obvious :) 14:47:40 #topic Next week's chair 14:48:15 anyone? 14:48:36 I can do it. 14:48:41 thanks! 14:48:50 #action zbyszek will chair next meeting 14:49:01 #topic Open Floor 14:49:17 Quick q: 14:49:47 the first ticket we discussed, about compiler side-tags, do we need to #action someone to restart the discussion with gcc maintainers? 14:50:08 I asked that and got no response, so I didn't 14:50:12 I'm ok taking that action 14:50:34 dcantrell++ 14:50:34 decathorpe: Karma for dcantrel changed to 3 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:51:02 dcantrell++, thanks 14:51:05 np 14:51:18 I've made notes for all of the tickets and was going to go through them after this meeting 14:51:40 anything else from anyone? 14:51:51 I know we're almost at an hour, sorry for that 14:52:14 ok, with that I'm going call end of meeting 14:52:17 dcantrell: the meeting is officially 2h, anything less is a bonus 14:52:26 #endmeeting