On Dienstag, 6. Mai 2025 13:05:55 Mitteleuropäische Sommerzeit Ben Cooksley
wrote:
> On Tue, May 6, 2025 at 9:35 PM Milian Wolff wrote:
> > On Mittwoch, 30. April 2025 21:07:35 Mitteleuropäische Sommerzeit Ben
> > Cooksley
> >
> > wrote:
> > > On Thu, May 1, 2025 at 3:42 AM Milian Wolff wrote:
Hi,
in the .kde-ci.yml:
https://lxr.kde.org/search?%21v=kf6-qt6&_filestring=&_string=use-ccache.
Cheers,
Johnny
Le mer. 7 mai 2025 à 14:20, Milian Wolff a écrit :
>
> On Dienstag, 6. Mai 2025 13:05:55 Mitteleuropäische Sommerzeit Ben Cooksley
> wrote:
> > On Tue, May 6, 2025 at 9:35 PM Milian W
On Dienstag, 6. Mai 2025 11:26:30 Mitteleuropäische Sommerzeit Ben Cooksley
wrote:
> On Tue, May 6, 2025 at 5:36 AM Volker Krause wrote:
> > On Freitag, 2. Mai 2025 22:55:34 Mitteleuropäische Sommerzeit Ben Cooksley
> >
> > wrote:
> > > On Sat, May 3, 2025 at 8:26 AM Christoph Cullmann > >
> >
On Tue, May 6, 2025 at 9:35 PM Milian Wolff wrote:
> On Mittwoch, 30. April 2025 21:07:35 Mitteleuropäische Sommerzeit Ben
> Cooksley
> wrote:
> > On Thu, May 1, 2025 at 3:42 AM Milian Wolff wrote:
> > > On Freitag, 18. April 2025 21:25:36 Mitteleuropäische Sommerzeit Ben
> > > Cooksley
> > >
>
On Mittwoch, 30. April 2025 21:07:35 Mitteleuropäische Sommerzeit Ben Cooksley
wrote:
> On Thu, May 1, 2025 at 3:42 AM Milian Wolff wrote:
> > On Freitag, 18. April 2025 21:25:36 Mitteleuropäische Sommerzeit Ben
> > Cooksley
> >
> > wrote:
> > > Hi all,
> > >
> > > Over the past week or two the
On Tue, May 6, 2025 at 5:36 AM Volker Krause wrote:
> On Freitag, 2. Mai 2025 22:55:34 Mitteleuropäische Sommerzeit Ben Cooksley
> wrote:
> > On Sat, May 3, 2025 at 8:26 AM Christoph Cullmann >
> >
> > wrote:
> > > On Friday, May 2nd, 2025 at 22:18, Ben Cooksley
> wrote:
> > >
> > > On Sat, May
On Freitag, 2. Mai 2025 22:55:34 Mitteleuropäische Sommerzeit Ben Cooksley
wrote:
> On Sat, May 3, 2025 at 8:26 AM Christoph Cullmann
>
> wrote:
> > On Friday, May 2nd, 2025 at 22:18, Ben Cooksley wrote:
> >
> > On Sat, May 3, 2025 at 3:27 AM Christoph Cullmann
> >
> > wrote:
> >> Hi,
> >>
On Sat, May 3, 2025 at 8:26 AM Christoph Cullmann
wrote:
>
>
> On Friday, May 2nd, 2025 at 22:18, Ben Cooksley wrote:
>
> On Sat, May 3, 2025 at 3:27 AM Christoph Cullmann
> wrote:
>
>>
>> Hi,
>>
>> at work we use cmake unity build to save time & costs.
>>
>> Would that be some idea here, too?
On Friday, May 2nd, 2025 at 22:18, Ben Cooksley wrote:
> On Sat, May 3, 2025 at 3:27 AM Christoph Cullmann
> wrote:
>
> >
> >
> > Hi,
> >
> > at work we use cmake unity build to save time & costs.
> >
> > Would that be some idea here, too?
> >
> > Naturally as side effect that ca
On Sat, May 3, 2025 at 3:27 AM Christoph Cullmann
wrote:
>
> Hi,
>
> at work we use cmake unity build to save time & costs.
>
> Would that be some idea here, too?
>
> Naturally as side effect that can hide compile issues
> or introduce ones.
>
We could look into that, just not sure how it would
Hi,
at work we use cmake unity build to save time & costs.
Would that be some idea here, too?
Naturally as side effect that can hide compile issues
or introduce ones.
Greetings
Christoph
On Friday, April 18th, 2025 at 21:25, Ben Cooksley wrote:
> Hi all,
> Over the past week or two there h
On Thu, May 1, 2025 at 3:42 AM Milian Wolff wrote:
> On Freitag, 18. April 2025 21:25:36 Mitteleuropäische Sommerzeit 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 investiga
On Freitag, 18. April 2025 21:25:36 Mitteleuropäische Sommerzeit 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.
> Plasma Workspace/Desktop: At least i
>> Another point that requires extra build time for Krita is an
inappropriate timeout on 100 minutes. A lot of our windows builds are
terminated at around 95% completion because of this timeout, so we have to
rerun them and, effectively, consume more and more CI time.
>Have you got a list of these
> This is probably at least in part due to Windows on Docker having
extremely poor file system performance even vs. straight NTFS (which isn't
great to begin with).
Well, Krita builds on a normal Windows system are also quite slow (at least
much slower than on Linux). Though they are still much fa
Yes, that is a full clean build after the build directory is configured
from scratch. The dependencies are prepared before that, and this is just
the time to run ninja which lists 4900 build steps or so (I can't
remember). I mean, the build isn't exactly very fast even on a reasonably
high-end syst
On Tue, Apr 22, 2025 at 10:53 PM Maciej Jesionowski
wrote:
> Yes, that is a full clean build after the build directory is configured
> from scratch. The dependencies are prepared before that, and this is just
> the time to run ninja which lists 4900 build steps or so (I can't
> remember). I mean,
On Tue, Apr 22, 2025 at 10:44 PM Konstantin Kharlamov
wrote:
> On Tue, 2025-04-22 at 07:15 +1200, Ben Cooksley wrote:
> > On Tue, Apr 22, 2025 at 5:57 AM Dmitry Kazakov
> > wrote:
> > > Hi, Ben!
> > >
> >
> >
> > Hey Dmitry,
> >
> > >
> > > As for Krita, most of CI time is spent on the Windows p
On Tue, 2025-04-22 at 07:15 +1200, Ben Cooksley wrote:
> On Tue, Apr 22, 2025 at 5:57 AM Dmitry Kazakov
> wrote:
> > Hi, Ben!
> >
>
>
> Hey Dmitry,
>
> >
> > As for Krita, most of CI time is spent on the Windows pipeline,
> > which build extremely slowly due to done obscure filesystem issues
On Tue, Apr 22, 2025 at 9:53 AM Maciej Jesionowski wrote:
> Hi,
>
Hi Maciej,
> Are these servers running multiple builds at a time, or is a Windows build
> given the full host resources, i.e. 8c/16t and 64GB of RAM? If you can
> monitor the resources in real time, it would be interesting to co
Hi,
Are these servers running multiple builds at a time, or is a Windows build
given the full host resources, i.e. 8c/16t and 64GB of RAM? If you can
monitor the resources in real time, it would be interesting to confirm if
indeed the CPU utilization is significantly lower than 100%, meaning
someth
Hi, Ben!
As for Krita, most of CI time is spent on the Windows pipeline, which build
extremely slowly due to done obscure filesystem issues (searching includes
is extremely slow). I personally don't know how to fix it. I tried: 1) PCH
builds, 2) relative includes, 3) split debug info (dwo). The on
On Tue, Apr 22, 2025 at 5:57 AM Dmitry Kazakov wrote:
> Hi, Ben!
>
Hey Dmitry,
>
> As for Krita, most of CI time is spent on the Windows pipeline, which
> build extremely slowly due to done obscure filesystem issues (searching
> includes is extremely slow). I personally don't know how to fix i
On Sun, Apr 20, 2025 at 8:26 AM Ben Cooksley wrote:
> 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
On Sun, Apr 20, 2025 at 9:10 PM Albert Astals Cid wrote:
> El divendres, 18 d’abril del 2025, a les 21:25:36 (Hora d’estiu d’Europa
> central), Ben Cooksley va escriure:
> > Hi all,
> >
> > Over the past week or two there have been a number of complaints
> regarding
> > CI builder availability wh
El divendres, 18 d’abril del 2025, a les 21:25:36 (Hora d’estiu d’Europa
central), Ben Cooksley va escriure:
> 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
El dissabte, 19 d’abril del 2025, a les 10:47:13 (Hora d’estiu d’Europa
central), Ben Cooksley va escriure:
> 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
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
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
On Sun, Apr 20, 2025 at 3:05 AM Thomas Friedrichsmeier <
thomas.friedrichsme...@kdemail.net> wrote:
> On Sat, 19 Apr 2025 07:25:36 +1200
> Ben Cooksley wrote:
> [...]
> > This morning I ran a basic query to ascertain the top 20 projects for
> > CI time utilisation on invent.kde.org which revealed
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
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
On Sun, Apr 20, 2025 at 3:05 AM Thomas Friedrichsmeier <
thomas.friedrichsme...@kdemail.net> wrote:
> On Sat, 19 Apr 2025 07:25:36 +1200
> Ben Cooksley wrote:
> [...]
> > This morning I ran a basic query to ascertain the top 20 projects for
> > CI time utilisation on invent.kde.org which revealed
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
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
On Sat, 19 Apr 2025 07:25:36 +1200
Ben Cooksley wrote:
[...]
> This morning I ran a basic query to ascertain the top 20 projects for
> CI time utilisation on invent.kde.org which revealed the following:
What (rough) percentage is that of the total? I.e. is the problem more
one of a few projects h
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 frontlines. The earlier we
> share feedback the better, and review
>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"
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.
On Sat, 2025-04-19 at 20:33 +1200, Ben Cooksley wrote:
> 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
> > >
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
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
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
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
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
45 matches
Mail list logo
