Disable new SIGABRT test on valgrind (#8013)

The crash reports cause false-positive warnings when run with valgrind.
This commit is contained in:
Meir Shpilraien (Spielrein) 2020-11-04 13:13:55 +02:00 committed by GitHub
parent 639b73cd2a
commit 762be79f0b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -1,7 +1,7 @@
set server_path [tmpdir server.log]
set system_name [string tolower [exec uname -s]] set system_name [string tolower [exec uname -s]]
if {$system_name eq {linux} || $system_name eq {darwin}} { if {$system_name eq {linux} || $system_name eq {darwin}} {
set server_path [tmpdir server.log]
start_server [list overrides [list dir $server_path]] { start_server [list overrides [list dir $server_path]] {
test "Server is able to generate a stack trace on selected systems" { test "Server is able to generate a stack trace on selected systems" {
r config set watchdog-period 200 r config set watchdog-period 200
@ -21,8 +21,9 @@ if {$system_name eq {linux} || $system_name eq {darwin}} {
} }
} }
} }
}
# Valgrind will complain that the process terminated by a signal, skip it.
if {!$::valgrind} {
set server_path [tmpdir server1.log] set server_path [tmpdir server1.log]
start_server [list overrides [list dir $server_path]] { start_server [list overrides [list dir $server_path]] {
test "Crash report generated on SIGABRT" { test "Crash report generated on SIGABRT" {
@ -33,3 +34,6 @@ start_server [list overrides [list dir $server_path]] {
assert {[string match $pattern $result]} assert {[string match $pattern $result]}
} }
} }
}
}