* tests/threads/threadInterrupt.java: Added brief comment explaining the

purpose of this test.
* tests/threads/waitAndInterrupt.java: Likewise.

diff --git a/tests/threads/threadInterrupt.java b/tests/threads/threadInterrupt.java
index ef4108379a40ca8429d533fbe9c37a07ad0b1e53..cbff1131798d5c6163776b979c34f04e7e1f6d9c 100644 (file)
--- a/tests/threads/threadInterrupt.java
+++ b/tests/threads/threadInterrupt.java
@@ -1,3 +1,10 @@
+// This test has been added because of a bug in CACAO that allowed threads
+// blocked inside monitorenter to be interrupted. In the presence of the bug,
+// the program would not exit.
+//
+// The bug has been fixed as part of the sable lock implementation.
+// hg revision 2988182011bb ff (Wed Feb 06 18:46:34 2008 +0100)
+
 public class threadInterrupt {
        public static class firstthread implements Runnable {
                private threadInterrupt s;

diff --git a/tests/threads/waitAndInterrupt.java b/tests/threads/waitAndInterrupt.java
index 2f68b7558923f978d2fb58c1ad905cc61e7379f7..6a1ac0bdeb7632a64d21e4ecb8a2cbaca5a2aa7e 100644 (file)
--- a/tests/threads/waitAndInterrupt.java
+++ b/tests/threads/waitAndInterrupt.java
@@ -1,3 +1,6 @@
+// This should run forever. If it stops, that's a good indication for a bug in
+// the VM.
+//
 // This test grew a bit more elaborate than anticipated...
 // It verifies that the JVM handles properly the case of a thread being
 // interrupted and notified at the same time.