Re: Upcoming reorganisation of the CI system

2018-08-21 Thread Morten Volden
Hi Ben

I don't know if this is on you radar or not, but here goes.

I have noticed that quite a few of the KDevelop unittests are failing on
the Windows CI.

Running the tests locally they work fine.

If I look at the output of the failing tests it is similar to that pasted
below.

Searching brought me to this page:

https://stackoverflow.com/questions/43897167/does-qt-build-with-opengl-angle-fix-support-for-windows-clients-not-having-openg/43932575#43932575

Which seem to suggest that (re) install DirectX End-User Runtimes (June
2010) .should
fix the issues.

Since people will be giving the servers some TLC in the near future I
thought it might be worth looking at.

Kind Regards

Morten


qt.qpa.input.tablet: Tablet support:  "None"
qt.qpa.windows: QWindowsContext::setProcessDpiAwareness 2
SetProcessDpiAwareness(2) failed: COM error 0x80070005
E_ACCESSDENIED (Unknown error 0x080070005), using 2
qt.qpa.windows: QWindowsIntegrationPrivate::QWindowsIntegrationPrivate
DpiAwareness= 2 effective process DPI awareness= 2
qt.qpa.windows: QWindowsContext::registerWindowClass "Qt5ClipboardView"
style=0x0 brush=0x0 icon=false atom=49400
qt.qpa.mime: QWindowsClipboard::registerViewer m_clipboardViewer: 0xede04e8
format listener: true next: 0x0
qt.qpa.windows: New Monitor:  Screen "WinDisc" 1024x768+0+0 avail:
1024x768+0+0 physical: -1x-1 DPI: 96x96 Depth: 32 Format: 6 hMonitor:
0x10001 primary virtual desktop lock screen
qt.qpa.fonts: QWindowsFontDatabase::systemDefaultFont QFont( "MS Shell Dlg
2,8.25,-1,5,50,0,0,0,0,0" )
qt.qpa.windows: QWindowsTheme::refreshIconPixmapSizes (QSize(16, 16),
QSize(32, 32), QSize(48, 48), QSize(256, 256))
qt.qpa.gl: QWindowsIntegration::createPlatformOpenGLContext
QSurfaceFormat(version 2.0, options QFlags(),
depthBufferSize -1, redBufferSize -1, greenBufferSize -1, blueBufferSize
-1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior
QSurfaceFormat::SwapBehavior(DefaultSwapBehavior), swapInterval 1,
colorSpace QSurfaceFormat::ColorSpace(DefaultColorSpace), profile
QSurfaceFormat::OpenGLContextProfile(NoProfile))
qt.qpa.gl: Basic wglCreateContext gives version 1.1
qt.qpa.gl: OpenGL version too low
qt.qpa.gl: OpenGL 2.0 entry points not found
qt.qpa.gl: GPU features: QSet("disable_d3d11", "disable_desktopgl",
"disable_d3d9")
qt.qpa.gl: Disabling Desktop GL:  GpuDescription(vendorId=0x0,
deviceId=0x0, subSysId=0x0, revision=0, driver: "", version=, "")
qt.qpa.gl: Disabling D3D11:  GpuDescription(vendorId=0x0, deviceId=0x0,
subSysId=0x0, revision=0, driver: "", version=, "")
qt.qpa.gl: Disabling D3D9:  GpuDescription(vendorId=0x0, deviceId=0x0,
subSysId=0x0, revision=0, driver: "", version=, "")
qt.qpa.gl: QWindowsOpenGLTester::supportedRenderers
GpuDescription(vendorId=0x0, deviceId=0x0, subSysId=0x0, revision=0,
driver: "", version=, "") renderer:  QFlags(0x8|0x20)
qt.qpa.gl: Qt: Using EGL from libEGLd
qt.qpa.gl: Qt: Using OpenGL ES 2.0 from libGLESv2d
qt.qpa.gl: QWindowsEGLStaticContext::create Created EGL display
0x1e5631fcd80 v 1 . 4




Den tir. 21. aug. 2018 kl. 17.27 skrev Ben Cooksley :

> Hi all,
>
> Final call for objections or queries for this change - i'll be looking
> to roll this out this weekend.
>
> Note: Plasma and KDevelop, i'm not subscribed to your lists so please
> ensure i'm in CC for any responses.
>
> Cheers,
> Ben
>


-- 
Regards / Med venlig hilsen

Morten Danielsen Volden
Software Developer
M.Sc. EE


Re: Upcoming reorganisation of the CI system

2018-08-21 Thread Ben Cooksley
On Wed, Aug 22, 2018 at 2:36 AM Morten Volden  wrote:
>
> Hi Ben

Hi Morten,

>
> I don't know if this is on you radar or not, but here goes.
>
> I have noticed that quite a few of the KDevelop unittests are failing on the 
> Windows CI.
>
> Running the tests locally they work fine.
>
> If I look at the output of the failing tests it is similar to that pasted 
> below.
>
> Searching brought me to this page:
>
> https://stackoverflow.com/questions/43897167/does-qt-build-with-opengl-angle-fix-support-for-windows-clients-not-having-openg/43932575#43932575
>
> Which seem to suggest that (re) install DirectX End-User Runtimes (June 
> 2010).should fix the issues.
>
> Since people will be giving the servers some TLC in the near future I thought 
> it might be worth looking at.

I suspect in this instance the problem may be caused by the KVM QXL
drivers that we're reliant on to serve as the system graphics.
Any ideas as to whether this might be the case or not?

As part of the system setup we have to install the DirectX SDK for
some components so I would have expected that it took care of
installing all the necessary runtime components as well.

>
> Kind Regards
>
> Morten

Cheers,
Ben

>
>
> qt.qpa.input.tablet: Tablet support:  "None"
> qt.qpa.windows: QWindowsContext::setProcessDpiAwareness 2
> SetProcessDpiAwareness(2) failed: COM error 0x80070005 E_ACCESSDENIED 
> (Unknown error 0x080070005), using 2
> qt.qpa.windows: QWindowsIntegrationPrivate::QWindowsIntegrationPrivate 
> DpiAwareness= 2 effective process DPI awareness= 2
> qt.qpa.windows: QWindowsContext::registerWindowClass "Qt5ClipboardView" 
> style=0x0 brush=0x0 icon=false atom=49400
> qt.qpa.mime: QWindowsClipboard::registerViewer m_clipboardViewer: 0xede04e8 
> format listener: true next: 0x0
> qt.qpa.windows: New Monitor:  Screen "WinDisc" 1024x768+0+0 avail: 
> 1024x768+0+0 physical: -1x-1 DPI: 96x96 Depth: 32 Format: 6 hMonitor: 0x10001 
> primary virtual desktop lock screen
> qt.qpa.fonts: QWindowsFontDatabase::systemDefaultFont QFont( "MS Shell Dlg 
> 2,8.25,-1,5,50,0,0,0,0,0" )
> qt.qpa.windows: QWindowsTheme::refreshIconPixmapSizes (QSize(16, 16), 
> QSize(32, 32), QSize(48, 48), QSize(256, 256))
> qt.qpa.gl: QWindowsIntegration::createPlatformOpenGLContext 
> QSurfaceFormat(version 2.0, options QFlags(), 
> depthBufferSize -1, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, 
> alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior 
> QSurfaceFormat::SwapBehavior(DefaultSwapBehavior), swapInterval 1, colorSpace 
> QSurfaceFormat::ColorSpace(DefaultColorSpace), profile  
> QSurfaceFormat::OpenGLContextProfile(NoProfile))
> qt.qpa.gl: Basic wglCreateContext gives version 1.1
> qt.qpa.gl: OpenGL version too low
> qt.qpa.gl: OpenGL 2.0 entry points not found
> qt.qpa.gl: GPU features: QSet("disable_d3d11", "disable_desktopgl", 
> "disable_d3d9")
> qt.qpa.gl: Disabling Desktop GL:  GpuDescription(vendorId=0x0, deviceId=0x0, 
> subSysId=0x0, revision=0, driver: "", version=, "")
> qt.qpa.gl: Disabling D3D11:  GpuDescription(vendorId=0x0, deviceId=0x0, 
> subSysId=0x0, revision=0, driver: "", version=, "")
> qt.qpa.gl: Disabling D3D9:  GpuDescription(vendorId=0x0, deviceId=0x0, 
> subSysId=0x0, revision=0, driver: "", version=, "")
> qt.qpa.gl: QWindowsOpenGLTester::supportedRenderers 
> GpuDescription(vendorId=0x0, deviceId=0x0, subSysId=0x0, revision=0, driver: 
> "", version=, "") renderer:  QFlags(0x8|0x20)
> qt.qpa.gl: Qt: Using EGL from libEGLd
> qt.qpa.gl: Qt: Using OpenGL ES 2.0 from libGLESv2d
> qt.qpa.gl: QWindowsEGLStaticContext::create Created EGL display 0x1e5631fcd80 
> v 1 . 4
>
>
>
>
> Den tir. 21. aug. 2018 kl. 17.27 skrev Ben Cooksley :
>>
>> Hi all,
>>
>> Final call for objections or queries for this change - i'll be looking
>> to roll this out this weekend.
>>
>> Note: Plasma and KDevelop, i'm not subscribed to your lists so please
>> ensure i'm in CC for any responses.
>>
>> Cheers,
>> Ben
>
>
>
> --
> Regards / Med venlig hilsen
>
> Morten Danielsen Volden
> Software Developer
> M.Sc. EE


Re: Upcoming reorganisation of the CI system

2018-08-21 Thread Ben Cooksley
Hi all,

Final call for objections or queries for this change - i'll be looking
to roll this out this weekend.

Note: Plasma and KDevelop, i'm not subscribed to your lists so please
ensure i'm in CC for any responses.

Cheers,
Ben


Re: Upcoming reorganisation of the CI system

2018-08-14 Thread Ben Cooksley
On Tue, 14 Aug 2018, 17:09 Christoph Feck,  wrote:

> On 14.08.2018 15:03, Ben Cooksley wrote:
> > Currently CI jobs are all created within a flat namespace, meaning
> > that it is quite difficult to view the overall status of an individual
> > project. Additionally, it creates the issue that the main default view
> > can take a significant amount of time to load.
> >
> > To resolve this we intend to shift everything within Folders in
> > Jenkins. These folders will be structured in the form of Product /
> > Project / 
>
> Will we still be able to see the status of all Applications (or all
> Frameworks) without clicking hundreds of subfolders? This is useful to
> get an overview before doing releases.
>

Yes, with a recursive view this will still be possible - it just won't be
the default landing page.


> Christoph Feck
>

Cheers,
Ben

>


Re: Upcoming reorganisation of the CI system

2018-08-14 Thread Christoph Feck

On 14.08.2018 15:03, Ben Cooksley wrote:

Currently CI jobs are all created within a flat namespace, meaning
that it is quite difficult to view the overall status of an individual
project. Additionally, it creates the issue that the main default view
can take a significant amount of time to load.

To resolve this we intend to shift everything within Folders in
Jenkins. These folders will be structured in the form of Product /
Project / 


Will we still be able to see the status of all Applications (or all 
Frameworks) without clicking hundreds of subfolders? This is useful to 
get an overview before doing releases.


Christoph Feck


Re: Upcoming reorganisation of the CI system

2018-08-14 Thread David Faure
On mardi 14 août 2018 15:03:42 CEST Ben Cooksley wrote:
> Hi all,
> 
> Currently CI jobs are all created within a flat namespace, meaning
> that it is quite difficult to view the overall status of an individual
> project. Additionally, it creates the issue that the main default view
> can take a significant amount of time to load.
> 
> To resolve this we intend to shift everything within Folders in
> Jenkins. These folders will be structured in the form of Product /
> Project / 

Very nice!

-- 
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5





Upcoming reorganisation of the CI system

2018-08-14 Thread Ben Cooksley
Hi all,

Currently CI jobs are all created within a flat namespace, meaning
that it is quite difficult to view the overall status of an individual
project. Additionally, it creates the issue that the main default view
can take a significant amount of time to load.

To resolve this we intend to shift everything within Folders in
Jenkins. These folders will be structured in the form of Product /
Project / 

If this creates issues for anyone, or if anyone has any questions
regarding this, please let me know.

At this stage it is intended that we will keep all build history for
jobs on the system (although downtime will be needed in order to allow
for the changeover).

Thanks,
Ben Cooksley
KDE Sysadmin