From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Gibson To: passt-dev@passt.top Subject: [PATCH 15/18] tests: Clean up better after iperf tests Date: Fri, 15 Jul 2022 15:21:38 +1000 Message-ID: <20220715052141.890703-16-david@gibson.dropbear.id.au> In-Reply-To: <20220715052141.890703-1-david@gibson.dropbear.id.au> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9009545260974580304==" --===============9009545260974580304== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit The iperf based test commands create a bunch of .bw and .pid files for each iperf client and server. The server side .bw files are cleaned up afterwards, but the pid files are not, and none of the client side files are cleaned up. The latter doesn't really matter when the client is run on ephemeral guests, but sometimes we run it in a namespace that shares the filesystem with the host. Clean up all of these files after the tests. Signed-off-by: David Gibson --- test/lib/test | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/lib/test b/test/lib/test index cb89e0b..e5a8632 100755 --- a/test/lib/test +++ b/test/lib/test @@ -79,7 +79,7 @@ test_iperf3() { pane_wait "${__pane}" pane_parse "${__pane}" pane_run "${__pane}" 'for i in $(seq 0 '${__procs}'); do' \ - 'rm -f s${i}.bw; done' + 'rm -f [cs]${i}.bw [cs]${i}.pid; done' pane_status "${__pane}" } -- 2.36.1 --===============9009545260974580304==--