From: Denys Vlasenko <vda.linux@googlemail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
busybox <busybox@busybox.net>, Ron Yorston <rmy@pobox.com>,
dash@vger.kernel.org
Subject: dash tested against ash testsuite: 17 failures
Date: Sat, 1 Oct 2016 19:17:12 +0200 [thread overview]
Message-ID: <CAK1hOcMma=uH2R=vWX1Z6r2xf9PcW7MPSEPYOk76Zn97LD-7Jw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2341 bytes --]
ash-signals/savetrap.tests
While trying to port some fixes from dash,
one of them broke some signal handling testcases.
I guess some of things we test for are not tested
by dash developers.
I ran entire ash testsuite against dash, deleted failing
things which dash does not support (some bashisms),
and false positives caused by differences in error
messages.
What's left is:
ash-glob/glob2.tests:
Evidently, dash supports \f -> ^L escape.
This test uses \f as invalid backslash escape,
hence differences.
ash-misc/echo_write_error.tests
EPIPE errors in echo are not reported
ash-misc/func2.tests
$((i++)) not supported
ash-misc/local1.tests
Doesn't unset as described:
local a
# the above line unsets $a
echo "A2:'$a'"
ash-misc/shift1.tests
"shift N" fails if fewer than N argv[i] exists
(likely not a bug, but bash does it differently)
ash-redir/redir.tests
echo errors due to closed stdout are not reported
ash-redir/redir3.tests
"echo foo >&9" correctly says "9: Bad file descriptor"
and exitcode is 2 (in bash, it is 1).
ash-redir/redir7.tests
ash-redir/redir8.tests
uni\x81code filename is not found by uni?code glob pattern.
ash-signals/reap1.tests
Builtins never wait for children. This loop will not ever stop:
sleep 1 &
PID=$!
while kill -0 $PID >/dev/null 2>&1; do
true
done
ash-signals/savetrap.tests
`trap` does not work as expected
ash-signals/sigint1.tests
trap "exit 0" SIGINT - does not like name "SIGINT". "INT" works.
ash-signals/signal4.tests
trap "echo Trapped" BADNAME TERM - abort seeing BADNAME.
bash complains, but sets the trap for the second signal.
ash-signals/signal8.tests
"kill %1" in non-interactive shell does not find
previously backgrounded task.
ash-vars/var-utf8-length.tests
${#VAR} counts unicode chars in bash
ash-vars/var_unbackslash.tests
b=-$a-\t-\\-\"-\`-\--\z-\*-\?-
b="-$a-\t-\\-\"-\`-\--\z-\*-\?-"
b='-$a-\t-\\-\"-\`-\--\z-\*-\?-'
b1=$b
"b1=$b"
You can imagine... not everything went well here...
ash-vars/var_unbackslash.tests
echo Forty two:$\
(\
(\
42\
)\
)
dash says: Syntax error: Missing '))'
The tarball is attached. Unpack, add an ash -> /path/to/your/dash
symlink, then run ./run-all
[-- Attachment #2: ash_test.tar.gz --]
[-- Type: application/x-gzip, Size: 13851 bytes --]
next reply other threads:[~2016-10-01 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-01 17:17 Denys Vlasenko [this message]
2016-10-08 19:42 ` dash tested against ash testsuite: 17 failures Martijn Dekker
2016-10-10 20:20 ` Harald van Dijk
2016-10-12 17:24 ` Harald van Dijk
2016-10-10 21:51 ` Jilles Tjoelker
2016-10-10 22:30 ` Harald van Dijk
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='CAK1hOcMma=uH2R=vWX1Z6r2xf9PcW7MPSEPYOk76Zn97LD-7Jw@mail.gmail.com' \
--to=vda.linux@googlemail.com \
--cc=busybox@busybox.net \
--cc=dash@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=rmy@pobox.com \
/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.
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).