Valgrind runs itself on forked children, and does its cleanup when they
complete, and this is slow... slow enough that it frequently makes the
test time out.
Valgrind let's you ignore child *processes* that you exec, but I can't
find a way to skip forked children in the same address space.
Work around this by skip this validation when running under valgrind.
Fixes: http://tracker.ceph.com/issues/20602
Signed-off-by: Sage Weil <sage@redhat.com>
conf:
global:
osd heartbeat grace: 40
+ mon:
+ mon osd crush smoke test: false
valgrind:
mon: [--tool=memcheck, --leak-check=full, --show-reachable=yes]
osd: [--tool=memcheck]
debug deliberately leak memory: true
osd max object name len: 460
osd max object namespace len: 64
+ mon:
+ mon osd crush smoke test: false
valgrind:
mon: [--tool=memcheck, --leak-check=full, --show-reachable=yes]
osd: [--tool=memcheck]
conf:
global:
osd heartbeat grace: 40
+ mon:
+ mon osd crush smoke test: false
valgrind:
mon: [--tool=memcheck, --leak-check=full, --show-reachable=yes]
osd: [--tool=memcheck]
conf:
global:
osd heartbeat grace: 40
+ mon:
+ mon osd crush smoke test: false
valgrind:
mon: [--tool=memcheck, --leak-check=full, --show-reachable=yes]
osd: [--tool=memcheck]
conf:
global:
osd heartbeat grace: 40
+ mon:
+ mon osd crush smoke test: false
valgrind:
mon: [--tool=memcheck, --leak-check=full, --show-reachable=yes]
osd: [--tool=memcheck]