BUILD FAILURE
Build URL
https://build.kde.org/job/Plasma/job/plasma-mobile/job/kf5-qt5%20SUSEQt5.15/10/
Project:
kf5-qt5 SUSEQt5.15
Date of build:
Fri, 11 Feb 2022 05:22:41 +
Build duration:
42 sec and counting
CONSOLE OUTPUT
[...truncated 230
BUILD FAILURE
Build URL
https://build.kde.org/job/Plasma/job/plasma-mobile/job/kf5-qt5%20SUSEQt5.15/9/
Project:
kf5-qt5 SUSEQt5.15
Date of build:
Fri, 11 Feb 2022 05:21:06 +
Build duration:
36 sec and counting
CONSOLE OUTPUT
[...truncated 230
We should wrap this as the dates are getting near.
Should we do March 5th and 6th?
On Mon, Jan 31, 2022 at 11:18 AM Marco Martin wrote:
>
> Hi all,
> Here is a doodle with a bunch of dates to plan the sprint
> https://doodle.com/poll/nvdyzp979y8dvfyd?utm_source=poll_medium=link
> --
> Marco
On 2/10/22 11:07, Ben Cooksley wrote:
Hence the feeling of impending doom (imagine if you were getting a flood
of bug reports about a single issue and knew that it was only going to
get bigger before it got smaller)
JFYI there is no need to imagine; that's literally the everyday reality
for
On Fri, Feb 11, 2022 at 1:23 AM Aleix Pol wrote:
> On Wed, Feb 9, 2022 at 11:05 AM Ben Cooksley wrote:
> >
> > On Wed, Feb 9, 2022 at 4:30 AM Nate Graham wrote:
> >>
> >> Much work is currently in progress to actually fix these issues. I see
> >> multiple merge requests across multiple repos
On Wed, Feb 9, 2022 at 11:05 AM Ben Cooksley wrote:
>
> On Wed, Feb 9, 2022 at 4:30 AM Nate Graham wrote:
>>
>> Much work is currently in progress to actually fix these issues. I see
>> multiple merge requests across multiple repos being reviewed and merged.
>> I think it makes sense to let that
On Thu, Feb 10, 2022 at 11:05 AM Ben Cooksley wrote:
>
>
>
> On Thu, Feb 10, 2022 at 8:20 AM Aleix Pol wrote:
>>
>> [Snip]
>>
>> We still haven't discussed here is how to prevent this problem from
>> happening again.
>>
>> If we don't have information about what is happening, we cannot fix
On Thu, Feb 10, 2022 at 8:20 AM Aleix Pol wrote:
> [Snip]
>
> We still haven't discussed here is how to prevent this problem from
> happening again.
>
> If we don't have information about what is happening, we cannot fix
> problems.
>
Part of the issue here is that the problem only came to
