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 On 10/08/2018 17:04, David Faure wrote: > On lundi 6 août 2018 11:01:03 CEST Ben Cooksley wrote: >> On Mon, Aug 6, 2018 at 3:54 AM, David Faure <fa...@kde.org> 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 <fa...@kde.org> wrote: >>>>> Why is there no output from kxmlgui_unittest in >>>>> https://build.kde.org/view/Frameworks/job/Frameworks%20kxmlgui%20kf5-qt >>>>> 5%2 >>>>> 0WindowsMSVCQt5.10/21/console ? >>>> Hi David, >>>> >>>> I'm not sure why there isn't any output unfortunately. >>>> Can you give some background as to what this test does so we can take >>>> a closer look at what might be causing this behaviour? >>> Nothing out of the ordinary (parsing XML, creating menus and toolbars, >>> etc.) I don't think it's related to what it's doing, I think it's the >>> fact that it fails but the CI -- or ctest -- doesn't capture its output. >>> >>> It's almost like CTEST_OUTPUT_ON_FAILURE isn't set to 1? >> Unfortunately it is set :( >> >> https://cgit.kde.org/sysadmin/ci-tooling.git/tree/helpers/run-tests.py#n81 >> >> I wonder if the test could potentially be crashing, I fear this will >> require actual debugging on the CI node to confirm though.. >> Any other ideas before we look into direct debugging? > I'm getting the same problem in KRunner... > > https://build.kde.org/view/Frameworks/job/Frameworks%20krunner%20kf5-qt5%20WindowsMSVCQt5.10/24/consoleFull > > Strangely enough, it works for other jobs: > > https://build.kde.org/view/Frameworks/job/Frameworks%20kservice%20kf5-qt5%20WindowsMSVCQt5.10/34/consoleFull >
