kross unit tests broken

[David Faure]

On Sunday 02 August 2015 18:45:38 Alexander Potashev wrote:
> 2015-08-01 12:57 GMT+03:00 David Faure <faure at kde.org>:
> > Hello Alexander,
> >
> > thanks for your recent commits related to the unit tests in kross.
> >
> > However it seems that they don't pass ;)
> >
> > See https://build.kde.org/job/kross%20master%20kf5-qt5/PLATFORM=Linux,compiler=gcc/10/console
> >
> > I get the same error locally.
> >
> > "Action::setInterpreter: interpreter not found: python"
> >
> > Can you look into it?
> 
> Hi David,
> 
> This is because kross-interpreters[python] is not installed on CI
> server. I had to move these tests into the kross-interpreters repo,
> but didn't do that yet because I'm not sure how to share the autotests
> code between kross.git and kross-interpreters.git repos.

I tried moving all the unittests to kross-interpreters, and that didn't fully fix it:

Test project /d/kde/build/5/kde/kdebindings/kross-interpreters/autotests
    Start 1: krossqtstest-test-es
1/8 Test #1: krossqtstest-test-es .............***Exception: Other  1.99 sec
kross(25424)/default runScriptFile: Execute scriptfile: "/d/kde/src/5/kde/kdebindings/kross-interpreters/autotests/qtstest.es"
kross(25424)/default QScript::functionPrint: 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()]

kross(25424)/default QScript::functionPrint: interpreters=python,qtscript

kross(25424)/default Kross::krossdebug: Kross: "Loading the interpreter library for python"
kross(25424)/default Kross::krossdebug: Kross: "Successfully loaded Interpreter instance from library."
kross(25424)/default Kross::krossdebug: Kross: "PythonScript::Constructor."
kross(25424)/default Kross::krossdebug: Kross: "PythonScript::execute"
kross(25424)/default Kross::krossdebug: Kross: "PythonScript::execute result=None"
kross(25424)/default qt_assert: ASSERT: "i >= 0" in file /d/kde/src/5/frameworks/kross/src/modules/form.cpp, line 392

    Start 2: kross-metafunctiontest
2/8 Test #2: kross-metafunctiontest ...........   Passed    0.04 sec
    Start 3: kross-unittest-es
3/8 Test #3: kross-unittest-es ................   Passed    0.63 sec
    Start 4: kross-guiform-py
4/8 Test #4: kross-guiform-py .................***Exception: Other  0.27 sec
Execute scriptfile /d/kde/src/5/kde/kdebindings/kross-interpreters/autotests/testguiform.py now
krosstest(25429)/default Kross::krossdebug: Kross: "Loading the interpreter library for python"
krosstest(25429)/default Kross::krossdebug: Kross: "Successfully loaded Interpreter instance from library."
krosstest(25429)/default Kross::krossdebug: Kross: "PythonScript::Constructor."
krosstest(25429)/default Kross::krossdebug: Kross: "PythonScript::execute"
krosstest(25429)/default qt_assert: ASSERT: "i >= 0" in file /d/kde/src/5/frameworks/kross/src/modules/form.cpp, line 392

    Start 5: kross-guiqt-py
5/8 Test #5: kross-guiqt-py ...................   Passed    0.25 sec
    Start 6: kross-guitk-py
6/8 Test #6: kross-guitk-py ...................   Passed   15.73 sec
    Start 7: kross-test-py
7/8 Test #7: kross-test-py ....................   Passed    0.30 sec
    Start 8: kross-unittest-py
8/8 Test #8: kross-unittest-py ................   Passed    0.55 sec

75% tests passed, 2 tests failed out of 8

On top of that, kross-guitk-py pops up a window and waits for me to click Exit, which is a big no-no for automated tests
(it shouldn't be in autotests then).

> I think we can disable all the python tests from kross.git.

I'll do that, but please keep working on moving these tests and making them pass ;)

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