zeitgeist team mailing list archive

[Markus Korn <thekorn@xxxxxx>]

The more I look into it the more issues I see ;)
There are two issues you can see in the description of this bug:
 1.) testDeleteEvents is timing out, but the testcase is marked as Ok (aka no failure, but a timeout won't be ok)
 2.) testFindRelated indicates an AssertionError, but the test is also marked as Ok.

I will work on both issues, and attach the branch for further review.

Markus

** Changed in: zeitgeist
     Assignee: (unassigned) => Markus Korn (thekorn)

** Changed in: zeitgeist
   Importance: Undecided => Medium

** Changed in: zeitgeist
       Status: New => In Progress

** Changed in: zeitgeist
    Milestone: None => 0.4.1

-- 
Dbus Timeout when running test/remote-test.py -v ZeitgeistRemoteAPITest
https://bugs.launchpad.net/bugs/595411
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.

Status in Zeitgeist Framework: In Progress

Bug description:
This Timeout "error" in "testFindByRandomActorAndGet" is reproducible for me when running the testsuite

% test/remote-test.py -v ZeitgeistRemoteAPITest                                                                :(
Ensure that the DataSourceRegistry extension is there. If we'd want ... ok
testDeleteEvents (__main__.ZeitgeistRemoteAPITest) ... ok
testFindByRandomActorAndGet (__main__.ZeitgeistRemoteAPITest) ... Error from Zeitgeist engine: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
ok
testFindEventsForValues (__main__.ZeitgeistRemoteAPITest) ... ok
testFindRelated (__main__.ZeitgeistRemoteAPITest) ... Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 576, in msg_reply_handler
    reply_handler(*message.get_args_list(**get_args_opts))
  File "test/remote-test.py", line 292, in callback
    self.assertEquals(uris, ["i2", "i1", "i3", "i5"])
  File "/usr/lib/python2.6/unittest.py", line 350, in failUnlessEqual
    (msg or '%r != %r' % (first, second))
AssertionError: dbus.Array([dbus.String(u'i3'), dbus.String(u'i2'), dbus.String(u'i1'), dbus.String(u'i5')], signature=dbus.Signature('s')) != ['i2', 'i1', 'i3', 'i5']
ok
testFindTwoOfThreeEvents (__main__.ZeitgeistRemoteAPITest) ... DEBUG:root:RESULTS [2, 1]
ok
testGetEvents (__main__.ZeitgeistRemoteAPITest) ... ok
testInsertAndGetEvent (__main__.ZeitgeistRemoteAPITest) ... ok
testMonitorDeleteEvents (__main__.ZeitgeistRemoteAPITest) ... ok
testMonitorDeleteNonExistingEvent (__main__.ZeitgeistRemoteAPITest) ... ok
testMonitorInsertEvents (__main__.ZeitgeistRemoteAPITest) ... ok
testMonitorInstallRemoval (__main__.ZeitgeistRemoteAPITest) ... ok
testTwoMonitorsDeleteEvents (__main__.ZeitgeistRemoteAPITest) ... ok
testUnicodeInsert (__main__.ZeitgeistRemoteAPITest) ... ok

----------------------------------------------------------------------
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 ZeitgeistRemoteAPITest.testFindByRandomActorAndGet
.
----------------------------------------------------------------------
Ran 1 test in 3.026s

OK