diff options
| author | Andrey Shinkevich <andrey.shinkevich@virtuozzo.com> | 2019-09-04 12:11:20 +0300 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2019-09-13 12:18:37 +0200 |
| commit | 8af224d66b1c259d19d5edbb8ac3d93627c3492a (patch) | |
| tree | 4c3d92a5ce273dbddfb6211f7f17f91e1b404891 /tests/qemu-iotests/137 | |
| parent | 036d8cbffd7785052d511f5cc83b969f0e827be1 (diff) | |
| download | qemu-8af224d66b1c259d19d5edbb8ac3d93627c3492a.zip qemu-8af224d66b1c259d19d5edbb8ac3d93627c3492a.tar.gz qemu-8af224d66b1c259d19d5edbb8ac3d93627c3492a.tar.bz2 | |
iotests: exclude killed processes from running under Valgrind
The Valgrind tool fails to manage its termination in multi-threaded
processes when they raise the signal SIGKILL. The bug has been reported
to the Valgrind maintainers and was registered as the bug #409141:
https://bugs.kde.org/show_bug.cgi?id=409141
Let's exclude such test cases from running under the Valgrind until a
new version with the bug fix is released because checking for the
memory issues is covered by other test cases.
Suggested-by: John Snow <jsnow@redhat.com>
Signed-off-by: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
Reviewed-by: John Snow <jsnow@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'tests/qemu-iotests/137')
| -rwxr-xr-x | tests/qemu-iotests/137 | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/tests/qemu-iotests/137 b/tests/qemu-iotests/137 index 0c3d2a1..089821d 100755 --- a/tests/qemu-iotests/137 +++ b/tests/qemu-iotests/137 @@ -130,6 +130,7 @@ echo # Whether lazy-refcounts was actually enabled can easily be tested: Check if # the dirty bit is set after a crash +_NO_VALGRIND \ $QEMU_IO \ -c "reopen -o lazy-refcounts=on,overlap-check=blubb" \ -c "write -P 0x5a 0 512" \ |