Bug #13251
closedmon leaks lots on shutodwn
0%
Description
two instances of mon.b leaking a zillion objects
description: rados/verify/{1thrash/none.yaml clusters/fixed-2.yaml fs/btrfs.yaml msgr/simple.yaml
msgr-failures/few.yaml tasks/rados_api_tests.yaml validater/valgrind.yaml}
/a/sage-2015-09-25_13:41:11-rados-wip-sage-testing---basic-multi/1069006
description: rados/verify/{1thrash/none.yaml clusters/fixed-2.yaml fs/btrfs.yaml msgr/simple.yaml
msgr-failures/few.yaml tasks/rados_cls_all.yaml validater/valgrind.yaml}
/a/sage-2015-09-24_20:43:22-rados-wip-sage-testing---basic-multi/1067967
Updated by Samuel Just over 8 years ago
ubuntu@teuthology:/ceph/teuthology-archive/samuelj-2015-09-28_22:02:11-rados-wip-sam-testing-distro-basic-multi/1075268
also I think
Updated by Sage Weil over 8 years ago
- Status changed from New to In Progress
- Assignee set to Sage Weil
Updated by Sage Weil over 8 years ago
Pretty sure the problem is the fork() we do in common/SubProcess.cc, used to run crush tests via crushtool.
Updated by Sage Weil over 8 years ago
- Status changed from In Progress to Fix Under Review
https://github.com/ceph/teuthology/pull/644
it passes now! /a/sage-13251/1078478
Updated by Sage Weil over 8 years ago
- Status changed from Fix Under Review to Resolved