Re: Test failures with krunner 5.39.0

[David Faure]

On mercredi 1 novembre 2017 16:37:30 EET Hartmut Goebel wrote:
> Hallo,
> 
> I'm packaging krunner 5.39.0 for GNU Guix [1]. GNU Guix builds all
> software in an isolated environment (a container), which includes only
> the packages and tools specified explicitly.
> 
> When running the tests, dbusrunnertest faills, with this notable warning
> and the error show below:
> 
>DBusRunnerTest::testMatch() org.kde.krunner: Invalid entry: "DBus
> runner test"
> 
> Any idea what may be missing, what needs to be set up (env-var,
> directory, package, paths)? Any idea hos to debug this further?
> 
> All required packages and all optional/feature packages (except of QCH)
> are installed. I tried running the tests with both dbus-launch and
> without. The external program "testremoterunner" gets started. strace -e
> trace=file" shows nothing relevant (as far as I can tell).
> 
> * Start testing of DBusRunnerTest *
> Config: Using QtTest library 5.9.2, Qt 5.9.2 (x86_64-little_endian-lp64
> shared (dynamic) release build; by GCC 5.4.0)
> PASS   : DBusRunnerTest::initTestCase()
> QWARN  : DBusRunnerTest::testMatch() inotify_add_watch("/etc/mtab")
> failed: "No such file or directory"
> QWARN  : DBusRunnerTest::testMatch() inotify_add_watch("/etc/fstab")
> failed: "No such file or directory"
> QWARN  : DBusRunnerTest::testMatch() org.kde.krunner: Invalid entry:
> "DBus runner test"

I've been debugging this today too (just saw this email now).

It works after "make install", right?
The issue is that when the servicetype isn't installed, the sycoca indexing 
doesn't contain the necessary properties.

The real long term solution would be to port this from KServiceTypeTrader 
(i.e. desktop files) to KPluginMetadata (i.e. plugins with json).
But of course keeping compatibility with desktop file based runners.

I'm doing exactly this for emoticon themes right now, if that works we can 
look at doing the same here.

I saw weird things in gdb while trying to debug this, so I'm only 99% sure of 
my diagnostic, but what's for sure is that it works for me after make install
(into a path whose /share subdir is in $XDG_DATA_DIRS, of course),
and that I can see how the missing servicetype is a huge problem anyway.

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

Re: Test failures with krunner 5.39.0

[David Edmundson]

If the external process gets started then it is indeed weird.

Dbus-monitor (or bustle) will be the best tools here, they'll show the
traffic between the test and test helper.

On 1 Nov 2017 23:18, "Hartmut Goebel"  wrote:

> Hallo,
>
> I'm packaging krunner 5.39.0 for GNU Guix [1]. GNU Guix builds all
> software in an isolated environment (a container), which includes only
> the packages and tools specified explicitly.
>
> When running the tests, dbusrunnertest faills, with this notable warning
> and the error show below:
>
>DBusRunnerTest::testMatch() org.kde.krunner: Invalid entry: "DBus
> runner test"
>
> Any idea what may be missing, what needs to be set up (env-var,
> directory, package, paths)? Any idea hos to debug this further?
>
> All required packages and all optional/feature packages (except of QCH)
> are installed. I tried running the tests with both dbus-launch and
> without. The external program "testremoterunner" gets started. strace -e
> trace=file" shows nothing relevant (as far as I can tell).
>
> * Start testing of DBusRunnerTest *
> Config: Using QtTest library 5.9.2, Qt 5.9.2 (x86_64-little_endian-lp64
> shared (dynamic) release build; by GCC 5.4.0)
> PASS   : DBusRunnerTest::initTestCase()
> QWARN  : DBusRunnerTest::testMatch() inotify_add_watch("/etc/mtab")
> failed: "No such file or directory"
> QWARN  : DBusRunnerTest::testMatch() inotify_add_watch("/etc/fstab")
> failed: "No such file or directory"
> QWARN  : DBusRunnerTest::testMatch() org.kde.krunner: Invalid entry:
> "DBus runner test"
> FAIL!  : DBusRunnerTest::testMatch() 'spy.wait()' returned FALSE. ()
>Loc:
> [/tmp/guix-build-krunner-5.39.0.drv-0/krunner-5.39.0/autotes
> ts/dbusrunnertest.cpp(82)]
> PASS   : DBusRunnerTest::cleanupTestCase()
> Totals: 2 passed, 1 failed, 0 skipped, 0 blacklisted, 4931ms
> * Finished testing of DBusRunnerTest *
>
> --
> Regards
> Hartmut Goebel
>
> | Hartmut Goebel  | h.goe...@crazy-compilers.com   |
> | www.crazy-compilers.com | compilers which you thought are impossible |
>
>
>

Test failures with krunner 5.39.0

[Hartmut Goebel]

Hallo,

I'm packaging krunner 5.39.0 for GNU Guix [1]. GNU Guix builds all
software in an isolated environment (a container), which includes only
the packages and tools specified explicitly.

When running the tests, dbusrunnertest faills, with this notable warning
and the error show below:

   DBusRunnerTest::testMatch() org.kde.krunner: Invalid entry: "DBus
runner test"

Any idea what may be missing, what needs to be set up (env-var,
directory, package, paths)? Any idea hos to debug this further?

All required packages and all optional/feature packages (except of QCH)
are installed. I tried running the tests with both dbus-launch and
without. The external program "testremoterunner" gets started. strace -e
trace=file" shows nothing relevant (as far as I can tell).

* Start testing of DBusRunnerTest *
Config: Using QtTest library 5.9.2, Qt 5.9.2 (x86_64-little_endian-lp64
shared (dynamic) release build; by GCC 5.4.0)
PASS   : DBusRunnerTest::initTestCase()
QWARN  : DBusRunnerTest::testMatch() inotify_add_watch("/etc/mtab")
failed: "No such file or directory"
QWARN  : DBusRunnerTest::testMatch() inotify_add_watch("/etc/fstab")
failed: "No such file or directory"
QWARN  : DBusRunnerTest::testMatch() org.kde.krunner: Invalid entry:
"DBus runner test"
FAIL!  : DBusRunnerTest::testMatch() 'spy.wait()' returned FALSE. ()
   Loc:
[/tmp/guix-build-krunner-5.39.0.drv-0/krunner-5.39.0/autotests/dbusrunnertest.cpp(82)]
PASS   : DBusRunnerTest::cleanupTestCase()
Totals: 2 passed, 1 failed, 0 skipped, 0 blacklisted, 4931ms
* Finished testing of DBusRunnerTest *

-- 
Regards
Hartmut Goebel

| Hartmut Goebel  | h.goe...@crazy-compilers.com   |
| www.crazy-compilers.com | compilers which you thought are impossible |