On Wed, 2019-04-17 at 16:38 +0800, [email protected] wrote: > From: Changqing Li <[email protected]> > > 1. since one bug in run-ptest, testcase test-bus have never been > actually run (althrough it's result is PASS). > > After commit 0828850, test-bus can actually run but it > did not install: > test-service, test-shell-service, test-segfault, and > dbus-daemon-launch-helper-test > Add the configure flag: > --enable-embedded-tests > to generate binary dbus-daemon-launch-helper-test, then install > them so that test-bus will now pass. > > 2. fix testcase test-dbus-daemon failed > we enable --enable-verbose-mode in recipe dbus-test, and don't > enable it in recipe dbus. This will make below test code get > unexpect result of have_verbose and assert. > disable --enable-verbose-mode for recipe dbus-test to fix it. > > #ifdef DBUS_ENABLE_STATS > g_assert_true (have_stats); > #else > g_assert_false (have_stats); > #endif > > Signed-off-by: Changqing Li <[email protected]> > --- > meta/recipes-core/dbus/dbus-test_1.12.12.bb | 13 ++++++++++--- > meta/recipes-core/dbus/dbus/run-ptest | 16 ++++++++++++---- > 2 files changed, 22 insertions(+), 7 deletions(-)
I'm wondering if some of these tests were intentionally not run due to the length of time they take? It takes the dbus-ptest time from 26s to 250+s. Can you see which test that is and why its taking so long please? Cheers, Richard -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
