Actions
Bug #16025
closedunittest_chain_xattr failure in 'make check' bot
% Done:
0%
Source:
Q/A
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Perhaps the test still needs some better handling of different environments, e.g. with selinux setup, since it is working on the gitbuilders:
From https://jenkins.ceph.com/job/ceph-pull-requests/6114/console :
FAIL: unittest_chain_xattr ========================== [==========] Running 5 tests from 1 test case. [----------] Global test environment set-up. [----------] 5 tests from chain_xattr [ RUN ] chain_xattr.get_and_set [WARNING] ./src/gtest-death-test.cc:825:: Death tests use fork(), which is unsafe particularly in a threaded context. For this test, Google Test couldn't detect the number of threads. [WARNING] ./src/gtest-death-test.cc:825:: Death tests use fork(), which is unsafe particularly in a threaded context. For this test, Google Test couldn't detect the number of threads. [ OK ] chain_xattr.get_and_set (19 ms) [ RUN ] chain_xattr.chunk_aligned 2038 attr user.foo attr security.selinux attr user.bar attr security.selinux 2039 attr user.foo attr security.selinux attr user.bar attr security.selinux 2040 attr user.foo attr security.selinux attr user.bar attr security.selinux 2041 attr user.foo attr security.selinux attr user.bar attr security.selinux 2042 attr user.foo attr security.selinux attr user.bar attr security.selinux 2043 attr user.foo attr security.selinux attr user.bar attr security.selinux 2044 attr user.foo attr security.selinux attr user.bar attr security.selinux 2045 attr user.foo attr security.selinux attr user.bar attr security.selinux 2046 attr user.foo attr security.selinux attr user.bar attr security.selinux 2047 attr user.foo attr security.selinux attr user.bar attr security.selinux 2048 attr user.foo attr security.selinux attr user.bar attr security.selinux 2049 attr user.foo attr user.foo@1 attr security.selinux attr user.bar attr user.bar@1 attr security.selinux 2050 attr user.foo attr user.foo@1 attr security.selinux attr user.bar attr user.bar@1 attr security.selinux 2051 attr user.foo attr user.foo@1 attr security.selinux attr user.bar attr user.bar@1 attr security.selinux 2052 attr user.foo attr user.foo@1 attr security.selinux attr user.bar attr user.bar@1 attr security.selinux 2053 attr user.foo attr user.foo@1 attr security.selinux attr user.bar attr user.bar@1 attr security.selinux 2054 attr user.foo attr user.foo@1 attr security.selinux attr user.bar attr user.bar@1 attr security.selinux 2055 attr user.foo attr user.foo@1 attr security.selinux attr user.bar attr user.bar@1 attr security.selinux 2056 attr user.foo attr user.foo@1 attr security.selinux attr user.bar attr user.bar@1 attr security.selinux 2057 attr user.foo attr user.foo@1 attr security.selinux attr user.bar attr user.bar@1 attr security.selinux 240 attr user.foo attr security.selinux 241 attr user.foo attr security.selinux 242 attr user.foo attr security.selinux 243 attr user.foo attr security.selinux 244 attr user.foo attr security.selinux 245 attr user.foo attr security.selinux 246 attr user.foo attr security.selinux 247 attr user.foo attr security.selinux 248 attr user.foo attr security.selinux 249 attr user.foo attr security.selinux 250 attr user.foo attr security.selinux 251 attr user.foo attr user.foo@1 attr security.selinux 252 attr user.foo attr user.foo@1 attr security.selinux 253 attr user.foo attr user.foo@1 attr security.selinux 254 attr user.foo attr user.foo@1 attr security.selinux 255 attr user.foo attr user.foo@1 attr security.selinux 256 attr user.foo attr user.foo@1 attr security.selinux 257 attr user.foo attr user.foo@1 attr security.selinux 258 attr user.foo attr user.foo@1 attr security.selinux 259 attr user.foo attr user.foo@1 attr security.selinux [ OK ] chain_xattr.chunk_aligned (13 ms) [ RUN ] chain_xattr.listxattr [ OK ] chain_xattr.listxattr (0 ms) [ RUN ] chain_xattr.fskip_chain_cleanup_and_ensure_single_attr test/objectstore/chain_xattr.cc:371: Failure Value of: 1UL Actual: 1 Expected: get_xattrs(fd).size() Which is: 2 [ FAILED ] chain_xattr.fskip_chain_cleanup_and_ensure_single_attr (0 ms) [ RUN ] chain_xattr.skip_chain_cleanup_and_ensure_single_attr test/objectstore/chain_xattr.cc:415: Failure Value of: 1UL Actual: 1 Expected: get_xattrs(file).size() Which is: 2 [ FAILED ] chain_xattr.skip_chain_cleanup_and_ensure_single_attr (1 ms) [----------] 5 tests from chain_xattr (33 ms total) [----------] Global test environment tear-down [==========] 5 tests from 1 test case ran. (33 ms total) [ PASSED ] 3 tests. [ FAILED ] 2 tests, listed below: [ FAILED ] chain_xattr.fskip_chain_cleanup_and_ensure_single_attr [ FAILED ] chain_xattr.skip_chain_cleanup_and_ensure_single_attr 2 FAILED TESTS
Updated by Yuri Weinstein over 7 years ago
i see the same on manual run:
[yuriw@smithi018 build]$ bin/unittest_chain_xattr [==========] Running 5 tests from 1 test case. [----------] Global test environment set-up. [----------] 5 tests from chain_xattr [ RUN ] chain_xattr.get_and_set [WARNING] /home/yuriw/ceph/src/googletest/googletest/src/gtest-death-test.cc:836:: Death tests use fork(), which is unsafe particularly in a threaded context. For this test, Google Test detected 3 threads. [WARNING] /home/yuriw/ceph/src/googletest/googletest/src/gtest-death-test.cc:836:: Death tests use fork(), which is unsafe particularly in a threaded context. For this test, Google Test detected 3 threads. [ OK ] chain_xattr.get_and_set (24 ms) [ RUN ] chain_xattr.chunk_aligned 2038 attr security.selinux attr user.foo attr security.selinux attr user.bar 2039 attr security.selinux attr user.foo attr security.selinux attr user.bar 2040 attr security.selinux attr user.foo attr security.selinux attr user.bar 2041 attr security.selinux attr user.foo attr security.selinux attr user.bar 2042 attr security.selinux attr user.foo attr security.selinux attr user.bar 2043 attr security.selinux attr user.foo attr security.selinux attr user.bar 2044 attr security.selinux attr user.foo attr security.selinux attr user.bar 2045 attr security.selinux attr user.foo attr security.selinux attr user.bar 2046 attr security.selinux attr user.foo attr security.selinux attr user.bar 2047 attr security.selinux attr user.foo attr security.selinux attr user.bar 2048 attr security.selinux attr user.foo attr security.selinux attr user.bar 2049 attr security.selinux attr user.foo@1 attr user.foo attr security.selinux attr user.bar@1 attr user.bar 2050 attr security.selinux attr user.foo@1 attr user.foo attr security.selinux attr user.bar@1 attr user.bar 2051 attr security.selinux attr user.foo@1 attr user.foo attr security.selinux attr user.bar@1 attr user.bar 2052 attr security.selinux attr user.foo@1 attr user.foo attr security.selinux attr user.bar@1 attr user.bar 2053 attr security.selinux attr user.foo attr user.foo@1 attr security.selinux attr user.bar attr user.bar@1 2054 attr security.selinux attr user.foo attr user.foo@1 attr security.selinux attr user.bar attr user.bar@1 2055 attr security.selinux attr user.foo attr user.foo@1 attr security.selinux attr user.bar attr user.bar@1 2056 attr security.selinux attr user.foo attr user.foo@1 attr security.selinux attr user.bar attr user.bar@1 2057 attr security.selinux attr user.foo attr user.foo@1 attr security.selinux attr user.bar attr user.bar@1 240 attr security.selinux attr user.foo 241 attr security.selinux attr user.foo 242 attr security.selinux attr user.foo 243 attr security.selinux attr user.foo 244 attr security.selinux attr user.foo 245 attr security.selinux attr user.foo 246 attr security.selinux attr user.foo 247 attr security.selinux attr user.foo 248 attr security.selinux attr user.foo 249 attr security.selinux attr user.foo 250 attr security.selinux attr user.foo 251 attr security.selinux attr user.foo@1 attr user.foo 252 attr security.selinux attr user.foo@1 attr user.foo 253 attr security.selinux attr user.foo@1 attr user.foo 254 attr security.selinux attr user.foo@1 attr user.foo 255 attr security.selinux attr user.foo attr user.foo@1 256 attr security.selinux attr user.foo attr user.foo@1 257 attr security.selinux attr user.foo attr user.foo@1 258 attr security.selinux attr user.foo attr user.foo@1 259 attr security.selinux attr user.foo attr user.foo@1 [ OK ] chain_xattr.chunk_aligned (3 ms) [ RUN ] chain_xattr.listxattr [ OK ] chain_xattr.listxattr (1 ms) [ RUN ] chain_xattr.fskip_chain_cleanup_and_ensure_single_attr /home/yuriw/ceph/src/test/objectstore/chain_xattr.cc:371: Failure Expected: 1UL Which is: 1 To be equal to: get_xattrs(fd).size() Which is: 2 [ FAILED ] chain_xattr.fskip_chain_cleanup_and_ensure_single_attr (0 ms) [ RUN ] chain_xattr.skip_chain_cleanup_and_ensure_single_attr /home/yuriw/ceph/src/test/objectstore/chain_xattr.cc:415: Failure Expected: 1UL Which is: 1 To be equal to: get_xattrs(file).size() Which is: 2 [ FAILED ] chain_xattr.skip_chain_cleanup_and_ensure_single_attr (0 ms) [----------] 5 tests from chain_xattr (28 ms total) [----------] Global test environment tear-down [==========] 5 tests from 1 test case ran. (28 ms total) [ PASSED ] 3 tests. [ FAILED ] 2 tests, listed below: [ FAILED ] chain_xattr.fskip_chain_cleanup_and_ensure_single_attr [ FAILED ] chain_xattr.skip_chain_cleanup_and_ensure_single_attr 2 FAILED TESTS
Updated by Dan Mick over 7 years ago
Seems like the test might be being confused by extra security.selinux xattrs
Updated by Dan Mick over 7 years ago
It's true, files have a security.selinux attr under selinux and don't without. The test could get the current number of attrs and factor that in. testing a hack now.
Updated by Dan Mick over 7 years ago
- Assignee set to Dan Mick
(relatedly: how has this been here for 4 months at High priority? Are we doing bug scrubs?)
Actions