Description of problem:
when running dbus unit tests on ppc64 I can see some failures
#0 0x00396402 in __kernel_vsyscall ()
#1 0x00a69320 in __nanosleep_nocancel () from /lib/libpthread.so.0
#2 0x080be9a6 in _dbus_sleep_milliseconds (milliseconds=180000)
#3 0x080bd634 in _dbus_abort () at dbus-sysdeps.c:83
#4 0x080a9f5c in _dbus_warn (format=0x80dd7bc "Did not expect error %s\n")
#5 0x0806b0e7 in check_list_services (context=0x9ae2998, connection=0x9ace618)
#6 0x0806c1be in bus_dispatch_test_conf (test_data_dir=<value optimized out>,
filename=<value optimized out>, use_launcher=0) at dispatch.c:4519
#7 0x0806cafc in bus_dispatch_test (test_data_dir=0xbfd4c7c4)
#8 0x0807b221 in main (argc=155, argv=0xbfd4c884) at test-main.c:131
don't know if this can be somehow critical or is caused by test itself
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.execute /desktop/rhel5/dbus/dbus-unit-tests from beaker
Hmm, is this a regression? Or did we just start recently running the tests on ppc64?
It's worth noting that in the last few months a significant amount of work has gone into dbus upstream tests; they're now a lot less crappy to be blunt =)
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).