CI results for kxmlgui

Ben Cooksley bcooksley at kde.org
Mon Aug 6 10:01:03 BST 2018


On Mon, Aug 6, 2018 at 3:54 AM, David Faure <faure at 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 <faure at kde.org> 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,
>>
>> 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?

>
> --
> David Faure, faure at kde.org, http://www.davidfaure.fr
> Working on KDE Frameworks 5
>
>
>

Cheers,
Ben


More information about the Kde-windows mailing list