Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [PATCH] [long] typeset doesn't report tied parameters (and related issues)
- X-seq: zsh-workers 43629
- From: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
- To: Vin Shelton <acs@xxxxxxxxxxxxxxxxxxxx>
- Subject: Re: [PATCH] [long] typeset doesn't report tied parameters (and related issues)
- Date: Mon, 8 Oct 2018 15:10:55 +0100
- Cc: Zsh Hackers' List <zsh-workers@xxxxxxx>
- Cms-type: 201P
- Dkim-filter: OpenDKIM Filter v2.11.0 mailout1.w1.samsung.com 20181008141058euoutp014a3429f6fe5ddc9a2f9e74d8fb4f8744~bp35JoI-23179731797euoutp01w
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsung.com; s=mail20170921; t=1539007858; bh=u267qSutz2C7USBxgCeqgqeU+SbUIcTXihL8DGj0mOY=; h=Subject:From:To:CC:Date:In-Reply-To:References:From; b=EI2VlVqjQBnOIkitIU/9M0jbPoidbzAIgMxd+Qx4oopRA/vFpkzZNOiv26jADwyX+ 0wDA2j9zFwXrzdmEDad3wSg7tQLOIGFJrp+WucMfkdA6s6DyfCkzQpyXlX4E+BzkSj Rw/gjbFNHFh78xCV138MCmAiqWTd1yaOdH5mEqiA=
- In-reply-to: <CACeGjnUhNqca7jLAR0KKSxobzDd+xXdAe4BeUeRpxu2CTp_zkA@mail.gmail.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- List-unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <20180924210550.carijwjibarjivu4@chaz.gmail.com> <CGME20181007133632epcas5p43a3b4c7f0fe1863478748c5cf46ce8ef@epcas5p4.samsung.com> <20181007133545.zzkrbc3ed6shnk3e@chaz.gmail.com> <20181008090557eucas1p11f18ef9ca4a6e3cc09fd59242f344f96~bltk3bsqO1947719477eucas1p1q@eucas1p1.samsung.com> <CACeGjnUhNqca7jLAR0KKSxobzDd+xXdAe4BeUeRpxu2CTp_zkA@mail.gmail.com>
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?
pws
Messages sorted by:
Reverse Date,
Date,
Thread,
Author