Zsh Mailing List Archive
Messages sorted by:
Re: Test suite failures on GNU Hurd: Test ../../Test/C02cond.ztst failed: bad status 1, expected 0
- X-seq: zsh-workers 31776
- From: Axel Beckert <abe@xxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: Test suite failures on GNU Hurd: Test ../../Test/C02cond.ztst failed: bad status 1, expected 0
- Date: Tue, 1 Oct 2013 13:19:14 +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: <130618213620.ZM18097@torch.brasslantern.com>
- List-help: <mailto:firstname.lastname@example.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:email@example.com>
- 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: <20130618230807.GM30957@sym.noone.org> <130618213620.ZM18097@torch.brasslantern.com>
On Tue, Jun 18, 2013 at 09:36:20PM -0700, Bart Schaefer wrote:
> On Jun 19, 1:08am, Axel Beckert wrote:
> } So I wonder: Why does the test suite fail while -c seems to work fine
> } on the command line on GNU Hurd?
> I'm just guessing, but I suspect that because the automated build
> process doesn't have a terminal, then /dev/tty doesn't stat as a char
> device. Yes, I know that seems unlikely.
We've added a patch which uses the same technique as the -b test case
for finding a suitable tty device:
find /dev/ -nowarn -maxdepth 1 -name 'tty*' -type c -print
Interestingly that yielded the following error mesage:
find: `/dev/tty': No such device or address
So it seems to me that if you run a process without controlling
terminal on Hurd, find sees /dev/tty as directory entry, but gets an
error when it tries to stat() it for the "-type c" check.
I was able to prove this theory by connecting to a machine running
Debian GNU/Hurd by ssh but deliberately without a controlling terminal:
% ssh exodar.debian.net "ls -l /dev/" | grep 'tty$'
ls: cannot access /dev/tty: No such device or address
?????????? ? ? ? ? ? tty
This acutally looks like a bug in either libc on Hurd or the Hurd
kernel itself. So it's nothing that zsh should bother (except for the
failing tests of course :-).
> Someone with access to the build could try replacing /dev/tty with
> /dev/zero or /dev/random in that test; if that "fixes" it, then the
> problem is with the implementation of /dev/tty ...
Yes, that'd be my try for the next zsh upload to Debian.
(Actually I wanted to point out here that connecting to a buildd with
SSH gives your a controlling terminal when I remembered that it
doesn't give you a terminal by default if you pass a command as
parameter and suddenly I knew how to test the issue and so you've got
the details above. :-)
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.asciiribbon.org/ | abe@xxxxxxxxx (Mail+Jabber)
/ \ I love long mails: http://email.is-not-s.ms/ | http://noone.org/abe/ (Web)
Messages sorted by: