Re: CI Utilisation and system efficiency

2025-04-19 Thread Neal Gompa
On Fri, Apr 18, 2025 at 3:26 PM Ben Cooksley wrote: > > > When reviewing the list of CI builds projects have enabled, it is important > to consider to what degree your project benefits from having various builds > enabled. One common pattern i've seen is having Alpine, SUSE Qt 6.9 and SUSE > Qt

Re: CI Utilisation and system efficiency

2025-04-19 Thread Ingo Klöcker
On Samstag, 19. April 2025 21:29:07 Mitteleuropäische Sommerzeit Ben Cooksley wrote: > On Sun, Apr 20, 2025 at 7:21 AM Ingo Klöcker wrote: > > Sounds like we shouldn't be so trigger-happy clicking the Rebase button on > > our > > MRs when it's not really necessary. We could rebase locally and the

Re: CI Utilisation and system efficiency

2025-04-19 Thread Ben Cooksley
On Sun, Apr 20, 2025 at 1:50 AM Linus Jahn wrote: > On Sat, 19 Apr 2025 13:23:59 +0100 > David Edmundson wrote: > > > >Realistically merge requests shouldn't be proposed until people are > > >ready to get something reviewed and merged in... > > > > That's not realistic with how it is on the fron

Re: CI Utilisation and system efficiency

2025-04-19 Thread Ben Cooksley
On Sun, Apr 20, 2025 at 12:24 AM David Edmundson wrote: > >Realistically merge requests shouldn't be proposed until people are ready > to get something reviewed and merged in... > > That's not realistic with how it is on the frontlines. The earlier we > share feedback the better, and reviews can

Re: CI Utilisation and system efficiency

2025-04-19 Thread Ben Cooksley
On Sun, Apr 20, 2025 at 7:21 AM Ingo Klöcker wrote: > On Samstag, 19. April 2025 10:33:45 Mitteleuropäische Sommerzeit Ben > Cooksley > wrote: > > A big part of the issue here is our rebase centric workflow - normally > with > > Gitlab you use merge commits and in this workflow CI only runs when

Re: CI Utilisation and system efficiency

2025-04-19 Thread Ingo Klöcker
On Samstag, 19. April 2025 10:33:45 Mitteleuropäische Sommerzeit Ben Cooksley wrote: > A big part of the issue here is our rebase centric workflow - normally with > Gitlab you use merge commits and in this workflow CI only runs when the MR > changes. > With a rebase workflow like ours though, othe

Re: CI Utilisation and system efficiency

2025-04-19 Thread Ben Cooksley
On Sun, Apr 20, 2025 at 3:19 AM Akseli Lahtinen wrote: > On Friday 18 April 2025 22:25:36 Eastern European Summer Time Ben Cooksley > wrote: > > Hi all, > > > > Over the past week or two there have been a number of complaints > regarding > > CI builder availability which i've done some investigat

Re: CI Utilisation and system efficiency

2025-04-19 Thread Gleb Popov
On Sat, Apr 19, 2025 at 11:47 AM Ben Cooksley wrote: > > - FreeBSD Qt 6.9 monitors buildability on BSD libc + Clang + Qt 6.9 FreeBSD is at Qt 6.8 at the moment. We're close to updating to 6.9 though.

Re: CI Utilisation and system efficiency

2025-04-19 Thread Akseli Lahtinen
On Friday 18 April 2025 22:25:36 Eastern European Summer Time Ben Cooksley wrote: > Hi all, > > Over the past week or two there have been a number of complaints regarding > CI builder availability which i've done some investigating into this > morning. > Hi, is there a possibility we don't run

Re: CI Utilisation and system efficiency

2025-04-19 Thread Martin Gysel
Am Samstag, 19. April 2025, 10:33:45 Mitteleuropäische Sommerzeit schrieb Ben Cooksley: > > Not sure what we can do about kwin. I looked how we can reduce the time > > needed to run tests, and there's not much space for improvements anymore. > > > > Speaking for kwin, I personally wouldn't mind

Re: CI Utilisation and system efficiency

2025-04-19 Thread David Edmundson
>Realistically merge requests shouldn't be proposed until people are ready to >get something reviewed and merged in... That's not realistic with how it is on the frontlines. The earlier we share feedback the better, and reviews can take many many iterations. There's a "CI_MERGE_REQUEST_APPROVED"

Re: CI Utilisation and system efficiency

2025-04-19 Thread Ben Cooksley
On Sat, Apr 19, 2025 at 7:25 AM Ben Cooksley wrote: > Hi all, > > Over the past week or two there have been a number of complaints regarding > CI builder availability which i've done some investigating into this > morning. > > Part of this is related to the Windows CI builders falling offline due

Re: CI Utilisation and system efficiency

2025-04-19 Thread Ben Cooksley
On Sat, Apr 19, 2025 at 8:05 PM laurent Montel wrote: > Le vendredi 18 avril 2025, 21:25:36 heure d’été d’Europe centrale Ben > Cooksley a écrit : > > Hi all, > > > Ruqola: Appears to be conducting a development process whereby changes > are > > made in stable then immediately merged to master in

Re: CI Utilisation and system efficiency

2025-04-19 Thread Ben Cooksley
On Sat, Apr 19, 2025 at 8:07 PM Vlad Zahorodnii wrote: > On 4/19/25 10:53 AM, Kai Uwe Broulik wrote: > > Hi, > > > > thanks for looking into this. > > > > It seems a major contributor to CI time is the fact that a merge > > request runs and once merged, master runs another pretty much > > identic

Re: CI Utilisation and system efficiency

2025-04-19 Thread Vlad Zahorodnii
On 4/19/25 10:53 AM, Kai Uwe Broulik wrote: Hi, thanks for looking into this. It seems a major contributor to CI time is the fact that a merge request runs and once merged, master runs another pretty much identical pipeline right after that. As for KWin: Not sure which one we could axe. KWi

Re: CI Utilisation and system efficiency

2025-04-19 Thread laurent Montel
Le vendredi 18 avril 2025, 21:25:36 heure d’été d’Europe centrale Ben Cooksley a écrit : > Hi all, > Ruqola: Appears to be conducting a development process whereby changes are > made in stable then immediately merged to master in a ever continuing loop. > Please discontinue this behaviour and onl

Re: CI Utilisation and system efficiency

2025-04-19 Thread Kai Uwe Broulik
Hi, thanks for looking into this. It seems a major contributor to CI time is the fact that a merge request runs and once merged, master runs another pretty much identical pipeline right after that. As for KWin: Not sure which one we could axe. KWin uses a bunch of internal Qt stuff, so catc