RepoMirrors/ceph
1
0
Fork 0
mirror of https://github.com/ceph/ceph synced 2025-03-11 02:39:05 +00:00
Code Issues Packages Projects Releases Wiki Activity
cd56b91021
ceph/qa/suites/rados/verify/validater/valgrind.yaml

30 lines
861 B
YAML
Raw Normal View History

do all valgrind runs on centos We are fighting two issues with valgrind on ubuntu (xenial, yakkety, and z): http://tracker.ceph.com/issues/18126 http://tracker.ceph.com/issues/20360 Revert this when it is fixed. Signed-off-by: Sage Weil <sage@redhat.com>
2017-06-30 13:33:10 +00:00
# see http://tracker.ceph.com/issues/20360 and http://tracker.ceph.com/issues/18126
os_type: centos
add valgrind collection to regression suite Run a smaller set of tests with valgrind on the mon, osd, and mds. Valgrind is currently ignoring leaks, but this will pick up use-after-free and similar badness.
2012-02-21 18:02:44 +00:00
overrides:
use notcmalloc builder for valgrind leak checking This reverts 453d72b294af6d3db1ae7a212ba9b43209d69f26. It turns out that tcmalloc defeats the leak checking in valgrind. Signed-off-by: Sage Weil <sage@inktank.com>
2014-07-08 23:39:19 +00:00
install:
ceph:
flavor: notcmalloc
suites: debuginfo: true for valgrind This lets us get line numbers in the valgrind xml output. Signed-off-by: Sage Weil <sage@redhat.com>
2016-02-26 14:46:27 +00:00
debuginfo: true
add valgrind collection to regression suite Run a smaller set of tests with valgrind on the mon, osd, and mds. Valgrind is currently ignoring leaks, but this will pick up use-after-free and similar badness.
2012-02-21 18:02:44 +00:00
ceph:
osd_heartbeat_grace from 20 -> 40 when running valgrind This will mask occasional 'wrongly marked me down' errors when valgrind is running (it makes things generally slow). Signed-off-by: Sage Weil <sage@inktank.com>
2014-05-21 22:43:41 +00:00
conf:
global:
osd heartbeat grace: 40
qa/suites/rados/verify/validator/valgrind: debug refs = 5 If we detect a leak, let's include logging so we can find it. Signed-off-by: Sage Weil <sage@redhat.com>
2019-02-05 13:30:52 +00:00
debug refs: 5
qa/suites: disable mon crush smoke test with valgrind 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>
2017-07-14 15:42:31 +00:00
mon:
mon osd crush smoke test: false
osd: add osd_fast_shutdown option (default true) If we get a SIGINT or SIGTERM or are deleted from the OSDMap, do a fast shutdown by exiting immediately. This has a few important benefits: - We immediately stop responding (binding) to any sockets, which means other OSDs will immediately decide we are down (and dead!). This minimizes IO interruption. - We avoid the complex "clean" shutdown process, which is historically a source of bugs. In reality, the only purpose of the "clean" shutdown is to try to tear down everything in memory so we can do memory leak checking with valgrind. Set this option to false for valgrind QA runs so we can still do that. Not that with the new read leases in octopus, we rely on the default behavior that a ECONNREFUSED is taken to mean that the OSD is fully dead, so that we don't have to wait for any leases to time out. This works in sane environments with normal IP networks, but that behavior could conceivably be a bad idea if there are some weird network shenanigans going on. If osd_fast_fail_on_connection_refused were disabled, then this fast shutdown procedure might be *worse* than the clean shutdown because we would have to wait for the heartbeat timeout. Signed-off-by: Sage Weil <sage@redhat.com>
2019-11-15 15:31:50 +00:00
osd:
osd fast shutdown: false
qa/suites/rados/verify/validater/valgrind: whitelist PG_ Peering might be slow due to valgrind. Signed-off-by: Sage Weil <sage@redhat.com>
2017-08-12 18:18:59 +00:00
log-whitelist:
- overall HEALTH_
# valgrind is slow.. we might get PGs stuck peering etc
- \(PG_
qa/suites/rados/verify: whitelist MON_DOWN when using valgrind Signed-off-by: Sage Weil <sage@redhat.com>
2019-09-29 15:27:01 +00:00
# mons sometimes are left off of initial quorum due to valgrind slowness. ok to whitelist here because we'll still catch an actual crash due to the core
- \(MON_DOWN\)
add valgrind collection to regression suite Run a smaller set of tests with valgrind on the mon, osd, and mds. Valgrind is currently ignoring leaks, but this will pick up use-after-free and similar badness.
2012-02-21 18:02:44 +00:00
valgrind:
check ceph-mon for leaks
2012-11-16 06:04:20 +00:00
mon: [--tool=memcheck, --leak-check=full, --show-reachable=yes]
add valgrind collection to regression suite Run a smaller set of tests with valgrind on the mon, osd, and mds. Valgrind is currently ignoring leaks, but this will pick up use-after-free and similar badness.
2012-02-21 18:02:44 +00:00
osd: [--tool=memcheck]
mds: [--tool=memcheck]
qa/suites: disable valgrind leak checks on ceph-mgr We've disabled the "clean" shutdown in ceph-mgr due to https://tracker.ceph.com/issues/38621 Until then, no valgrind leak checks! Signed-off-by: Sage Weil <sage@redhat.com>
2019-03-07 17:23:19 +00:00
# https://tracker.ceph.com/issues/38621
# mgr: [--tool=memcheck]
Reference in New Issue Copy Permalink