[Kde-pim] Request: disable CI mails on the pim list

[Ben Cooksley]

On Sat, Dec 28, 2013 at 3:03 AM, Albert Astals Cid <aacid at kde.org> wrote:
> El Dimarts, 24 de desembre de 2013, a les 21:39:02, Ben Cooksley va escriure:
>> Hello all,
>>
>> As previously noted, if the tests weren't fixed I would be revoking
>> the execution of tests from kdepim.
>> This has now been done.
>
> What's the point of this? I mean we do have jenkins so we find the failing
> tests, if you disable the test execution we're missing half of the story no?
>
> What problem is the failing tests causing that you had to disable them?

The CI system does exist to find broken tests, yes. However there is
very little point in it finding broken tests, if nobody fixes them.

It sent countless (in excess of 40) mails to the PIM mailing list over
several days, to the extent it generated complaints about the noise of
the system (and even suggestions that the system be more intelligent
and only send reminders every day or so). Based on this I gathered
that the PIM developers found the system to be of no use - as they
clearly were ignoring it and just wanted it silenced.

Due to this lack of support, execution of their tests was stripped from them.

In the interim since then, Christophe was kind enough to debug the
actual cause of the breakage and pushed a patch which fixed the test,
so I have restored the execution of tests.

>
> Cheers,
>   Albert

Regards,
Ben

>
>>
>> I am extremely disappointed, that even when pointed towards the commit
>> which broke the test in question that nobody stepped up to fix the
>> issue - especially as there have been many, many commits since that
>> mail. See http://build.kde.org/job/kdepim_master/changes for details
>> on that.
>>
>> This brings into serious consideration whether kdepim is maintained to
>> an adequate level.
>>
>> Regards,
>> Ben Cooksley
>> KDE Sysadmin
>> _______________________________________________
>> release-team mailing list
>> release-team at kde.org
>> https://mail.kde.org/mailman/listinfo/release-team
>