The test doesn't even get past the setup function.
The setup function is quite basic. Create an image, partition the image, create filesystem on the image.
https://git.launchpad.net/~ubuntu-core-dev/+git/systemd/tree/test/test-functions?h=ubuntu-artful#n333
It appears that the kernel has failed to re-read the partition table, as /dev/loop4p1 is expected to exist.
Is sfdisk not sufficient to re-read the parition table?! i wonder if between calling sfdisk and mkfs, and udevadm wait for idle state is needed.
The test doesn't even get past the setup function.
The setup function is quite basic. Create an image, partition the image, create filesystem on the image.
https:/ /git.launchpad. net/~ubuntu- core-dev/ +git/systemd/ tree/test/ test-functions? h=ubuntu- artful# n333
It appears that the kernel has failed to re-read the partition table, as /dev/loop4p1 is expected to exist.
Is sfdisk not sufficient to re-read the parition table?! i wonder if between calling sfdisk and mkfs, and udevadm wait for idle state is needed.