zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>,
	"ZSH Workers Mailing List" <zsh-workers@sunsite.dk>
Subject: Re: PATCH: Block device tests
Date: Sun, 27 May 2001 22:54:20 +0000	[thread overview]
Message-ID: <1010527225420.ZM1568@candle.brasslantern.com> (raw)
In-Reply-To: <000301c0e5bd$558b0e10$21c9ca95@mow.siemens.ru>

On May 26, 12:24pm, Andrej Borsenkow wrote:
} Subject: RE: PATCH: Block device tests
}
} This broke test on my system where find returns 1 even if files were found;
} I fixed this but then got errors in next test (char devices). I fixed this
} but got errors in mkfifo test. It is pointless - we need general "not
} implemented" framework for test harness.

Not finding any block (or character) devices because /dev is inaccessible
to nonprivileged users -- which has been the cause of at least a few of
the device test failures reported -- is not the same as "not implemented"
(which is presumably the issue with mkfifo on ReliantUNIX).

Further, I don't see any alternative to editing each test chunk even if
there were a not-implemented framework.

Could we use a grep of config.h as the not-implemented test?

} +  block=$(find /dev(|ices)/ -type b -print 2> /dev/null)

You don't need the 2>/dev/null any more -- the test condition is `0D:',
which means to ignore the error output and use only the exit status in
determining whether the test succeeded.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2001-05-27 22:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-22 15:14 Almost all tests pass under new cygwin Andrej Borsenkow
2001-05-22 15:24 ` Andrej Borsenkow
2001-05-22 15:31 ` Bart Schaefer
2001-05-22 15:44   ` Oliver Kiddle
2001-05-23 16:51     ` About zmodload test segfaults Bart Schaefer
2001-05-24 12:15       ` Andrej Borsenkow
2001-05-25 16:54         ` PATCH: Block device tests Bart Schaefer
2001-05-26  8:24           ` Andrej Borsenkow
2001-05-27 22:54             ` Bart Schaefer [this message]
2001-05-28  6:50               ` Andrej Borsenkow
2001-05-28 16:06                 ` Bart Schaefer
2001-05-28 17:25                   ` Bart Schaefer
2001-05-29 10:34                   ` Peter Stephenson
2001-05-29 10:51                     ` Andrej Borsenkow
2001-05-29 15:37                       ` Bart Schaefer
2001-05-30  9:21                         ` Peter Stephenson
2001-05-28  9:21       ` About zmodload test segfaults Sven Wischnowsky
2001-05-22 15:53   ` Almost all tests pass under new cygwin Andrej Borsenkow
2001-05-23 11:40 ` Peter Stephenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1010527225420.ZM1568@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=Andrej.Borsenkow@mow.siemens.ru \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).