On Tuesday, October 12, 2010 00:08:12 Glenn Fowler wrote: > the AT&T Software Technology ast beta 2010-10-10 source release > has been posted to the download site > http://www.research.att.com/sw/download/beta/
Is it expected that beta version passes all shtests? > basic.sh[438]: early termination not causing broken pipe > test functions(shcomp) begins at 2010-10-12+08:24:56 > Usage: kill [-l] [-n signum] [-s signame] job ... > Or: kill [ options ] -l [arg ...] > test functions(shcomp) passed at 2010-10-12+08:25:02 [ 96 tests 0 errors ] > test signal begins at 2010-10-12+08:28:21 > signal.sh[55]: pipe with --pipefail PIPE trap hangs > signal.sh[296]: kill -PIPE $$ failed, required termination by signal 'KILL' > test signal failed at 2010-10-12+08:29:53 with exit code 2 [ 37 tests 2 errors ] Odd is when I start tests manualy all of them works, but when started automaticaly during the rpm build process they fail. I'll try to find out what's the difference. ------------------------------------------ > locale.sh[269]: LANG change not seen by function -- expected $'(libshell,3,46)\nAn error occurred.\n(libshell,3,46)' or $'(debug,message,libshell,"An error occurred.")\nAn error occurred. \n(debug,message,libshell,"An error occurred.")', got $'(debug,message,libshell,An error occurred.)\nAn error occurred. \n(debug,message,libshell,An error occurred.)' this one ^^^ seems odd, because this tests expects: $'(debug,message,libshell,"An error occurred.")... ---- (string with double quotes) but latest tests looking almost the same way expects: yyy(debug,'$Command',libshell,hello " fish\)xx ---- (string without double quotes) are these tests executed always before new stable/beta release or just time to time? _______________________________________________ ast-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-users
