Re: CI results for kxmlgui

2018-08-19 Thread David Faure
On samedi 18 août 2018 19:07:20 CEST Ben Cooksley wrote: > I debugged this directly on the CI servers and once I had DebugView > running with Admin privileges that showed the output from the test. > As it turns out Qt 5.11 introduced the variable above, so for older > versions we need to set QT_LOG

Re: CI results for kxmlgui

2018-08-18 Thread Ben Cooksley
On Sun, Aug 19, 2018 at 1:15 AM David Faure wrote: > > On jeudi 16 août 2018 15:01:18 CEST Ben Cooksley wrote: > > On Sat, Aug 11, 2018 at 3:22 AM Hannah von Reth wrote: > > > Hi David, > > > > Hi Hannah, > > > > > To see whats going on I was running the tests with > > > https://github.com/TheOne

Re: CI results for kxmlgui

2018-08-18 Thread David Faure
On jeudi 16 août 2018 15:01:18 CEST Ben Cooksley wrote: > On Sat, Aug 11, 2018 at 3:22 AM Hannah von Reth wrote: > > Hi David, > > Hi Hannah, > > > To see whats going on I was running the tests with > > https://github.com/TheOneRing/vsd . > > > > It turns out those are gui applications so Qt wr

Re: CI results for kxmlgui

2018-08-16 Thread Ben Cooksley
On Sat, Aug 11, 2018 at 3:22 AM Hannah von Reth wrote: > > Hi David, Hi Hannah, > > To see whats going on I was running the tests with > https://github.com/TheOneRing/vsd . > > It turns out those are gui applications so Qt writes to the debug > stream, not stdout. > > Setting QT_FORCE_STDERR_LOG

Re: CI results for kxmlgui

2018-08-10 Thread Hannah von Reth
Hi David, To see whats going on I was running the tests with https://github.com/TheOneRing/vsd . It turns out those are gui applications so Qt writes to the debug stream, not stdout. Setting QT_FORCE_STDERR_LOGGING=1 fixes this issue, I'd suggest to set it automatically in ecm? Cheers, Hannah

Re: CI results for kxmlgui

2018-08-10 Thread David Faure
On lundi 6 août 2018 11:01:03 CEST Ben Cooksley wrote: > On Mon, Aug 6, 2018 at 3:54 AM, David Faure wrote: > > On dimanche 5 août 2018 02:01:39 CEST Ben Cooksley wrote: > >> On Sat, Aug 4, 2018 at 10:49 AM, David Faure wrote: > >> > Why is there no output from kxmlgui_unittest in > >> > https://

Re: CI results for kxmlgui

2018-08-06 Thread Ben Cooksley
On Mon, Aug 6, 2018 at 3:54 AM, David Faure wrote: > On dimanche 5 août 2018 02:01:39 CEST Ben Cooksley wrote: >> On Sat, Aug 4, 2018 at 10:49 AM, David Faure wrote: >> > Why is there no output from kxmlgui_unittest in >> > https://build.kde.org/view/Frameworks/job/Frameworks%20kxmlgui%20kf5-qt5%

Re: CI results for kxmlgui

2018-08-05 Thread David Faure
On dimanche 5 août 2018 02:01:39 CEST Ben Cooksley wrote: > On Sat, Aug 4, 2018 at 10:49 AM, David Faure wrote: > > Why is there no output from kxmlgui_unittest in > > https://build.kde.org/view/Frameworks/job/Frameworks%20kxmlgui%20kf5-qt5%2 > > 0WindowsMSVCQt5.10/21/console ? > > Hi David, > >

Re: CI results for kxmlgui

2018-08-04 Thread Ben Cooksley
On Sat, Aug 4, 2018 at 10:49 AM, David Faure wrote: > Why is there no output from kxmlgui_unittest in > https://build.kde.org/view/Frameworks/job/Frameworks%20kxmlgui%20kf5-qt5%20WindowsMSVCQt5.10/21/console > ? Hi David, I'm not sure why there isn't any output unfortunately. Can you give some b

CI results for kxmlgui

2018-08-03 Thread David Faure
Why is there no output from kxmlgui_unittest in https://build.kde.org/view/Frameworks/job/Frameworks%20kxmlgui%20kf5-qt5%20WindowsMSVCQt5.10/21/console ? -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5