Re: [PATCH] [long] typeset doesn't report tied parameters (and related issues)

[Daniel Shahaf <d.s@daniel.shahaf.name>]

Peter Stephenson wrote on Mon, 08 Oct 2018 15:10 +0100:
> On Mon, 2018-10-08 at 09:58 -0400, Vin Shelton wrote:
> > I'm now seeing 2 failures on my Sparky (Debian) system.  I'm not seeing
> > these failures on my Fedora28 VM.
> 
> Hmm, that looks like it's got something to do with your particular set
> up, which isn't to see there's no problem in the build/test system
> either.  In one case there's no good reason why you should get the wrong
> status, and I don't think it's down to the basic shell internals (it
> could be a knock-on effect from the test, e.g. what's in the
> environment).  In the other it seems to think you're running as
> root.  Is this from a clean build?

I see a failure in a clean build on Debian stretch

[[[
Test /home/daniel/src/zsh/./Test/V10private.ztst failed: bad status 139, expected 0 from:
 if (( UID )); then
   ZTST_verbose=0 $ZTST_exe +Z -f $ZTST_srcdir/ztst.zsh private.TMP/B02
 else
   ZTST_skip="cannot re-run typeset tests when tests run as superuser"
 fi
Was testing: typeset still works with zsh/param/private module loaded
]]]

It then says "2 failures, 2 skipped" even though no other failures are
listed in the output.

This is with --enable-zsh-debug and modules compiled statically, if that matters.