Twice recently, once on x86_64 and once on i686, zsh has failed its testsuite while being built by hydra. Here's the output in both cases:
Toggle snippet (28 lines)
Test ./C02cond.ztst failed: bad status 1, expected 0 from: print -u $ZTST_fd 'This test takes two seconds...' sleep 2 cat unmodified touch newnewnew if [[ $OSTYPE == "cygwin" ]]; then print -u$ZTST_fd "Warning: not testing [[ -N file ]] (not supported on Cygwin)" true elif [[ "$(find . -prune -fstype nfs 2>/dev/null)" == "." ]]; then print -u$ZTST_fd "Warning: not testing [[ -N file ]] (not supported with NFS)" true elif test -f /etc/mtab && { grep $(df . 2>/dev/null| tail -n1 | awk '{print $1}') /etc/mtab | grep -q noatime; }; then print -u$ZTST_fd "Warning: not testing [[ -N file ]] (not supported with noatime file system)" true else [[ -N newnewnew && ! -N unmodified ]] fiWas testing: -N cond./C02cond.ztst: test failed.The following may (or may not) help identifying the cause: This test can fail on NFS-mounted filesystems as the access and modification times are not updated separately. The test will fail on HFS+ (Apple Mac OS X default) filesystems because access times are not recorded. Also, Linux ext3 filesystems may be mounted with the noatime option which does not update access times. Failures in these cases do not indicate a problem in the shell.
I restarted the x86_64 build and it succeeded on the second try.Now it has failed on i686: http://hydra.gnu.org/build/128208My first guess is that one of our build machines has the 'noatime' mountoption set on its /tmp.Is there a way to tell from the URL above which build machine was used? Mark