Linux bluetooth development
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH obexd 2/2 v2] test: Use longer D-Bus timeout in test scripts
Date: Thu, 20 Sep 2012 15:07:15 +0300	[thread overview]
Message-ID: <1348142835-13146-2-git-send-email-luiz.dentz@gmail.com> (raw)
In-Reply-To: <1348142835-13146-1-git-send-email-luiz.dentz@gmail.com>

From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>

As the daemon already waits for 60 seconds for the first response this
just use the same timeout for calls that don't use transfer but return the
response as reply.
---
 test/map-client | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/test/map-client b/test/map-client
index ac1a8ca..7741c7f 100755
--- a/test/map-client
+++ b/test/map-client
@@ -109,11 +109,11 @@ class MapClient:
 			print "%s/" % (i["Name"])
 
 	def list_messages(self, folder):
-		ret = self.map.GetMessageListing(folder, dict())
+		ret = self.map.GetMessageListing(folder, dict(), timeout=60)
 		print pformat(unwrap(ret))
 
 	def get_message(self, handle):
-		self.map.GetMessageListing("", dict())
+		self.map.GetMessageListing("", dict(), timeout=60)
 		path = self.path + "/message" + handle
 		obj = bus.get_object("org.bluez.obex.client", path)
 		msg = dbus.Interface(obj, "org.bluez.obex.Message")
-- 
1.7.11.4


      reply	other threads:[~2012-09-20 12:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 12:07 [PATCH obexd 1/2 v2] client: Use larger timeout first packet in transfers Luiz Augusto von Dentz
2012-09-20 12:07 ` Luiz Augusto von Dentz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1348142835-13146-2-git-send-email-luiz.dentz@gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox