test: wait for loopback device being actually created
authorYu Watanabe <watanabe.yu+github@gmail.com>
Mon, 14 Mar 2022 13:02:37 +0000 (22:02 +0900)
committerYu Watanabe <watanabe.yu+github@gmail.com>
Tue, 15 Mar 2022 03:35:50 +0000 (12:35 +0900)
commit6626ea08f6db3c050b5e05fa760cf0e371862173
tree73a0baec764b2290ec8e688d5ec89d2eaa4d0c5a
parent8c166c962d9fdb69ec3333e4587d716a68a043fc
test: wait for loopback device being actually created

It seems there exists a short time period that we cannot see the
loopback device after `losetup` is finished:
```
testsuite-58.sh[367]: ++ losetup -b 1024 -P --show -f /tmp/testsuite-58-sector-1024.img
kernel: loop1: detected capacity change from 0 to 204800
testsuite-58.sh[285]: + LOOP=/dev/loop1
testsuite-58.sh[285]: + systemd-repart --pretty=yes --definitions=/tmp/testsuite-58-sector/ --seed=750b6cd5c4ae4012a15e7be3c29e6a47 --empty=require --dry-run=no /dev/loop1
testsuite-58.sh[368]: Device '/dev/loop1' has no dm-crypt/dm-verity device, no need to look for underlying block device.
testsuite-58.sh[368]: Failed to determine canonical path for '/dev/loop1': No such file or directory
testsuite-58.sh[368]: Failed to open file or determine backing device of /dev/loop1: No such file or directory
```
test/units/testsuite-58.sh