From: Andreas K. <and...@ac...> - 2006-09-20 16:34:41
|
I have now committed a change to the run code which uses a different method of execution on windows which doesn't use 'echo', nor 'cat'. I also disabled use of valgrind for that platform. There is no valgrind port for Windows, so the feature is not needed there. > > > Oh: under Cygwin with Tcl 8.4.1, I get an ERR (child process exited > > > abnormally) on a multiplexer test. > > > > I forgot to mention that the tests stop after this! With the rewrite I have no ERR for multiplexer. > > > > > > I entered the command "tclsh sak.tcl test run math", but it went ahead > > > with all modules. > > > > > > > It seems to be ignoring the module argument ... Which is a pity I tried my rewrite and it is good for me, i.e. not ignoring the modules and running only the specified testsuites. > > > On Windows it fails: couldn't execute "echo": no such file or directory > > I thought that this was an artifact of the colorization ... As I > disabled that it can't ... grepping I see > > ./support/devel/sak/test/run.tcl:152: lappend cmd echo [join $script \n] > > and now remember: I use 'echo' to infect the script into the > subprocess running the testsuite. This construction is needed to get > the execution under valgrind right, and I decided to use it for the > regular startup as well. As valgrind is not relevant under Windows I > better rewrite things for windows to not use the echo-construction. > > > > > > Not a new complaint. > > But only now fully recognized where the problem is. -- Andreas Kupries <and...@Ac...> Developer @ http://www.ActiveState.com Tel: +1 778-786-1122 |