From: Eric Biggers <ebiggers@xxxxxxxxxx>
Since the upgrade of the chroot tarball to Debian Stretch, it's now
expected that devpts be mounted in the chroot. Otherwise there is a
warning message like the following when the shell starts:
mesg: ttyname failed: Success
Android mounts devpts already, so just bind-mount it into the chroot.
Signed-off-by: Eric Biggers <ebiggers@xxxxxxxxxx>
---
kvm-xfstests/android-xfstests | 2 ++
1 file changed, 2 insertions(+)
diff --git a/kvm-xfstests/android-xfstests b/kvm-xfstests/android-xfstests
index 8e5b77c..e204e2f 100755
--- a/kvm-xfstests/android-xfstests
+++ b/kvm-xfstests/android-xfstests
@@ -227,6 +227,7 @@ chroot_prepare()
! mountpoint $CHROOT_DIR/sys > /dev/null && mount sysfs -t sysfs $CHROOT_DIR/sys
! mountpoint $CHROOT_DIR/proc > /dev/null && mount proc -t proc $CHROOT_DIR/proc
! mountpoint $CHROOT_DIR/dev > /dev/null && mount --bind /dev $CHROOT_DIR/dev
+! mountpoint $CHROOT_DIR/dev/pts > /dev/null && mount --bind /dev/pts $CHROOT_DIR/dev/pts
# Allow xfstests to detect that SELinux is in use.
! mountpoint $CHROOT_DIR/sys/fs/selinux > /dev/null && \
@@ -258,6 +259,7 @@ chroot_wipe()
umount $CHROOT_DIR/sys/fs/selinux &> /dev/null
umount $CHROOT_DIR/sys &> /dev/null
umount $CHROOT_DIR/proc &> /dev/null
+umount $CHROOT_DIR/dev/pts &> /dev/null
umount $CHROOT_DIR/dev &> /dev/null
umount $CHROOT_DIR/results &> /dev/null
rm -rf $CHROOT_DIR
--
2.14.1.581.gf28d330327-goog
--
To unsubscribe from this list: send the line "unsubscribe fstests" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
