bug-coreutils
[Top][All Lists]
Advanced

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

Re: make check for coreutils-7.2 fails


From: Sergei Steshenko
Subject: Re: make check for coreutils-7.2 fails
Date: Wed, 1 Apr 2009 08:33:40 -0700 (PDT)



--- On Wed, 4/1/09, Jim Meyering <address@hidden> wrote:

> From: Jim Meyering <address@hidden>
> Subject: Re: make check for coreutils-7.2 fails
> To: "Sergei Steshenko" <address@hidden>
> Cc: address@hidden
> Date: Wednesday, April 1, 2009, 8:03 AM
> Jim Meyering wrote:
> > Sergei Steshenko wrote:
> >> please find 'make check' screen output attached.
> There was no failure on the same machine under the same OS
> (SUSE 10.3) for coreutils-7.1.
> >>
> >> FAIL: mv/i-3.log (exit: 1)
> >> ==========================
> > ...
> >> + ls /dev/stdin
> >> + mv f g
> >> ./mv/i-3: line 38: /dev/stdin: Permission denied
> >
> > Thanks for the report.
> > It failed because your /dev/stdin is not readable.
> > The patch below makes is so that test will now be
> skipped in
> > that situation.
> >
> >>From 72e01aeb6ec4999f3f6ce72fd35671a65cacfc69 Mon
> Sep 17 00:00:00 2001
> > From: Jim Meyering <address@hidden>
> > Date: Wed, 1 Apr 2009 16:59:54 +0200
> > Subject: [PATCH] tests: skip mv/i-3 if /dev/stdin is
> unreadable
> >
> > * tests/mv/i-3: Skip if /dev/stdin is unreadable.
> > Reported by Sergei Steshenko.
> > ---
> >  tests/mv/i-3 |    3 +++
> >  1 files changed, 3 insertions(+), 0
> deletions(-)
> >
> > diff --git a/tests/mv/i-3 b/tests/mv/i-3
> > index d1f119c..738605b 100755
> > --- a/tests/mv/i-3
> > +++ b/tests/mv/i-3
> > @@ -35,6 +35,9 @@ fail=0
> >  ls /dev/stdin >/dev/null 2>&1 \
> >    || skip_test_ 'there is no /dev/stdin
> file'
> >
> > +test -r /dev/stdin 2>&1 \
> > +  || skip_test_ '/dev/stdin is not readable'
> > +
> 
> Oops.
> No need for redirection:
> 
>   +test -r /dev/stdin \
> 

Could you please prepare a new full tarball, like, say, coreutils-7.2a ?

The point is I have my own tool (AppsFromScratch) which downloads the 
source and builds stuff automatically, i.e. I am not building the stuff
manually.

I can, of course, add a piece of code which applies patches, but the next
release there will be no patch, so I'll write the code for nothing

So, if you just prepare the tarabll suitable for the standard

./configure
make
make check
make install

sequence, I'll be able to check without adding any code, just changing the
version.

Thanks,
  Sergei.







reply via email to

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