Re: Testsuite failures in A05execution inside Jenkins, but not locally (was: zsh 5.0.8.-test-3)

[Bart Schaefer <schaefer@brasslantern.com>]

On Aug 26,  3:58pm, Axel Beckert wrote:
}
} But I had test suite failures when being build inside a Jenkins job.
} Doesn't seem to be caused by the zsh updated though as the most recent
} 5.0.8 build failed at the very same test:
} 
} + (eval):printf:4: write error: broken pipe
} + (eval):4: write error: inappropriate ioctl for device
} + cat: write error: Broken pipe
} + hang:printf: write error: broken pipe
} + hang: write error: inappropriate ioctl for device
} Was testing: Bug regression: piping a shell construct to an external process may hang


Those broken pipe errors are irrelevant to the test (in fact they're the
expected reason for the printf and cat processes to terminate, but under
normal circumstances that doesn't print an error).  So I think we can
safely throw them away.

Consequently, does this fix it?


diff --git a/Test/A05execution.ztst b/Test/A05execution.ztst
index d5501bb..d9e6409 100644
--- a/Test/A05execution.ztst
+++ b/Test/A05execution.ztst
@@ -207,7 +207,7 @@ F:This similar test was triggering a reproducible failure with pipestatus.
   coproc { read -et 5 || { print -u $ZTST_fd KILLED; kill -HUP -$$ } }
   print -u $ZTST_fd 'This test takes 5 seconds to fail...'
   { printf "%d\n" {1..20000} } | ( read -e )
-  hang(){ printf "%d\n" {2..20000} | cat }; hang | ( read -e )
+  hang(){ printf "%d\n" {2..20000} | cat }; hang 2>/dev/null | ( read -e )
   print -p done
   read -et 6 -p
 0:Bug regression: piping a shell construct to an external process may hang