In the current implementation of the QEMU bash iotests, only qemu-io
processes may be run under the Valgrind, which is a useful tool for
finding memory usage issues. Let's allow the common.rc bash script
runing all the QEMU processes, such as qemu-kvm, qemu-img, qemu-ndb
and qemu-vxhs, under the Valgrind tool.

v6:
  01: The possibility was added for a user to exclude particular processes
      from running under the Valgrind to speed up the test run (suggested
      by John).
  02: The shim function _NO_VALGRIND() was introduced as a workaround for
      the Valgrind bug that hangs QEMU killed process (suggested by John).
  03: The comments were amended in the commit messages and common.rc file.

  Discussed in the email threads with the message IDs:
  <1563553816-148827-1-git-send-email-andrey.shinkev...@virtuozzo.com>
  <1560276131-683243-1-git-send-email-andrey.shinkev...@virtuozzo.com>

Andrey Shinkevich (6):
  iotests: allow Valgrind checking all QEMU processes
  iotests: exclude killed processes from running under Valgrind
  iotests: Add casenotrun report to bash tests
  iotests: Valgrind fails with nonexistent directory
  iotests: extended timeout under Valgrind
  iotests: extend sleeping time under Valgrind

 tests/qemu-iotests/028       |   6 ++-
 tests/qemu-iotests/039       |   5 ++
 tests/qemu-iotests/039.out   |  30 ++---------
 tests/qemu-iotests/051       |   4 ++
 tests/qemu-iotests/061       |   2 +
 tests/qemu-iotests/061.out   |  12 +----
 tests/qemu-iotests/137       |   1 +
 tests/qemu-iotests/137.out   |   6 +--
 tests/qemu-iotests/183       |   9 +++-
 tests/qemu-iotests/192       |   6 ++-
 tests/qemu-iotests/247       |   6 ++-
 tests/qemu-iotests/common.rc | 124 ++++++++++++++++++++++++++++++++++++-------
 12 files changed, 149 insertions(+), 62 deletions(-)

-- 
1.8.3.1


Reply via email to