Skip to contentSkip to conversation

generic/270: kill fsstress by exact name

PATCH In review Andrey Albershteyn 2 participants 2 messages Jul 9 – Jul 10

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 generic/270: kill fsstress by exact name

Running ./check with fsstress in the arguments (for example -x fsstress_scrub) causes pkill to kill parent bash process executing the tests. The test suite execution just stops with:

xfstests-start[4099970]: Terminated _run_seq 2>&1 | tee $tmp.out
xfstests-start[4099970]: Ran: generic/269 generic/270 xfstests-start[4102535]: Interrupted! xfstests-start[4102538]: Interrupted!

Fix by using exact name, we can not use _pkill_fsstress here as this test copies fsstress binary under custom name.

---
 tests/generic/270 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
tests/generic/270 +1 -1
index 9ac829a7379f..73464f02d3d9 100755
@@ -50,7 +50,7 @@ _workout()
 		sleep $enospc_time
 	done
 
-	_pkill -PIPE -f fsstress
+	_pkill -PIPE -f "$tmp.fsstress.bin"
 	wait $_FSSTRESS_PID
 	return 0
 }
Signature · 1 line
2.54.0