Master moves to Qt 6 this Wednesday

[Albert Astals Cid]

El dilluns, 11 de setembre de 2023, a les 23:44:01 (CEST), 
christoph at cullmann.io va escriure:
> On 2023-09-11 21:42, Albert Astals Cid wrote:
> > El dilluns, 11 de setembre de 2023, a les 13:58:18 (CEST),
> > 
> > christoph at cullmann.io 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/c8fad91ccd47b57c1c1039c
> >> >> 496
> >> >> a6b 99b5f5e3220
> >> >> 
> >> >> And with
> >> >> 
> >> >> https://invent.kde.org/utilities/kate/-/commit/4041ef2956fceb4335243ed
> >> >> 680
> >> >> 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.
> 
> Hi,
> 
> that is not very fair and if the CI is disabled build failures will
> creep in.

CI job is still there so no build failure will creep in, it's only that 
Windows/Qt6 failing tests are not considered a fail anymore, so basically the 
same status as before but now it's marked as passing instead of failing.

Once the tests are passing again the change can be put back to consider 
Windows/Qt6 failing tests a failure of the job.

Best Regards,
  Albert

> 
> And yes, I watch for that.
> 
> ATM the cache is still not redone as frameworks don't compile.
> 
> Could you please just wait, perhaps I miss a point, or does that block
> anything?
> 
> If you really have something blocked by that I can disable the tests.
> 
> Greetings
> Christoph
> 
> > Cheers,
> > 
> >   Albert
> >> 
> >> But I should have pinged people that stuff is globally broken, sorry
> >> about that.
> >> 
> >> Greetings
> >> Christoph