RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 650594 - libcap-ng self-test fails
Summary: libcap-ng self-test fails
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libcap-ng
Version: 6.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Steve Grubb
QA Contact: Ondrej Moriš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-07 09:51 UTC by Ondrej Moriš
Modified: 2010-11-08 13:09 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 08:32:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Ondrej Moriš 2010-11-07 09:51:06 UTC 
Description of problem:

Component libcap-ng contains self-test, but its execution fails on RHEL6.

Version-Release number of selected component (if applicable):

* libcap-ng-0.6.4-3.el6
* libcap-ng-0.6.4-3.el6_0.1

How reproducible:

Always.

Steps to Reproduce:

1. rpmbuild -vv -bc ~/rpmbuild/SPECS/libcap-ng.spec
2. make -C ~/rpmbuild/BUILD/libcap-ng-0.6.4 check
  
Actual results:

make: Entering directory `/root/rpmbuild/BUILD/libcap-ng-0.6.4'
Making check in src
make[1]: Entering directory `/root/rpmbuild/BUILD/libcap-ng-0.6.4/src'
Making check in test
make[2]: Entering directory `/root/rpmbuild/BUILD/libcap-ng-0.6.4/src/test'
make  lib_test thread_test
make[3]: Entering directory `/root/rpmbuild/BUILD/libcap-ng-0.6.4/src/test'
make[3]: `lib_test' is up to date.
make[3]: `thread_test' is up to date.
make[3]: Leaving directory `/root/rpmbuild/BUILD/libcap-ng-0.6.4/src/test'
make  check-TESTS
make[3]: Entering directory `/root/rpmbuild/BUILD/libcap-ng-0.6.4/src/test'
Doing basic bit tests...
Doing advanced bit tests for 33 capabilities...
PASS: lib_test
Testing thread separation of capabilities
Detected capabilities when they should not be any
FAIL: thread_test
===================
1 of 2 tests failed
===================
make[3]: *** [check-TESTS] Error 1
make[3]: Leaving directory `/root/rpmbuild/BUILD/libcap-ng-0.6.4/src/test'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory `/root/rpmbuild/BUILD/libcap-ng-0.6.4/src/test'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/root/rpmbuild/BUILD/libcap-ng-0.6.4/src'
make: *** [check-recursive] Error 1
make: Leaving directory `/root/rpmbuild/BUILD/libcap-ng-0.6.4'

Expected results:

All test passed.
Comment 1 Steve Grubb 2010-11-08 01:07:10 UTC 
Was that test run as root by any chance? The code is designed to run as non-root.
Comment 2 Ondrej Moriš 2010-11-08 08:32:36 UTC 
Ah.. you're right, I was running self-test by root and when using non-root account it passes. Great, hence I will close this bug as NOTABUG. Unfortunately, there is no information about using non-root account to run self-test in README or INSTALL even though it might be interesting (why?).
Comment 3 Steve Grubb 2010-11-08 13:09:35 UTC 
I'll make some changes upstream to either skip the test if root or run a different test if root.
Note You need to log in before you can comment on or make changes to this bug.