http://bugs.meego.com/show_bug.cgi?id=5609

--- Comment #15 from qkmiao <[email protected]> 2010-10-14 07:43:04 PDT ---
(In reply to comment #14)
> From bug #7761 comment #3:
> 
> (In reply to comment #2)
> > patrick, this fix makes one case of test-dbus failed. you can find it in the
> > nightly report.  
> 
> Which one? This here?
> 
> FAIL: check the Server.GetCapabilities() call
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/home/nightly/syncevolution-testing/syncevolution/test/test-dbus.py",
> line 557, in testCapabilities
>     self.failUnlessEqual(capabilities, ['ConfigChanged', 'GetConfigName',
> 'Notifications', 'SessionFlags', 'Version'])
> AssertionError: dbus.Array([dbus.String(u'ConfigChanged'),
> dbus.String(u'GetConfigName'), dbus.String(u'Notifications'),
> dbus.String(u'SessionAttach'), dbus.String(u'SessionFlags'),
> dbus.String(u'Version')], signature=dbus.Signature('s')) != ['ConfigChanged',
> 'GetConfigName', 'Notifications', 'SessionFlags', 'Version']
> 
> 
> The test-dbus.py script seems to be out-dated:
> http://meego.gitorious.org/meego-middleware/syncevolution/blobs/master/test/test-dbus.py#line557
> 
>   self.failUnlessEqual(capabilities, ['ConfigChanged', 'GetConfigName',
> 'Notifications', 'SessionAttach', 'SessionFlags', 'Version'])
> 
> How can this happen? Isn't the nightly testing using the version of
> test-dbus.py from the checkout that it is testing?  

I checked the nightly testing script. test-dbus.py was not the latest code. It
was got from /home/nightly/syncevolution-testing/syncevolution/test. I am not
very clear about the history why sub-directory "syncevolution" used in
/home/nightly/syncevolution-testing. I will fix this.

-- 
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues

Reply via email to