[telepathy-mission-control/master] dispatcher/dispatch-rejected-by-plugin.py: don't assert that we see ChannelLost

Simon McVittie simon.mcvittie at collabora.co.uk
Fri Jun 26 08:50:31 PDT 2009


In situations where processing is forcibly stopped, it seems reasonable
not to wait for the channel to close before terminating the dispatch
operation.
---
 .../dispatcher/dispatch-rejected-by-plugin.py      |    4 ----
 1 files changed, 0 insertions(+), 4 deletions(-)

diff --git a/test/twisted/dispatcher/dispatch-rejected-by-plugin.py b/test/twisted/dispatcher/dispatch-rejected-by-plugin.py
index b64965f..b77919b 100644
--- a/test/twisted/dispatcher/dispatch-rejected-by-plugin.py
+++ b/test/twisted/dispatcher/dispatch-rejected-by-plugin.py
@@ -112,10 +112,6 @@ def test(q, bus, mc):
             interface=cs.CHANNEL, method='Close', args=[],
             handled=True)
 
-    e = q.expect('dbus-signal',
-            path=cdo_path, interface=cs.CDO, signal='ChannelLost')
-    assert e.args[0] == chan.object_path
-
     q.expect_many(
             EventPattern('dbus-signal', path=cdo_path,
                 interface=cs.CDO, signal='Finished'),
-- 
1.5.6.5




More information about the telepathy-commits mailing list