[telepathy-mission-control/master] account-manager/presence.py: don't fail when valgrinding

[Simon McVittie]

Some AccountPropertyChanged signals that are normally combined may end up
separate when valgrinding (it's that much slower).
---
 test/twisted/account-manager/presence.py |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/test/twisted/account-manager/presence.py b/test/twisted/account-manager/presence.py
index 9a6fb5e..c7967da 100644
--- a/test/twisted/account-manager/presence.py
+++ b/test/twisted/account-manager/presence.py
@@ -38,7 +38,7 @@ def test(q, bus, mc):
 
     q.expect('dbus-signal', path=account.object_path,
             interface=cs.ACCOUNT, signal='AccountPropertyChanged',
-            predicate=lambda e: e.args[0]['CurrentPresence'] == presence)
+            predicate=lambda e: e.args[0].get('CurrentPresence') == presence)
 
     # Change requested presence after going online
     presence = dbus.Struct((dbus.UInt32(cs.PRESENCE_TYPE_AWAY), 'away',
@@ -61,7 +61,7 @@ def test(q, bus, mc):
 
     q.expect('dbus-signal', path=account.object_path,
             interface=cs.ACCOUNT, signal='AccountPropertyChanged',
-            predicate=lambda e: e.args[0]['CurrentPresence'] == presence)
+            predicate=lambda e: e.args[0].get('CurrentPresence') == presence)
 
 if __name__ == '__main__':
     exec_test(test, {})
-- 
1.5.6.5