From: Christophe R. <cs...@ca...> - 2006-01-15 18:29:21
|
Nathan Froyd <nf...@us...> writes: > Update of /cvsroot/sbcl/sbcl/contrib/sb-posix > In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv6965/contrib/sb-posix > > Modified Files: > constants.lisp defpackage.lisp designator.lisp interface.lisp > macros.lisp posix-tests.lisp > Log Message: > 0.9.8.35: > Add getpwnam and getpwuid to SB-POSIX... > * ...in a fit of frustration ("why does this work in sb-bsd-sockets > and the exact same thing not work here?"), remove the > SB-POSIX-INTERNAL package and throw everything into SB-POSIX. > No more lurking issues with packages. It appears that this change has an effect on the SBCL regression tests, at least on x86/linux. Empirically, on x86/linux, versions 0.9.8.35 and later suffer failure in mop-[347].impure-cload.lisp when run as part of the complete regression test suite sh ./run-tests.sh They do _not_ fail if run in isolation sh ./run-tests.sh mop-3.impure-cload.lisp or even as part of a large group of tests sh ./run-tests.sh clos* mop* The failure mode, if run with sh ./run-tests.sh --break-on-failure seems to be a vicious metacircle, which at least makes a certain amount of sense, as the three test files in question are indeed those with multiple subclasses of standard-generic-function; however, the fact that they don't fail in isolation but do as a whole indicates a problem. To add to the confusion, it would appear that sbcl on neither sparc/sunos5.8 nor x86-64/linux suffers from this problem. Additionally, of course, I'm baffled as to how this commit could cause anything like this symptom at all. Ideas? (This is blocking some Win32 merges, so it would be nice to understand the cause soon) Cheers, Christophe |