On Thu, 12 Aug 2010 16:23:53 +0200 Elias Pipping wrote:
> indeed, the ksh from PATH I had installed was causing this.
> Uninstalling it made everything work. The test suite complains about
good
> basic.sh[437]: ~/build/arch/linux.i386-64/bin/cat: not found [No such
> file or directory]
> and
> path.sh[172]: ~/build/arch/linux.i386-64/bin/chmod: not found [No such
> file or directory]
> by the way. As a result, some tests are skipped. Should those files be
> created as symlinks to /bin/cat and /bin/chmod automatically or should
> I be creating those?
these are assumption bugs in our test scripts -- they will be fixed
in the next release, due out later today
> Also,
> test shcomp-signal.ksh begins at 2010-08-12+16:01:54
> shcomp-signal.ksh[296]: kill -TERM $$ failed, required
> termination by signal 'KILL'
> test shcomp-signal.ksh failed at 2010-08-12+16:03:11 with exit code 1
> [ 35 tests 1 error ]
this looks like a problem
re-check with the next release before spending time on it
> looks like a test failure but the exit status of `bash bin/package
> only test ast-ksh` is zero. Is that intentional?
test regressions are noted by the string "FAILURE" in the test logs
a regression does not cause non-0 exit status
this is so the build system { "nmake test" "bin/package test" }
can differentiate test harness failures and regressions
> Since the ksh that had a memory fault here was ast-ksh 2010.07.01 as
> well, there appears to be a problem. I'll report back once I've looked
> into it a bit more.
I believe we have nailed the problem already for the next release
try that before spending time on it
_______________________________________________
ast-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-users
