From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: kai.kang@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] dbus: fix ptest runtime failures
Date: Mon, 04 Sep 2017 21:04:43 +0100 [thread overview]
Message-ID: <1504555483.2175.78.camel@linuxfoundation.org> (raw)
In-Reply-To: <1919461d34964f3fccb8fe31931dc4daef977b41.1504517912.git.kai.kang@windriver.com>
On Mon, 2017-09-04 at 17:39 +0800, kai.kang@windriver.com wrote:
> From: Kai Kang <kai.kang@windriver.com>
>
> When run dbus ptest cases, there are some failures:
>
> >
> > ./test/test-dbus-daemon: relocation error: ./test/test-dbus-daemon:
> > symbol
> > _dbus_real_assert, version LIBDBUS_PRIVATE_1.10.20 not defined in
> > file
> > libdbus-1.so.3 with link time reference
> > FAIL: test/test-dbus-daemon
> > [ 24.943454] test-dbus-daemo[251]: segfault at 0
> > ip (null) sp
> > 00007ffddabe6818 error 14 in test-dbus-daemon-eavesdrop[
> > 400000+a000]
> It disables tests in dbus recipe which cases symbols missing and
> segment
> fault. When 'ptest' in DISTRO_FEATURES, it should enable some
> configure
> options to make the symbols visible to ptest cases.
>
> It also need to correct paths in ptest configure files.
Does this have a runtime effect on dbus, i.e. are these runtime asserts
which we don't want in production code?
Cheers,
Richard
next prev parent reply other threads:[~2017-09-04 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 9:39 [PATCH 0/1] dbus: fix ptest runtime failures kai.kang
2017-09-04 9:39 ` [PATCH 1/1] " kai.kang
2017-09-04 20:04 ` Richard Purdie [this message]
2017-09-05 1:56 ` Kang Kai
-- strict thread matches above, loose matches on Subject: below --
2017-09-05 3:12 [PATCH V2 0/1] " kai.kang
2017-09-05 3:13 ` [PATCH 1/1] " kai.kang
2017-09-05 10:01 ` Burton, Ross
2017-09-06 3:44 ` Kang Kai
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=1504555483.2175.78.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.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