On Tue, Feb 25, 2025 at 08:06:50AM +0100, Thomas Huth wrote: > Test 162 recently started failing for me for no obvious reasons (I > did not spot any suspicious commits in this area), but looking in > the 162.out.bad log file, there was a suspicious message at the end: > > qemu-nbd: Cannot lock pid file: Resource temporarily unavailable > > And indeed, the test starts the NBD server two times, without stopping > the first server before running the second one, so the second one can > indeed fail to lock the PID file. Thus let's make sure to stop the > first server before the test continues with the second one. With this > change, the test works fine for me again. > > Signed-off-by: Thomas Huth <th...@redhat.com> > --- > tests/qemu-iotests/162 | 1 + > 1 file changed, 1 insertion(+)
Reviewed-by: Eric Blake <ebl...@redhat.com> -- Eric Blake, Principal Software Engineer Red Hat, Inc. Virtualization: qemu.org | libguestfs.org
