On Sun, Oct 14, 2012 at 9:11 PM, Roland Mainz <[email protected]> wrote:
> On Sat, Oct 13, 2012 at 4:40 PM, Glenn Fowler <[email protected]> wrote:
>> ast-ksh 2012-10-12 alpha posted
>
> In general the alpha looks very good. There seems to be no new
> critical gcc warnings, interactive testing with builtin grep looks OK
> (e.g. we tested job control and repeated CTRL-C usage for grep -r
> etc.) and Solaris uses |posix_spawn()| without problems.
[snip]
> More testing is currently underway...
On Solaris 11/B134/SPARC I stumbled over this test failure:
-- snip --
test sun_solaris_compound_nameref begins at 2012-10-14+22:09:44
sun_solaris_compound_nameref.sh[114]: shell returned exit code 127
sun_solaris_compound_nameref.sh[145]: shell returned exit code 127
sun_solaris_compound_nameref.sh[175]: shell returned exit code 127
sun_solaris_compound_nameref.sh[200]: shell returned exit code 127
sun_solaris_compound_nameref.sh[231]: shell returned exit code 127
test sun_solaris_compound_nameref failed at 2012-10-14+22:09:46 with
exit code 5 [ 31 tests 5 errors ]
-- snip --
... after some testing I reduced this to:
-- snip --
SHELL=~/bin/ksh
{
cat <<EOF
print OK
exit 0
EOF
} | out=$( ${SHELL} 2>&1 )
out2="${out}$?"
if [[ "$out2" == 'OK0' ]] ; then
print 'SUCCESS.'
else
printf 'Expected "OK0", got %q\n' "$out2"
-- snip --
... the test should print "SUCCESS." but currently prints "OK127" on
both Solaris 11/B134/SPARC/64bit and SuSE 12.2/Linux/AMD64/64bit...
which means the command substitution returns an exit code of 127.
----
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) [email protected]
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 3992797
(;O/ \/ \O;)
_______________________________________________
ast-developers mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-developers
