Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: zpty-related testsuite failures if building in a chroot on a host running systemd 220 as init system
- X-seq: zsh-workers 35397
- From: Axel Beckert <abe@xxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: zpty-related testsuite failures if building in a chroot on a host running systemd 220 as init system
- Date: Fri, 5 Jun 2015 17:29:33 +0200
- Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAAAAAC3mUtaAAAABGdBTUEAALGPC/xhBQAAADh0RVh0U29mdHdhcmUAWFYgVmVyc2lvbiAzLjEwYSAgUmV2OiAxMi8yOS85NCAoUE5HIHBhdGNoIDEuMindFS5JAAACGElEQVQ4jXXQMU8UYRDG8f8shNjdDH4AbpfGDjAWlKiJiZ0ajL1aGCvsNCbGaCGG1koLaztaTYz6ATy+gOyehYmF3MxVxgg3FnDsHcTpJr/M+8w7Rf6nCsaVTTDqxbg9hoOXmw83H71+Eyfg4E1d7/Z2fG9rGkZbTQiu+K+3U/C+76lmkvAhJuDndnoAiftou4V84okAGclop4U/jYACZDTxrYWP0gkxVfAm/W//GLZpxIzwIN0Hn8dw0B+IWkZmQmRsj2HfhwokEklHfNCCiQCRgAR7YyhQVRVTCKCzP4Y5zBBE0t0zY3Q8oQaBqqAMlVEcgVQd9706zGirAFium8HXumlMIeMwqQCInju+2+uB6MRENupdpMt8pRlHZyuAW0F+Mb6XSIVqtxjD+iVmVqqystLEzFTGT92YqRaXpNT5eTVjeJhbALPnrTxLUZUKZsgxcNm64hAOYisT/xhF+oKTGU5RegtC3Rt6eEDi/QnIevdTx9Md2EMmYBRmCQR1026FCGQQJJExsRUqgkMGaWSbwYLnoO4T6VgpbQbdELPMBAHWWrhYrcxXnYgAsatPWygkFCBD4K62MAsOTqA6szYRPpsu6e6Y8mPiVrBMNuGIMrgwBUu4p2DgG1Ownu6hpuTv7hScefHAzAC/yRRw5U5pALMbJ4AUALvHSZhxgHPXTsHcdWD1GadAHr9avP+c0wCr7263Df8ASLwXWHWs+KIAAAAHdElNRQfYBQEBODPr
- In-reply-to: <20150605150211.GX4744@sym.noone.org>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mail-followup-to: zsh-workers@xxxxxxx
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- Organization: DeuxChevaux.org -- The Citroën 2CV Database
- References: <20150605150211.GX4744@sym.noone.org>
Hi,
some more details:
On Fri, Jun 05, 2015 at 05:02:12PM +0200, Axel Beckert wrote:
> while trying to prepare an official Debian package of zsh 5.0.8 I ran
> into interesting test suite failures which only happen under very
> specific circumstances:
I've also tried 5.0.7-dev-2 and 5.0.7-dev-4 -- no difference.
> ../../Test/V08zpty.ztst: starting.
> Running test: zpty with a process that does not set up the terminal: internal write
> Test ../../Test/V08zpty.ztst failed: bad status 1, expected 0 from:
> zpty cat cat
> zpty -w cat a line of text
> var=
> zpty -r cat var && print -r -- ${var%%$'\r\n'}
> zpty -d cat
> Error output:
> (zpty):zpty:1: can't open pseudo terminal: no such file or directory
> (eval):zpty:2: no such pty command: cat
> (eval):zpty:4: no such pty command: cat
> (eval):zpty:5: no such pty command: cat
[...]
> 39 successful test scripts, 5 failures, 0 skipped
While these failures sound similar to what Baptiste Daroussin wrote in
35355 (http://www.zsh.org/mla/workers/2015/msg01279.html, both times 5
zpty-related tests), the fix from Oliver Kiddle in 35360
(http://www.zsh.org/mla/workers/2015/msg01284.html) didn't change
anything for me.
Kind regards, Axel
--
/~\ Plain Text Ribbon Campaign | Axel Beckert
\ / Say No to HTML in E-Mail and News | abe@xxxxxxxxxxxxxxx (Mail)
X See http://www.nonhtmlmail.org/campaign.html | abe@xxxxxxxxx (Mail+Jabber)
/ \ I love long mails: http://email.is-not-s.ms/ | http://abe.noone.org/ (Web)
Messages sorted by:
Reverse Date,
Date,
Thread,
Author