[kaffe] CVS kaffe (jim): Added killer process to regression tests to kill tests
PatchSet 3960 Date: 2003/08/18 06:34:45 Author: jim Branch: HEAD Tag: (none) Log: Added killer process to regression tests to kill tests that get hung up (after TIMEOUT seconds). Members: ChangeLog:1.1558-1.1559 test/regression/Makefile.am:1.80-1.81 test/regression/Makefile.in:1.133-1.134 test/regression/TestScript.in:1.37-1.38 Index: kaffe/ChangeLog diff -u kaffe/ChangeLog:1.1558 kaffe/ChangeLog:1.1559 --- kaffe/ChangeLog:1.1558 Sun Aug 17 06:31:12 2003 +++ kaffe/ChangeLog Mon Aug 18 06:34:45 2003 @@ -1,6 +1,18 @@ 2003-08-16 Jim Pick [EMAIL PROTECTED] * test/regression/TestScript.in: + Add TIMEOUT variable and process to kill hung tests. + + * test/regression/Makefile.am: + Suppress shell job control messages caused by killer + process. + + * test/regression/Makefile.in: + Regenerated. + +2003-08-16 Jim Pick [EMAIL PROTECTED] + + * test/regression/TestScript.in: Remove -noverify, since it's turned on globally now. 2003-08-16 Guilhem Lavaux [EMAIL PROTECTED] Index: kaffe/test/regression/Makefile.am diff -u kaffe/test/regression/Makefile.am:1.80 kaffe/test/regression/Makefile.am:1.81 --- kaffe/test/regression/Makefile.am:1.80 Thu Jul 17 14:30:11 2003 +++ kaffe/test/regression/Makefile.am Mon Aug 18 06:34:46 2003 @@ -8,7 +8,9 @@ SETUP_ENVIRONMENT = env `. $(top_builddir)/BUILD_ENVIRONMENT; sed 's/.*export \(.*\)/echo \1=$$\1/' $(top_builddir)/BUILD_ENVIRONMENT | sh` -TESTS_ENVIRONMENT = $(SETUP_ENVIRONMENT) $(SHELL) TestScript +# Redirect errors to /dev/null to avoid annoying job control +# messages from shell when killing tests due to timeouts +TESTS_ENVIRONMENT = $(SETUP_ENVIRONMENT) $(SHELL) TestScript 2 /dev/null ALWAYS_TESTS = \ $(SIMPLE_HEALTH_CHECK) \ Index: kaffe/test/regression/Makefile.in diff -u kaffe/test/regression/Makefile.in:1.133 kaffe/test/regression/Makefile.in:1.134 --- kaffe/test/regression/Makefile.in:1.133 Thu Jul 31 22:47:09 2003 +++ kaffe/test/regression/Makefile.in Mon Aug 18 06:34:46 2003 @@ -243,7 +243,9 @@ SETUP_ENVIRONMENT = env `. $(top_builddir)/BUILD_ENVIRONMENT; sed 's/.*export \(.*\)/echo \1=$$\1/' $(top_builddir)/BUILD_ENVIRONMENT | sh` -TESTS_ENVIRONMENT = $(SETUP_ENVIRONMENT) $(SHELL) TestScript +# Redirect errors to /dev/null to avoid annoying job control +# messages from shell when killing tests due to timeouts +TESTS_ENVIRONMENT = $(SETUP_ENVIRONMENT) $(SHELL) TestScript 2 /dev/null ALWAYS_TESTS = \ $(SIMPLE_HEALTH_CHECK) \ Index: kaffe/test/regression/TestScript.in diff -u kaffe/test/regression/TestScript.in:1.37 kaffe/test/regression/TestScript.in:1.38 --- kaffe/test/regression/TestScript.in:1.37Sun Aug 17 06:31:13 2003 +++ kaffe/test/regression/TestScript.in Mon Aug 18 06:34:47 2003 @@ -17,6 +17,7 @@ # If you want to use jikes as default compiler for the regression tests uncomment the line below. #test -z @JIKES@ || : ${JIKES=@JIKES@ -nowarn} : ${JAVAC=${JIKES-$JAVA at.dms.kjc.Main} -classpath \.$PATHSEP$SRCDIR$PATHSEP$CLASSPATH\} +: ${TIMEOUT=300} overallerror=0 error=0 @@ -67,8 +68,15 @@ RESULT=$1.fail TMPRESULT=$1.tmp $VERBOSE $JAVA $* - $JAVA $* $TMPRESULT 21 + $JAVA $* $TMPRESULT 21 error=$? + pid=$! + $VERBOSE Background pid: $pid + (sleep $TIMEOUT; echo Timeout - $TIMEOUT seconds - killed $TMPRESULT; kill $pid) + killerpid=$! + $VERBOSE Killer process pid: $killerpid with timeout of $TIMEOUT seconds + wait $pid + kill $killerpid if test x$SORT = xyes; then # grep will take care of stripping \r from DOS-like output sort $TMPRESULT | grep '.*' $RESULT ___ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
Re: [kaffe] completed bytecode verifier!
On Friday, August 8, 2003, at 10:22 AM, Timothy Stack wrote:but not CSTATE_LINKED. The subclass would load the superclass using this special getClass(), set its own state to CSTATE_LOADED_SUPER (and NMS_LOADING) and process the superclass to CSTATE_LINKED afterwards. That way, the verifier would be able to properly resolve the subclass while verifying the superclass, but detection of ClassCircularityErrors should still work? I think the circularity checking is broken, its just checking to see if there is a loop in calls to loadClass and not checking that its still trying to load the super class. For example, in this case CMember would have finished loading its super (java.lang.Object) so there is no circularity. I'm thinking the fix would involve a new class state and classEntry state that break up the loading of the super class. I'll try to look at it more over the weekend... Did I say last weekend, I meant this weekend... Anyways, the only way I could figure out how to fix this was to start another thread to do the load. Its not ideal, but I'm having trouble finding any other way to do it that works with user loaders. Helmer tim tim ___ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
[kaffe] CVS kaffe (dalibor): Merged in RMI from GNU Classpath, replacing kaffe's old implementation. I've left out the RMISecurityManager for now, as it prevents native libraries needed for java.net from loading. I've changed classpath's implementation to fix a few bugs, and added kjc and jikes rmic compiler classes. Now at least RMIC works, but there are still some issues with serialization and class loading.
PatchSet 3961 Date: 2003/08/18 17:40:27 Author: dalibor Branch: HEAD Tag: (none) Log: Merged in RMI from GNU Classpath, replacing kaffe's old implementation. I've left out the RMISecurityManager for now, as it prevents native libraries needed for java.net from loading. I've changed classpath's implementation to fix a few bugs, and added kjc and jikes rmic compiler classes. Now at least RMIC works, but there are still some issues with serialization and class loading. Members: ChangeLog:1.1559-1.1560 include/Makefile.am:1.45-1.46 include/Makefile.in:1.117-1.118 kaffe/Makefile.in:1.77-1.78 kaffe/kaffe/Makefile.in:1.91-1.92 kaffe/scripts/Makefile.in:1.100-1.101 kaffe/scripts/rmic.in:1.4-1.5 kaffe/scripts/rmiregistry.in:1.4-1.5 kaffe/scripts/compat/Makefile.in:1.83-1.84 libraries/clib/native/Makefile.am:1.25-1.26 libraries/clib/native/Makefile.in:1.104-1.105 libraries/clib/native/RMIHashes.c:1.5-1.6(DEAD) libraries/javalib/Makefile.am:1.130-1.131 libraries/javalib/Makefile.in:1.178-1.179 libraries/javalib/gnu/java/rmi/RMIMarshalledObjectInputStream.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/RMIMarshalledObjectOutputStream.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/dgc/DGCImpl.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/dgc/DGCImpl_Skel.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/dgc/DGCImpl_Stub.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/registry/RegistryImpl.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/registry/RegistryImpl_Skel.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/registry/RegistryImpl_Stub.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/rmic/Compile_gcj.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/rmic/Compile_jikes.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/rmic/Compile_kjc.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/rmic/Compiler.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/rmic/CompilerProcess.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/rmic/RMIC.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/rmic/RMICException.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/rmic/TabbedWriter.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/server/ConnectionRunnerPool.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/server/ProtocolConstants.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/server/RMIDefaultSocketFactory.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/server/RMIHashes.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/server/RMIObjectInputStream.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/server/RMIObjectOutputStream.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/server/UnicastConnection.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/server/UnicastConnectionManager.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/server/UnicastRef.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/server/UnicastRemoteCall.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/server/UnicastRemoteStub.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/server/UnicastServer.java:INITIAL-1.1 libraries/javalib/gnu/java/rmi/server/UnicastServerRef.java:INITIAL-1.1 libraries/javalib/java/rmi/MarshalledObject.java:1.1-1.2 libraries/javalib/java/rmi/Naming.java:1.1-1.2 libraries/javalib/java/rmi/Remote.java:1.1-1.2 libraries/javalib/java/rmi/activation/Activatable.java:1.1-1.2 libraries/javalib/java/rmi/activation/ActivationDesc.java:1.1-1.2 libraries/javalib/java/rmi/activation/ActivationGroup.java:1.1-1.2 libraries/javalib/java/rmi/activation/ActivationGroupDesc.java:1.1-1.2 libraries/javalib/java/rmi/activation/ActivationGroupID.java:1.1-1.2 libraries/javalib/java/rmi/activation/ActivationID.java:1.1-1.2 libraries/javalib/java/rmi/activation/ActivationInstantiator.java:1.1-1.2 libraries/javalib/java/rmi/activation/ActivationMonitor.java:1.1-1.2 libraries/javalib/java/rmi/activation/ActivationSystem.java:1.1-1.2 libraries/javalib/java/rmi/activation/Activator.java:1.1-1.2 libraries/javalib/java/rmi/dgc/DGC.java:1.1-1.2 libraries/javalib/java/rmi/dgc/Lease.java:1.1-1.2 libraries/javalib/java/rmi/dgc/VMID.java:1.1-1.2 libraries/javalib/java/rmi/registry/LocateRegistry.java:1.1-1.2 libraries/javalib/java/rmi/registry/Registry.java:1.1-1.2 libraries/javalib/java/rmi/registry/RegistryHandler.java:1.1-1.2 libraries/javalib/java/rmi/server/LoaderHandler.java:1.1-1.2 libraries/javalib/java/rmi/server/LogStream.java:1.1-1.2 libraries/javalib/java/rmi/server/ObjID.java:1.1-1.2
Re: [kaffe] loginfo script problems
On Sat, 16 Aug 2003 08:50:07 -0700 Jim Pick [EMAIL PROTECTED] wrote: I've added some matching code / sanity checks to the script, so hopefully it will send the right patch for the commit now. And, I just added some code to truncate the subject line of the email to 80 characters. :-) Cheers, - Jim ___ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
[kaffe] peers and profile
Hi folks!!! Currently for kaffe all AWT targets use the exact same Java class files. Only the native C code varies. Now in a peer design each target would have its own set of classes. How will we approach this for setting up the build system? ___ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
RE: [kaffe] peers and profile
Hi James, As I myself am working on two separate sets of AWT peer implementations (framebuffer and peered Qt/Embedded), I'd really appreciate it if we could treat such peer implementations as self-contained jar extensions with their build separate from kaffe's. Stephane -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James Simmons Sent: 18 August 2003 19:59 To: [EMAIL PROTECTED] Subject: [kaffe] peers and profile Hi folks!!! Currently for kaffe all AWT targets use the exact same Java class files. Only the native C code varies. Now in a peer design each target would have its own set of classes. How will we approach this for setting up the build system? ___ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe ___ kaffe mailing list [EMAIL PROTECTED] http://kaffe.org/cgi-bin/mailman/listinfo/kaffe