Commit a051961
committed
check: print device names provided to test_device_array()
When a test case has test_device(), blktests prints the name of the test
target device provided to test_device(). The commit 653ace8
("check, new: introduce test_device_array()") introduced the support for
test_device_array() which runs the test for multiple devices. However,
when the test case has test_device_array(), blktests does not print the
names of the test target devices.
Modify the check script to print the test target device names. For that
purpose, factor out two _output_status() calls into a new helper
function _output_test_name(). In that function, print TEST_DEV_ARRAY
elements which are provided to test_dev_array() as the test target.
After this commit, md/003 run will look like as follows:
md/003 => nvme1n1 nvme2n1 nvme3n1 nvme4n1 (test md atomic writes for NVMe drives) [passed]
runtime 18.678s ... 18.446s
Tested-by: John Garry <[email protected]>
Signed-off-by: Shin'ichiro Kawasaki <[email protected]>1 parent 8c610b5 commit a051961
1 file changed
+17
-8
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
252 | 252 | | |
253 | 253 | | |
254 | 254 | | |
255 | | - | |
| 255 | + | |
| 256 | + | |
| 257 | + | |
| 258 | + | |
| 259 | + | |
256 | 260 | | |
257 | | - | |
| 261 | + | |
| 262 | + | |
| 263 | + | |
| 264 | + | |
| 265 | + | |
| 266 | + | |
258 | 267 | | |
259 | | - | |
| 268 | + | |
260 | 269 | | |
| 270 | + | |
| 271 | + | |
| 272 | + | |
| 273 | + | |
261 | 274 | | |
262 | 275 | | |
263 | 276 | | |
| |||
277 | 290 | | |
278 | 291 | | |
279 | 292 | | |
280 | | - | |
281 | | - | |
282 | | - | |
283 | | - | |
284 | | - | |
| 293 | + | |
285 | 294 | | |
286 | 295 | | |
287 | 296 | | |
| |||
0 commit comments