On QNX, do not run the tests involving /bin/ed at all, because it appears

oldish but is in fact broken. However, if /bin/ed is MirBSD ed(1), these
actually pass.
This commit is contained in:
tg 2008-11-02 23:03:45 +00:00
parent 17ecb986c8
commit 6e490218ca
1 changed files with 4 additions and 4 deletions

View File

@ -1,4 +1,4 @@
# $MirOS: src/bin/mksh/check.t,v 1.238 2008/11/02 22:29:35 tg Exp $
# $MirOS: src/bin/mksh/check.t,v 1.239 2008/11/02 23:03:45 tg Exp $
# $OpenBSD: bksl-nl.t,v 1.2 2001/01/28 23:04:56 niklas Exp $
# $OpenBSD: history.t,v 1.5 2001/01/28 23:04:56 niklas Exp $
# $OpenBSD: read.t,v 1.3 2003/03/10 03:48:16 david Exp $
@ -2205,7 +2205,7 @@ description:
Basic (ed) editing works (assumes you have generic ed editor
that prints no prompts). This is for oldish ed(1) which write
the character count to stdout.
category: oldish-ed
category: oldish-ed,!os:nto
arguments: !-i!
env-setup: !ENV=./Env!HISTFILE=hist.file!
file-setup: file 644 "Env"
@ -2227,7 +2227,7 @@ expected-stderr-pattern:
name: history-ed-2-old
description:
Correct command is edited when number given
category: oldish-ed
category: oldish-ed,!os:nto
arguments: !-i!
env-setup: !ENV=./Env!HISTFILE=hist.file!
file-setup: file 644 "Env"
@ -2258,7 +2258,7 @@ description:
in history.
(NOTE: adjusted for COMPLEX HISTORY compile time option)
(ksh88 fails 'cause it lists the fc command)
category: oldish-ed
category: oldish-ed,!os:nto
arguments: !-i!
env-setup: !ENV=./Env!HISTFILE=hist.file!
file-setup: file 644 "Env"