17:01:53 #startmeeting FESCO (2023-01-03) 17:01:53 Meeting started Tue Jan 3 17:01:53 2023 UTC. 17:01:53 This meeting is logged and archived in a public location. 17:01:53 The chair is mhroncok. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 17:01:53 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:01:53 The meeting name has been set to 'fesco_(2023-01-03)' 17:01:55 #meetingname fesco 17:01:55 The meeting name has been set to 'fesco' 17:01:59 #chair nirik, decathorpe, zbyszek, sgallagh, mhroncok, dcantrell, music, mhayden, Conan_Kudo, Pharaoh_Atem, Son_Goku, King_InuYasha, Sir_Gallantmon, Eighth_Doctor 17:01:59 Current chairs: Conan_Kudo Eighth_Doctor King_InuYasha Pharaoh_Atem Sir_Gallantmon Son_Goku dcantrell decathorpe mhayden mhroncok music nirik sgallagh zbyszek 17:02:08 .hello2 17:02:08 #topic init process 17:02:08 dcantrell: dcantrell 'David Cantrell' 17:02:19 .hello churchyrad 17:02:20 mhroncok: Sorry, but user 'churchyrad' does not exist 17:02:22 .hello2 17:02:24 zbyszek: zbyszek 'Zbigniew Jędrzejewski-Szmek' 17:02:36 .hello churchyard 17:02:37 mhroncok: churchyard 'Miro Hrončok' 17:02:45 .hello dcavalca 17:02:46 davide: dcavalca 'Davide Cavalca' 17:03:06 .hello salimma 17:03:07 salimma: salimma 'Michel Alexandre Salim' 17:03:11 .hello catanzaro 17:03:14 MichaelCatanzaro: catanzaro 'Michael Catanzaro' 17:03:18 .hi 17:03:19 mhayden: mhayden 'Major Hayden' 17:05:14 I count 4 FESCo members 17:05:18 .hello ngompa 17:05:19 Eighth_Doctor: ngompa 'Neal Gompa' 17:05:23 that's 5 17:06:26 #topic #2923 Re-vote for Change proposal: Add -fno-omit-frame-pointer to default 17:06:26 compilation flags 17:06:31 .fesco 2923 17:06:32 mhroncok: Issue #2923: Re-vote for Change proposal: Add -fno-omit-frame-pointer to default compilation flags - fesco - Pagure.io - https://pagure.io/fesco/issue/2923 17:06:51 I count +4,0,-1 in the ticket 17:07:15 +1 from me 17:07:19 is there anybody from fesco who has not voted in the ticket and is ready to be the fifth +1? 17:07:21 I can also add it to the ticket 17:07:37 that would be +5 17:08:08 do we want to discuss this, or approve it like that? 17:08:35 i have to run, but if people have follow up questions i can try to respond later today 17:08:35 * mhroncok feels like the discussion has been exhausted 17:09:02 hergertme: thanks for joining and the writeup in the ticket. 17:09:27 np 17:09:37 mhroncok: agreed. Let's just do whatever makes the most sense procedurally. You're the boss today. 17:09:58 does anybody want to say something? 17:10:12 i'm still very much torn on this one :| 17:10:23 same for me 17:10:49 also, should Python opt-out for now? 17:10:50 I think this is probably one of the few changes where we've gotten lots of external and internal discussion, but I do really believe that this is going to bring a ton of benefit for developers on Fedora 17:11:04 I think it probably makes sense for Python to opt-out 17:11:06 i think that it's worth the engineering effort to make things work without frame pointers, because we'll always have to progress towards that. but i think having them now, until we can have a bulletproof solution in place, is the better move 17:11:34 Eighth_Doctor, i hear upcoming python versions will improve performance wrt frame-pointers, so opt-out not needed 17:11:43 mhayden: what are your worries? 17:11:48 same goes for boringssl 17:11:49 future is the key word 17:11:53 yeah, Python 3.12 will recommend being compiled with it 17:12:02 i guess i've got quantifiable developer benefits on one hand and unquantified performance impacts on the other 🙃 17:12:11 but Python 3.11 is in F38, and it's going to hurt with it on 17:12:26 opt-out for 3.11 makes sense then 17:12:48 i mean, if we have this opt-out capability that is meant to be temporary, i could probably get on board with this 17:13:00 fortunately it's very easy to opt-out, just undefine the enablement variable 17:13:02 we'd started taking a closer look to the Python regression before the break, will follow up on that and see if there's something that can be done in the short term 17:13:13 if it makes people feel any better, macos still has frame-pointers for exactly the reasons we want, and it's why their profilers work ;) 17:13:17 enablement variable -> RPM macro? 17:13:20 but otherwise yeah, the point of the opt out is to be able to exclude problematic packages as needed 17:13:24 mhroncok: yes 17:13:29 yes it's a macro 17:13:38 hergertme: Windows too with SEH :) 17:13:46 Linux is the odd-duck out 17:13:47 https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/230 is the implementation 17:13:47 anybody else wants to cast their votes? 17:14:04 mhroncok: okay, now that i understand the opt-out process better, i can be a +1 here 17:14:25 mhroncok: i updated the ticket 17:14:38 I abstain. I see the benefit of this but I worry about the "we'll evaluate this" part. I am afraid we won't :D 17:14:39 mhayden: My understanding is that that opt-out is always an option. The proposal talks about *default* flags, and packages are (in general) allowed to override their flags if appropriate. 17:14:52 yup 17:15:08 even before we started conditionalizing flags, this has always been a thing 17:15:27 i think this also puts the burden of proof on removing frame pointers to prove it is faster and worth the cost of developers moving to other platforms to develop software 17:15:27 (In some cases, we disallow overriding, or at least raise the bar, e.g. for security flags. But I don't think that frame pointers would be covered by such a strong policy.) 17:15:37 mhroncok: I'll hold Davide Cavalca and daandemeyer to the fire :) 17:15:43 I also don't fully understand why we explicitly require 2 Fedora releases for the evaluation 17:16:38 I count +6,1,-1 now 17:17:01 with only sgallagh not voting 17:17:04 mhroncok: we want some time to both figure out why some packages are impacted (e.g. like with Python), but also to give time for the tools to catch up and for people to start making use of this. 17:17:14 yup, this :) 17:17:32 (no need to convince me, the vote is pretty obvious now) 17:17:42 If the effect is very terrible, we *can* revert earlier. But I think that waiting a bit for things to "settle down" will give as a more reliable result. 17:17:43 so unless there's something else to discuss 17:18:10 with mass rebuilds happening for gcc/etc, how will we know if regression was from frame-pointers or gcc? 17:18:25 or does that matter? 17:18:34 it doesn't really matter that much 17:18:45 cool 17:18:51 it's easy enough to retest by flipping things off and on 17:18:57 if someone suspects it 17:19:08 hergertme: first, we would establish whether there is a regression. And if there is, then in which packages. And then you can bisect by channging the flags or the compiler… 17:19:25 sgtm 17:20:38 #agree APPROVED (+6,1,-1) This Change is implemented for Fedora Linux 38 and we evaluate whether to retain it by Fedora Linux 40. This Change must be implemented in a manner which packages are able to trivially opt-out of retaining frame pointers during compilation so that packages that take larger performance hits can easily revert. 17:20:53 🎉 17:21:02 Phew. 17:21:05 thanks everyone! 17:21:20 #info Change owners please coordinate the change with the Python Maintainers before changing the defaults 17:21:46 #topic Next week's chair 17:21:58 I can probably do it 17:22:08 let me check real quick 17:22:17 #action Conan Kudo will probably chair next meeting 17:22:26 yeah lgtm 17:22:32 I'll undo if you cannot 17:22:34 thanks everyone! 17:23:06 .hello music 17:23:07 music[m]: music 'Benjamin Beasley' 17:23:10 #topic Open Floor 17:23:17 Can we do #2907 now? 17:23:21 .fesco 2907 17:23:22 zbyszek: Issue #2907: Exception for spliting OpenJDK build and integration - fesco - Pagure.io - https://pagure.io/fesco/issue/2907 17:23:47 #topic #2907 Exception for spliting OpenJDK build and integration 17:23:53 .fesco 2907 17:23:54 mhroncok: Issue #2907: Exception for spliting OpenJDK build and integration - fesco - Pagure.io - https://pagure.io/fesco/issue/2907 17:24:08 1) I don't believe an exception is needed 17:24:18 2) If needed, it would be an FPC exception 17:24:35 Right. 17:24:53 Proposal: We confirm that no exception is needed. 17:25:11 +1 for no exception needed 17:25:13 +1 from me 17:25:16 +1 17:25:24 +1 17:25:54 (FWIW, I also agree with 2, but it's moot.) 17:27:02 I'm iffy about it... +0 17:27:34 as in you don't want them to build it this way or you belive this requires an exception? 17:28:18 we are at (+4,1,-0) for no exception required 17:28:42 we also have Stephen +1ing in the ticket, but not exactly for this 17:29:01 other folks? 17:30:34 count me as a +1 17:31:20 #agree No exception is needed (+5,1,-0) 17:31:28 Thanks! 17:31:38 the latter 17:31:44 but I'm outvoted, so meh 17:31:50 ack 17:31:52 #topic Open Floor 17:32:03 I ahve a question about ticket policy 17:32:06 *have 17:32:12 a ticket is opened on day 0 17:32:24 during the first week, it gains +2 17:32:34 right after that, at day 9, it gains another +1 17:32:48 is it immediately approved, or does it wait until day 14? 17:32:58 my understanding always was that it waits 17:33:09 but zbyszek seems to think otherwise 17:33:43 my understanding is that it's approved when the tickets are being evaluated to be announced 17:33:59 "Once a ticket has a formal proposal offered, FESCo members have one week to either vote for or against it or else propose the ticket for the next weekly meeting agenda. At the end of that one week, if the proposal has gained at least three "for" votes and no "against" votes, it is approved." 17:34:32 "If the week passes and the required number of votes have not been met, the proposal is extended by one further week and the minimum requirement becomes a single positive "for" vote." 17:34:46 OK, so it seems mhroncok was right, and I was wrong. 17:34:50 so if the ticket is "evaluated to be announced" at day 8 and it has +2 from the first week and the person who evaluates it casts +1, it is approved? 17:35:05 that's what I figured it was 17:35:49 But it seems that we weren't following the rules. We would often close tickets without exactly checking which votes were cast in the first 7 days and which after. 17:36:25 me has not :) 17:36:40 anyway, I can take this async 17:36:50 won't hold you hostage any more 17:37:05 unless there is some other thing for open floor 17:37:18 🦗 17:37:18 Well, if we were stricly following the policy, we would not count the votes cast after 7 days. 17:37:54 not unless it has been 14 17:37:59 days, not votes 17:38:02 Because "it is approved" "at then end of that week" means that whatever the tally is *at that exact time* is the end tally. 17:38:37 (I'm talking about the case where there were 3..8 positive votes.) 17:38:47 But meh. 17:38:55 i like your attention to detail, zbyszek -- i completely overlooked the scenario you're talking about 17:39:56 I'm a bit lost 17:40:01 sorry 17:41:27 anyway 17:41:38 I am going to end this, ok? 17:41:43 mhroncok: you were right in the ticket, we should wait until 14th day. 17:41:48 Yes. 17:42:06 #endmeeting