Proposal: drop Salsa CI testing for now

Pino Toscano pino at debian.org
Sun Aug 29 07:37:00 BST 2021


Hi Norbert,

first of all, I just noticed this after you started to disable the
salsa CI almost everywhere; this email was sent to the wrong discussion
list, and thus it got buried in the usual flood of upload/bug emails.

In data mercoledì 18 agosto 2021 08:21:49 CEST, Norbert Preining ha scritto:
> I would like to collect opinions concerning Salsa CI testing:

Sure.

> I contemplate disabling the whole salsa-ci for now, since all tests
> always fail,

No, all tests do not "always fail".

What is usually failing is the blhc test, due to blhc mistaking the
cmake automoc commands as build commands. There is a semi-long story
about this, which is a different discussion topic than this. To make
it short, it can be easily disabled for the affected projects (i.e.
only those using qt5+cmake, qt5+qmake is not affected) using the
following variable in the yaml file:
<<<<<
variables:
  SALSA_CI_DISABLE_BLHC: 'no'
>>>>>

Every other test is perfectly valid and working. Even better, they
actually showed issues in your recent uploads that would have been
nice to first *before* the upload, rather than afterwards; for example
https://salsa.debian.org/qt-kde-team/kde/cantor/-/jobs/1833161
i.e. cantor being unbuildable because of an unsatified build dependency
(old libqalculate). There are similar cases also for failed autopkgtest
that I fixed after.

There are possible failures due to another kde package being not
available yet in the archive; I think the various plasma package use a
custom repository for it, which should do the job. If it does not, let's
look into it.

> and we only take a lot of computing power for tests
> that nobody looks into, and hundreds of emails.

Well, if you don't care about it, that isn't the same as saying it is
not useful. It only means that, well, you don't care about it.

> I have no intention to fix the salsa-ci stuff, so I would like to
> disable it.
> 
> If someone wants to work on getting the CI testing working again, we can
> reenable it again.

I mentioned above the way to avoid getting rid of the majority of the
"issues". Hence, please re-enable the salsa CI, which *is* useful even
if you don't care about it.

Thanks,
-- 
Pino Toscano
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-kde-talk/attachments/20210829/78c49f14/attachment.sig>


More information about the pkg-kde-talk mailing list