bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

test failures for "make check < /dev/null"


From: Paul Jarc
Subject: test failures for "make check < /dev/null"
Date: Tue, 10 Sep 2002 18:26:27 -0400
User-agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i686-pc-linux-gnu)

Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' 
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' 
-DCONF_VENDOR='pc' -DSHELL -DHAVE_CONFIG_H  -I. 
-I/package/host/localhost/bash-2.05b-3/conf/readline/include -I. -I./include 
-I./lib -I/nil -I/package/host/localhost/bash-2.05b-3/conf/readline/include 
-I/package/host/localhost/bash-2.05b-3/conf/ncurses/include -O2 -pipe
uname output: Linux multivac.cwru.edu 2.4.19 #1 SMP Mon Aug 5 11:15:13 EDT 2002 
i686 unknown
Machine Type: i686-pc-linux-gnu

Bash Version: 2.05b
Patch Level: 0
Release Status: release

I've applied patches 1-4, and I get these test failures if I run "make
check" with stdin redirected from /dev/null:

run-read
37c37
< 
---
> 4
39c39
< 
---
> 4
42c42
< 
---
> 4

run-test
58c58
< 1
---
> 0

It happens that I redirected stdin from /dev/null just to work around
the "test -r /dev/stdin" bug in configure, but I think the tests
shouldn't care anyway.  If the properties of stdin are important, the
test scripts should redirect stdin appropriately themselves, rather
than assuming.


paul




reply via email to

[Prev in Thread] Current Thread [Next in Thread]