Debugging CI test failures

Thomas Friedrichsmeier thomas.friedrichsmeier at
Sun Jun 19 08:58:19 BST 2022

On Sun, 19 Jun 2022 00:44:08 +1200
Ben Cooksley <bcooksley at> wrote:


> Looks like DirectX and it's corresponding components are missing:
> PS C:\> Get-ChildItem -Path C:\ -Recurse -ErrorAction SilentlyContinue
> -Force -Filter ddraw.dll
> PS C:\> Get-ChildItem -Path C:\ -Recurse -ErrorAction SilentlyContinue
> -Force -Filter glu32.dll
> PS C:\> Get-ChildItem -Path C:\ -Recurse -ErrorAction SilentlyContinue
> -Force -Filter MFCaptureEngine.dll
> Looks like to make QtWebEngine work we would need to make some
> changes to our Windows image:
> -
> -

That looks like a bit of a mess, too. What is your (and everybody's)
take on how we should proceed? Are those changes to the image more
trouble than it's worth?

I still have the alternative option to factor out any linkage to
QWebEngine from the testcase. Annoying but possible.

(Is there a way to detect that it's a CI build?)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the kde-devel mailing list