From: Marcel Holtmann <marcel@holtmann.org>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/2] unit: Fix intermitent failure of SDP tests
Date: Wed, 09 Jan 2013 17:21:14 -0800 [thread overview]
Message-ID: <1357780874.1806.65.camel@aeonflux> (raw)
In-Reply-To: <1357779808-25513-1-git-send-email-anderson.lizardo@openbossa.org>
Hi Anderson,
change the subject of the commit ;)
> While running tests, the D-Bus library was set to call _exit() when the
> client leaves the bus. This caused the second test to be interrupted
> without providing a PASS/FAIL result. This was confirmed by running
> test-sdp with DBUS_VERBOSE=1.
>
> This commit disables this behavior, which does not exist on BlueZ
> because g_dbus_set_disconnect_function() implicitly does this.
> ---
> unit/test-gdbus-client.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/unit/test-gdbus-client.c b/unit/test-gdbus-client.c
> index 7c849f0..cfbe4e0 100644
> --- a/unit/test-gdbus-client.c
> +++ b/unit/test-gdbus-client.c
> @@ -68,6 +68,10 @@ static struct context *create_context(void)
> return NULL;
> }
>
> + /* Make sure D-Bus library will not call _exit() and interrupt the next
> + * tests. */
Can you make this a one-line comment like this or similar:
/* Avoid D-Bus library calling _exit() before next test */
> + dbus_connection_set_exit_on_disconnect(context->dbus_conn, FALSE);
> +
> return context;
> }
>
Regards
Marcel
next prev parent reply other threads:[~2013-01-10 1:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 1:03 [PATCH BlueZ 1/2] unit: Fix intermitent failure of SDP tests Anderson Lizardo
2013-01-10 1:03 ` [PATCH BlueZ 2/2] unit: Print D-Bus error message in verbose mode Anderson Lizardo
2013-01-10 1:22 ` Marcel Holtmann
2013-01-10 1:21 ` Marcel Holtmann [this message]
2013-01-10 12:30 ` [PATCH v2 BlueZ] unit: Avoid D-Bus calling _exit() during SDP tests Anderson Lizardo
2013-01-10 12:31 ` Johan Hedberg
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=1357780874.1806.65.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=anderson.lizardo@openbossa.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.