++ t_=/home/remote/eblake/coreutils/tests/cu-runcon-no-reorder.EM7EZ3N6Hb
++ trap remove_tmp_ 0
++ trap 'Exit 129' 1
++ trap 'Exit 130' 2
++ trap 'Exit 131' 3
++ trap 'Exit 141' 13
++ trap 'Exit 143' 15
++ cd /home/remote/eblake/coreutils/tests/cu-runcon-no-reorder.EM7EZ3N6Hb
++ diff --version
++ grep GNU
++ fail=0
+ diag='runcon: runcon may be used only on a SELinux kernel'
+ echo 'runcon: runcon may be used only on a SELinux kernel'
++ id -Z
+ runcon unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 true -j
+ case `cat out` in
++ cat out
+ compare out exp
+ diff -u out exp
--- out 2010-09-16 11:35:12.682008155 -0600
+++ exp 2010-09-16 11:35:12.678988531 -0600
@@ -1 +1 @@
-runcon: failed to create security context:
unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023: Operation not
supported
+runcon: runcon may be used only on a SELinux kernel
+ fail=1
+ Exit 1
+ set +e
+ exit 1
+ exit 1
+ remove_tmp_
+ __st=1
+ cleanup_
+ :
+ cd /home/remote/eblake/coreutils/tests
But since the test already maps other failures to a common message,
perhaps all that is needed is an additional mapping if 'Operation not
supported' results from the attempt?
FAIL: misc/stat-mount (exit: 1)
===============================
++ initial_cwd_=/home/remote/eblake/coreutils/tests
+++ testdir_prefix_
+++ printf gt
++ pfx_=gt
+++ mktempd_ /home/remote/eblake/coreutils/tests gt-stat-mount.XXXX
+++ case $# in
+++ destdir_=/home/remote/eblake/coreutils/tests
+++ template_=gt-stat-mount.XXXX
+++ MAX_TRIES_=4
+++ case $destdir_ in
+++ case $template_ in
+++ fail=0
++++ unset TMPDIR
++++ mktemp -d -t -p /home/remote/eblake/coreutils/tests gt-stat-mount.XXXX
+++ d=/home/remote/eblake/coreutils/tests/gt-stat-mount.jXje
+++ case $d in
+++ test -d /home/remote/eblake/coreutils/tests/gt-stat-mount.jXje
++++ ls -dgo /home/remote/eblake/coreutils/tests/gt-stat-mount.jXje
++++ tr S -
+ create_exe_shims_ /home/remote/eblake/coreutils/src
+ case $EXEEXT in
+ return 0
+ shift
+ test 0 '!=' 0
+ export PATH
++ df -P .
++ sed -n '2s/.* \([^ ]*$\)/\1/p'
+ df_mnt=/shared
++ stat -c%m .
+ stat_mnt=/shared/home
+ test /shared = /shared/home
+ fail=1
+ Exit 1
+ set +e
+ exit 1
+ exit 1
+ remove_tmp_
+ __st=1
+ cleanup_
+ :
+ cd /home/remote/eblake/coreutils/tests
+ chmod -R u+rwx /home/remote/eblake/coreutils/tests/gt-stat-mount.jXje
+ rm -rf /home/remote/eblake/coreutils/tests/gt-stat-mount.jXje
+ exit 1
Here, the failure is that I have /home bind-mounted on /shared/home, and
since I ran the test under /home, the mount location reported by df is
different than the one reported by stat -c%m. This is a new test, and
I'm not sure what to do about the issue (whether stat needs fixing to
deal with bind mounts, or whether the test is at fault).
--
Eric Blake address@hidden +1-801-349-2682
Libvirt virtualization library http://libvirt.org