Dbus Timeout when running test/remote-test.py -v ZeitgeistRemoteAPITest
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zeitgeist Framework |
Fix Released
|
Medium
|
Markus Korn |
Bug Description
This Timeout "error" in "testFindByRand
% test/remote-test.py -v ZeitgeistRemote
Ensure that the DataSourceRegistry extension is there. If we'd want ... ok
testDeleteEvents (__main_
testFindByRando
ok
testFindEventsF
testFindRelated (__main_
File "/usr/lib/
reply_
File "test/remote-
self.
File "/usr/lib/
(msg or '%r != %r' % (first, second))
AssertionError: dbus.Array(
ok
testFindTwoOfTh
ok
testGetEvents (__main_
testInsertAndGe
testMonitorDele
testMonitorDele
testMonitorInse
testMonitorInst
testTwoMonitors
testUnicodeInsert (__main_
-------
Ran 14 tests in 47.956s
OK
I'm not sure if this is an issue with the engine or the client, or if we are just doing sth wrong in the testcase.
I also think we should change our Baseclass for tests to always mark a test as failed when a dbus error occures.
As a side note of wiredness, I don't get this timeout message when only running this testcase
% test/remote-test.py ZeitgeistRemote
.
-------
Ran 1 test in 3.026s
OK
Related branches
- Siegfried Gevatter: Needs Fixing
- Seif Lotfy: Approve
-
Diff: 224 lines (+97/-30)5 files modified_zeitgeist/engine/remote.py (+8/-1)
test/engine-extension-test.py (+12/-1)
test/engine-test.py (+10/-0)
test/remote-test.py (+28/-28)
test/testutils.py (+39/-0)
Changed in zeitgeist: | |
status: | Fix Committed → Fix Released |
Changed in zeitgeist: | |
milestone: | 0.4.1 → 0.5.0 |
I debugged this further, it is not ZeitgeistRemote APITest. testFindByRando mActorAndGet which is producing the timeout, it is ZeitgeistRemote APITest. testDeleteEvent s.