[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    CI Outage
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2023-02-17 7:32:47
Message-ID: CA+XidOHvz-tZUENftcTDyzx8yt5xrFnbp_bbRJGovuEYB4-Eig () mail ! gmail ! com
[Download RAW message or body]

Hi all,

As many of you will have noticed, the Linux side of our Gitlab CI setup,
including those runs for Android and other miscellaneous jobs (such as
cppcheck) were all KO yesterday due to a Docker error.

This has now been corrected, and was due to a defect in an update shipped
by the Docker upstream maintainers. They added a hard dependency on an
Apparmor CLI tool, however failed to add the corresponding dependency to
their packages (and to top matters off, part of that package is kernel side
and only does it's initialisation on system boot...)

The nodes have now had their setups corrected and have been rebooted, and
everything is back in service. I have also kicked off builds of just about
everything that is failing on the CI system.

Apologies for the disruption here.

While doing so I noticed a fairly sad number of actual
failures-to-build-from-source:
- Mandatory X11 dependency on Windows:
https://invent.kde.org/utilities/keditbookmarks
- Blind KF6 porting: https://invent.kde.org/pim/kontact/-/jobs/786385
- (and others yet to finish working their way through)

It also looks like we have some packages that are not being rebuilt by seed
jobs (see https://invent.kde.org/pim/kalendar/-/jobs/786366), so once the
system has finished playing catch up we may need to do some additional
infrastructure work there.

Please contact me if you'd like to assist with that.

Thanks,
Ben

[Attachment #3 (text/html)]

<div dir="ltr">Hi all,<div><br></div><div>As many of you will have noticed, the Linux \
side of our Gitlab CI setup, including those runs for Android and other miscellaneous \
jobs (such as cppcheck) were all KO yesterday due to a Docker \
error.</div><div><br></div><div>This has now been corrected, and was due to a defect \
in an update shipped by the Docker upstream maintainers. They added a hard dependency \
on an Apparmor CLI tool, however failed to add the corresponding dependency to their \
packages (and to top matters off, part of that package is kernel side and only does \
it&#39;s initialisation on system boot...)</div><div><br></div><div>The nodes have \
now had their setups corrected and have been rebooted, and everything is back in \
service. I have also kicked off builds of just about everything that is failing on \
the CI system.</div><div><br></div><div>Apologies for the disruption \
here.</div><div><br></div><div>While doing so I noticed a fairly sad number of actual \
failures-to-build-from-source:</div><div>- Mandatory X11 dependency on Windows:  <a \
href="https://invent.kde.org/utilities/keditbookmarks">https://invent.kde.org/utilities/keditbookmarks</a></div><div>- \
Blind KF6 porting:  <a \
href="https://invent.kde.org/pim/kontact/-/jobs/786385">https://invent.kde.org/pim/kontact/-/jobs/786385</a></div><div>- \
(and others yet to finish working their way through)</div><div><br></div><div>It also \
looks like we have some packages that are not being rebuilt by seed jobs (see <a \
href="https://invent.kde.org/pim/kalendar/-/jobs/786366">https://invent.kde.org/pim/kalendar/-/jobs/786366</a>), \
so once the system has finished playing catch up we may need to do some additional \
infrastructure work there.</div><div><br></div><div>Please contact me if you&#39;d \
like to assist with that.</div><div><br></div><div>Thanks,</div><div>Ben</div></div>



[prev in list] [next in list] [prev in thread] [next in thread]