From 1e57dd2550c68ff2ae273a6c8a694b6421f9f336 Mon Sep 17 00:00:00 2001 From: Stefan Ring Date: Wed, 30 Apr 2008 20:40:48 +0200 Subject: [PATCH] * tests/threads/threadInterrupt.java: Added brief comment explaining the purpose of this test. * tests/threads/waitAndInterrupt.java: Likewise. --- tests/threads/threadInterrupt.java | 7 +++++++ tests/threads/waitAndInterrupt.java | 3 +++ 2 files changed, 10 insertions(+) diff --git a/tests/threads/threadInterrupt.java b/tests/threads/threadInterrupt.java index ef4108379..cbff11317 100644 --- 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 2f68b7558..6a1ac0bde 100644 --- 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. -- 2.25.1