Your test calls python which only works on Linux Reproducible: Always Expected Results: Passing test
=== OS X testing log === Execute scriptfile: "/Users/jenkins/builds/kross/kf5-qt5/autotests/qtstest.es" Kross::Manager(name = "Kross") [objectName,destroyed(QObject*),destroyed(),objectNameChanged(QString),deleteLater(),started(Kross::Action*),finished(Kross::Action*),interpreters(),hasAction(QString),action(QString),module(QString),deleteModules(),executeScriptFile(QUrl),executeScriptFile(),addQObject(QObject*,QString),addQObject(QObject*),qobject(QString),qobjectNames()] interpreters=qtscript Kross: "Action::setInterpreter: interpreter not found: python" Kross: "No such interpreter 'python'" Kross: "Error error=No such interpreter "python" lineno=-1 trace= " ASSERT: "i >= 0" in file /Users/jenkins/builds/kross/kf5-qt5/src/modules/form.cpp, line 392
So, what can be done to test what is going on here? The OSX builders on KDE's new CI system offer MacPorts' both Python versions 2.7.9 and 3.4.3 - on top of the system's Python 2.7.5. BTW, "which python" reports "/usr/bin/python" on the builders.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
kross was already in pure maintenance mode in kf5, for kf6 it got removed, there will be no future work spend on this beside critical security issues, if at all.