CI seems to be frozen again. :(

yea - feel free to commit any changes related to this yourself if you want.

I manage to build the docker kdeorg/ci-suse-qt59 image - and of course the tests pass - so I'm not sure how to help now. I've already disabled this test again to avoid the sysadmins having more work to do.

When you did your reproduction attempt @hindenburg did you use the binaries the CI system itself uses, or did you build Frameworks, etc yourself?

In D16919#364587, @bcooksley wrote:

When you did your reproduction attempt @hindenburg did you use the binaries the CI system itself uses, or did you build Frameworks, etc yourself?

I used the script in the comments by knauss in https://phabricator.kde.org/T3689 which I thought is what the CI uses. If there's other instructions, let me know.

Yes, that is basically what the CI does so should be a pretty good method of reproducing it's results.
Did you run "make tests" / "ctest" or did you use the run-tests.py script to execute the unit tests?

In D16919#364934, @bcooksley wrote:

Yes, that is basically what the CI does so should be a pretty good method of reproducing it's results.
Did you run "make tests" / "ctest" or did you use the run-tests.py script to execute the unit tests?

The python test script

Okay, that is odd.

I'll try reproducing the issue on the CI nodes in the next day or so - you changed 'kcalcore' in that example to 'konsole' I assume?

Yes, I was actually surprised I managed to get it all to run. Are there official docs on how to setup an ci image and run applications? If not, it would be helpful.

The best we have documentation wise is https://phabricator.kde.org/w/continuous-integration/ however these are quite out of date (and incomplete).