aboutsummaryrefslogtreecommitdiff
path: root/include/scsi
diff options
context:
space:
mode:
authorChristian Schoenebeck <qemu_oss@crudebyte.com>2020-10-08 20:34:56 +0200
committerChristian Schoenebeck <qemu_oss@crudebyte.com>2020-10-19 14:25:40 +0200
commit051f0e5be12b2760d7fb2095b864b26ffe21f6de (patch)
tree25dd0a1bc6a9b16769fc19055cf7aa89ee2fa813 /include/scsi
parent3a565c641a5c50bd6d0cb4df881b607a279505f6 (diff)
downloadqemu-051f0e5be12b2760d7fb2095b864b26ffe21f6de.zip
qemu-051f0e5be12b2760d7fb2095b864b26ffe21f6de.tar.gz
qemu-051f0e5be12b2760d7fb2095b864b26ffe21f6de.tar.bz2
tests/9pfs: wipe local 9pfs test directory
Before running the first 9pfs test case, make sure the test directory for running the 9pfs 'local' tests on is entirely empty. For that reason simply delete the test directory (if any) before (re)creating it on test suite startup. Note: The preferable precise behaviour would be the test directory only being wiped once *before* a test suite run. Right now the test directory is also wiped at the *end* of a test suite run because libqos is calling the virtio_9p_register_nodes() callback for some reason also when a test suite completed. This is suboptimal as developers cannot immediately see what files and directories the 9pfs local tests created precisely after the test suite completed. But fortunately the test directory is not wiped if some test failed. So it is probably not worth it drilling another hole into libqos for this issue. Signed-off-by: Christian Schoenebeck <qemu_oss@crudebyte.com> Message-Id: <b30776ea3289dc40dabc7d0063d825d21d9a65bf.1602182956.git.qemu_oss@crudebyte.com> Signed-off-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
Diffstat (limited to 'include/scsi')
0 files changed, 0 insertions, 0 deletions