On Sat, Nov 11, 2017 at 3:39 PM, Bruno Haible <br...@clisp.org> wrote: > Test results of gzip git of today + gnulib git of today (only 32-bit > platforms): > > On > FreeBSD/i386: > Haiku/i386: > HP-UX/hppa: > HP-UX/ia64: > > FAIL: help-version
Thanks, Bruno. The FreeBSD failure looks like it is due to "more" not detecting write failure when its output is redirected to /dev/full (in the zmore test). The Haiku failure is due to gzexe failing due to that system's lack of hard link support: + eval 'env $i in-6369 < $tmp_in > $tmp_out' ++ env gzexe in-6369 in-6369: -15.4% ln: failed to create hard link 'in-6369~' => 'in-6369': Operation not supported /boot/home/gzip-1.8.41-9d3bb-dirty/build/tests/../gzexe: cannot backup in-6369 as in-6369~ + echo FAIL: gzexe FAIL: gzexe + fail=1 On hppa, the test that runs `gunzip --help > /dev/full` fails unexpectedly. It should run only on a system with writable "char" device /dev/full, and it should fail like this: $ gunzip --help > /dev/full echo: write error: No space left on device [Exit 1] But on your system, it exits with status 2. The other hppa failures may be similar: $ grep '^\*' test-suite.hpux-hppa|sort -u *** gunzip: bad exit status `2' (expected 1), *** gzexe: bad exit status `2' (expected 1), *** zcat: bad exit status `2' (expected 1), *** zcmp: bad exit status `0' (expected 2), *** zdiff: bad exit status `0' (expected 2), *** zegrep: bad exit status `0' (expected 2), *** zfgrep: bad exit status `0' (expected 2), *** zforce: bad exit status `2' (expected 1), *** zgrep: bad exit status `0' (expected 2), *** zless: bad exit status `2' (expected 1), *** zmore: bad exit status `0' (expected 1), *** znew: bad exit status `2' (expected 1),
