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

List:       kde-devel
Subject:    Failing builds on the CI system
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2020-11-28 2:42:21
Message-ID: CA+XidOHypB88==Hf928Hc6-OM546BMCCmP7UEAiH9NNX1Lfw8g () mail ! gmail ! com
[Download RAW message or body]

Hi all,

Yesterday evening a number of projects had their jobs on the CI system
regenerated, as part of Frameworks moving off Qt 5.12 and on to a minimum
build of Qt 5.14.

In keeping with prior precedence, this means that Applications and all
other builds then move on to the currently supported mainstream version of
Qt, which at the moment is Qt 5.15.

While the Dependency Builds did mostly complete without issue, as part of
this a number of long running failures were noted, which it would be nice
if people could please correct. In no particular order:

- Digikam: Appears to be trying to use headers from OpenCV 2, while the
Windows CI nodes have OpenCV 4.
- KIO Extras: Appears to make use of Unix specific constants that do not
exist on Windows
- KDevelop's Python Support: Appears to be broken due to SIC changes in
KDevelop itself
- KDevelop XDebug Support: Same as the Python support
- KDevelop: Appears to be performing an operation that is not permitted on
Windows in public interfaces
- Akonadi's Contacts Support: Now requires libkleo, yet that has
dependencies which aren't available on Windows at the moment (unless this
has changed)

Logs and other related build artifacts can be found at
https://build.kde.org/view/Failing/

Thanks,
Ben

[Attachment #3 (text/html)]

<div dir="ltr">Hi all,<div><br></div><div>Yesterday evening a number  of projects had \
their jobs on the CI system regenerated, as part of Frameworks moving off Qt 5.12 and \
on to a minimum build of Qt 5.14.  </div><div><br></div><div>In keeping with prior \
precedence, this means that Applications and all other builds then move on to the \
currently supported mainstream version of Qt, which at the moment is Qt \
5.15.</div><div><br></div><div>While the Dependency Builds did mostly complete \
without issue, as part of this a number of long running failures were noted, which it \
would be nice if people could please correct. In no particular \
order:</div><div><br></div><div>- Digikam: Appears to be trying to use headers from \
OpenCV 2, while the Windows CI nodes have OpenCV 4.</div><div>- KIO Extras: Appears \
to make use of Unix specific constants that do not exist on Windows</div><div>- \
KDevelop&#39;s  Python Support: Appears to be broken due to SIC changes in KDevelop \
itself</div><div>- KDevelop XDebug Support: Same as the Python support</div><div>- \
KDevelop: Appears to be performing an operation that is not permitted on Windows in \
public interfaces</div><div>- Akonadi&#39;s  Contacts Support: Now requires libkleo, \
yet that has dependencies which aren&#39;t available on Windows at the moment (unless \
this has changed)</div><div><br></div><div>Logs and other related build artifacts can \
be found at  <a href="https://build.kde.org/view/Failing/">https://build.kde.org/view/Failing/</a></div><div><br></div><div>Thanks,</div><div>Ben</div></div>




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

Configure | About | News | Add a list | Sponsored by KoreLogic