Re: Master moves to Qt 6 this Wednesday

El dilluns, 11 de setembre de 2023, a les 13:58:18 (CEST), 
[email protected] va escriure:
> Hi,
> 
> >> In most cases it goes away with a new full cache build.
> >> 
> >> If worked here
> >> 
> >> https://invent.kde.org/utilities/kate/-/commit/c8fad91ccd47b57c1c1039c496
> >> a6b 99b5f5e3220
> >> 
> >> And with
> >> 
> >> https://invent.kde.org/utilities/kate/-/commit/4041ef2956fceb4335243ed680
> >> c27 4d79082f66b
> >> 
> >> Even the most trivial test crash.
> >> 
> >> Naturally I can disable all tests, but then I will never see if that
> >> recovers again.
> > 
> > That is your problem.
> > 
> > Right now you have any single person that proposes a MR against kate
> > wondering
> > how their change broke CI, when it didn't, that's not acceptable for a
> > 4 week
> > (and in your words, "infinite" since you don't know what's wrong) time
> > frame.
> 
> I pinged now people to redo the cache.
> At the moment not even that works as frameworks doesn't compile.
> 
> I don't think it is helpful to disable the CI

I don't think it is helpful to have fake broken CI, and I have been warning 
for weeks that I will disable broken CI so I will act on it.

> I keep an eye on that,
> but I don't think I am responsible to takle all global CI breakages.

Nothing else is broken but kate (this is my past 3 weeks status report 
speaking, current point in time may be different), so no you're not 
responsible to fix all global CI breakeages, you're responsible of fixing kate 
CI.

Cheers,
  Albert

> 
> But I should have pinged people that stuff is globally broken, sorry
> about that.
> 
> Greetings
> Christoph