zsh test suite failures, possibly due to 'noatime' mount flag

OpenSubmitted by Mark HWeaver.
4 participants
  • Joshua Branson
  • Maxim Cournoyer
  • Mark HWeaver
  • Vincent Legoll
Mark HWeaver wrote on 26 Oct 2014 02:22
(address . bug-guix@gnu.org)
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:
My 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?
Joshua Branson wrote on 17 Mar 2017 20:56
zsh test suite failures, possible due to 'noatime' mount flag
(name . 18838@debbugs.gnu.org)(address . 18838@debbugs.gnu.org)
This is still an issue. The last two builds for i686 and arm appear to have been built fine.
But MIPS and x86_64 both have recent failures.
Vincent Legoll wrote on 5 Mar 2020 11:35
Re: zsh test suite failures
(address . 18838@debbugs.gnu.org)
Is this still happening?
I searched a bit on ci.guix.gnu.org...
We have a failure on 5.8 armhf (already present on 5.7.1 version)but it looks like it is a different set of tests that is failing...
-- Vincent Legoll
Maxim Cournoyer wrote on 9 Oct 2020 16:57
Re: bug#18838: zsh test suite failures
(name . Vincent Legoll)(address . vincent.legoll@gmail.com)(address . 18838@debbugs.gnu.org)
Vincent Legoll <vincent.legoll@gmail.com> writes:
Toggle quote (7 lines)> Is this still happening?>> I searched a bit on ci.guix.gnu.org...>> We have a failure on 5.8 armhf (already present on 5.7.1 version)> but it looks like it is a different set of tests that is failing...
I can't find failures in the raw logs of the last CI failures forzsh-5.8, but testing on master with:
./pre-inst-env guix build --check --system=armhf-linux zsh
I got 2 test failures:
Test ./A01grammar.ztst failed: bad status 1, expected 0 from: - $ZTST_testdir/../Src/zsh -fc "[[ \$0 = \"-$ZTST_testdir/../Src/zsh\" ]]"Was testing: `-' precommand modifier./A01grammar.ztst: test failed../A02alias.ztst: starting.This test hangs the shell when it fails..../A02alias.ztst: all tests successful../A03quoting.ztst: starting../A03quoting.ztst: all tests successful../A04redirect.ztst: starting../A04redirect.ztst: all tests successful../A05execution.ztst: starting.Unable to change MONITOR optionThis test takes 5 seconds to fail...Skipping pipe leak test, requires MONITOR optionThis test takes 3 seconds and hangs the shell when it fails..../A05execution.ztst: all tests successful../A06assign.ztst: starting../A06assign.ztst: all tests successful../A07control.ztst: starting../A07control.ztst: all tests successful../B01cd.ztst: starting.Test ./B01cd.ztst failed: bad status 0, expected 1 from: (unset HOME; ARGV0=sh $ZTST_testdir/../Src/zsh -c cd)Was testing: Implicit cd with unset HOME.