And something to be aware of as well: wjw@cephdev:~/master % sysctl -w kern.corefile=core.%N.%P kern.corefile: core.%N sysctl: kern.corefile=core.%N.%P: Operation not permitted Setting core-name output only works as root. --WjW On 11-8-2017 10:51, Willem Jan Withagen wrote: > @dzafman > I'm running into a small snag when running a full test: > I've added a line to show what is in the directory > ``` > 6: > /home/jenkins/workspace/ceph-master/qa/standalone/ceph-helpers.sh:172: > teardown: pwd > 6: /home/jenkins/workspace/ceph-master/build/src/test > 6: > /home/jenkins/workspace/ceph-master/qa/standalone/ceph-helpers.sh:173: > teardown: ls . > 6: CMakeFiles > 6: CTestTestfile.cmake > 6: Makefile > 6: ObjectMap > 6: bench > 6: cls_hello > 6: cls_lock > 6: cls_log > 6: cls_lua > 6: cls_numops > 6: cls_rbd > 6: cls_refcount > 6: cls_replica_log > 6: cls_rgw > 6: cls_sdk > 6: cls_statelog > 6: cls_version > 6: cmake_install.cmake > 6: common > 6: compressor > 6: core.ceph_test_objectsto.51398 > 6: core.unittest_bufferlist.50899 > 6: core.unittest_signals.50922 > 6: core.unittest_texttable.51005 > ``` > CWD = build/src/test > > So the setup routine already starts to fail in teardown because there > where cores, left from previous tests. > Question is how to find out who generated the cores, and do they > actually belong to the current test. > Complexing problem is that `%N` only uses the first 19 chars of a > process name. > > perhaps we should set core-names to something like "core.${testname}"?? > > --WjW > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html