Failing builds on the CI system

[Ben Cooksley]

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

[Gilles Caulier-4]

Le sam. 28 nov. 2020 à 03:42, Ben Cooksley <[hidden email]> a écrit :

>
> 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.

Hi Ben,

No, it's not a problem with the OpenCV version 2 headers. It's a
problem about missing Opencv ML modules on the CI (Machine Learning).

https://docs.opencv.org/master/dc/dd6/ml_intro.html

All OpenCV headers (including V3 and V4) go to opencv2 subdirectory
for compatibility purpose. digiKam is compatible is opencv v3 and v4.

Few months ago, ML module was available on the CI and all compiles
fine under MSVC. Now it disappeared, probably somebody did not judge
this module mandatory on the build systemm. No chance, digiKam uses it
for the famous face recognition feature....

Best regards

Gilles Caulier

[Milian Wolff]

On Samstag, 28. November 2020 03:42:21 CET Ben Cooksley wrote:

> 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:

<snip>

> - KDevelop's Python Support: Appears to be broken due to SIC changes in
> KDevelop itself
> - KDevelop XDebug Support: Same as the Python support

Both fixed now, sorry for the delay.

> - KDevelop: Appears to be performing an operation that is not permitted on
> Windows in public interfaces

We are on it, any help is welcome. See:

https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/181#note_136733
https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/194#note_136805

We will probably de-inline the corresponding functions in Windows to unbreak
this for now...

--
Milian Wolff
[hidden email]
http://milianw.de

[Laurent Montel]

> - Akonadi's Contacts Support: Now requires libkleo, yet that has
> dependencies which aren't available on Windows at the moment (unless this
> has changed)

It builds from several weeks on windows (as other pim*)

Regards.

[Ben Cooksley]

On Sun, Nov 29, 2020 at 9:07 AM Laurent Montel <[hidden email]> wrote:

> - Akonadi's Contacts Support: Now requires libkleo, yet that has
> dependencies which aren't available on Windows at the moment (unless this
> has changed)

It builds from several weeks on windows (as other pim*)

You'll need to file a ticket to request gpgme be added to the Windows (MSVC) platform, and that the blacklisting of libkleo on Windows be reversed.

Please note that this is an invasive change as it has been several months since the platform was last changed so it may take a few days to action.

Regards.

Cheers,

Ben

[Ben Cooksley]

On Sun, Nov 29, 2020 at 8:22 AM Milian Wolff <[hidden email]> wrote:

On Samstag, 28. November 2020 03:42:21 CET Ben Cooksley wrote:
> 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:

<snip>

> - KDevelop's Python Support: Appears to be broken due to SIC changes in
> KDevelop itself
> - KDevelop XDebug Support: Same as the Python support

Both fixed now, sorry for the delay.

> - KDevelop: Appears to be performing an operation that is not permitted on
> Windows in public interfaces

We are on it, any help is welcome. See:

https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/181#note_136733
https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/194#note_136805

We will probably de-inline the corresponding functions in Windows to unbreak
this for now...

Thanks for looking into these and resolving the other issues - it's appreciated!

 

--
Milian Wolff
[hidden email]
http://milianw.de

Cheers,

Ben