Fwd: Failing Tests in Kross

[Vishesh Handa]

Hey everyone

I managed to contact Sebastian through his kdab email account. I've
attached the response below.

On Fri, Oct 18, 2013 at 3:13 AM, Sebastian Sauer
<sebastian.sauer at kdab.com> wrote:
> On 10/16/2013 03:15 PM, Vishesh Handa wrote:
>>
>> Hey Sebastian
>
>
> Aloha Vishesh :)
>
>
>> If you get some free time could you please have a look at the tests?
>
>
> Unfortunately I don't have a working kf5 setup, there are no packages for my
> distribution and keeping up with kf5 development is near impossible for me
> having a fulltime-job and family.
>
>
>> The following tests FAILED:
>>            1 - kross-guiform-py (Failed)
>>            2 - kross-guiform-rb (Failed)
>>            3 - kross-guiqt-py (Failed)
>>            4 - kross-guiqt-rb (Failed)
>>            5 - kross-guitk-py (Failed)
>>            7 - kross-test-py (Failed)
>
>
> hmmm...
>
>>            8 - kross-unittest-es (SEGFAULT)
>
>
> *.es is QtScript. There may have been some incompatible changes in Qt5.
>
>>            9 - kross-unittest-js (SEGFAULT)
>
>
> *.js is KJS and KjsEmbed. Just delete them. They never got into a quality
> state.
>
>
>>           10 - kross-unittest-py (Failed)
>>           11 - kross-unittest-rb (Failed)
>
>
> Ruby and Python. I saw some weeks ago that Red Hat did some patches to port
> the ruby backend to latest ruby. Not sure who took over Python but there
> where a few patches last years from others.
>
>
>> The test in the qts plugin also segfaults.
>
>
> That's Qt5 QtScript? hmpf :(
>
>
>> The python and ruby tests fail
>> because of the missing kross plugin.
>
>
> Those are the only two important backends.
>
>
>> However the js/es ones seem to segault.
>
>
> Delete it (the test and kjs-backend in kross) and also delete kjsembed from
> kdelibs. iirc I was official(?) maintainer of all of that :) Rich Moore, who
> pushed it to kdelibs back then, suggested deletion at the kjsembed
> mailinglist some years ago, then Matt Bratstone and me took over and I think
> I am the only one left.
>
>
>> Do you think you could have a look at them? I'm not comfortable moving it
>> to
>> tier3 with failing tests.
>
>
> Unfortunately I have no time and while I hack a lot on Qt its 99% Qt4
> related. So, even my Qt5 setup is outdated already (for kf5 which iirc
> requires latest/greatest Qt 5.2) and so is my cmake, cmakeextras, all
> dependencies, etc. kf5 moves to fast if you only have 1h/week so I decided
> to better spend my time on Calligra.
>
>
>> There also seems to be a .ui file in the tests directory, which I'm not
>> sure
>> how to run.
>
>
> Those are not for run as in auto-tests but are manual tests used in the
> kross-gui* scripts (which are not auto-tests as in unittests too but
> manual-tests as in start a GUI for clicking and testing manually).
>
>
>> When Kross moves to its own git repo we should probably move the ruby and
>> python plugin in it as well.
>
>
> Makes sense.
>
>
>> Also, can I add a MAINTAINERS file with your name in it?
>
>
> I don't think I will have enough time anytime soon. Probably once there are
> kf5 packages or once kross can be build standalone without kf5 dependencies
> (it used to be that way, means tear1, when I hacked last on it).
>
> --
> Best regards
>
> Sebastian Sauer | sebastian.sauer at kdab.com | Software Engineer
> KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
> Germany: +49-30-521325470, Sweden (HQ): +46-563-540090
> KDAB - Qt Experts - Platform-independent software solutions



-- 
Vishesh Handa