Re: full-mod-check, socket tests

Hi Sam,

> >> I will enable the modules tests in configure.
> >
> > Please enable only base-mod-check for the moment.
> 
> base-mod-check goes to step5 and full-mod-check to step6,
> summarized at the end.

This is a good move forward, because it will let us see bugs in the modules
more quickly.

However, the rawsock tests on Solaris 10 hang quite often (with more than 50%
probability, and both on sparc and x86). While test failures are acceptable,
a hang is a show-stopper because it blocks the
"make -f Makefile.devel multibuild-..." based testing.

I am therefore forced to disable the full-mod-check for the moment.
(I'm leaving in the --with-module=rawsock option in Makefile.devel, so that
we can at least check whether the rawsock module compiles correctly.)

Now, you can spend time fixing the rawsock module to at least not hang.
Then we can reenable step6 quickly.

Or you can spend time fixing the many test failures of the built-in sockets
which are seen on all non-Linux platforms (see attachment; similar failures
also on Mac OS X and AIX). I would consider this higher priority, because
the built-in sockets are the primary socket API in clisp.

Bruno

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel