This testcase is repeatedly timing out on windows machines, not sure if this represents a regression or not.

TEST: java/util/ResourceBundle/RestrictedBundleTest.java
JDK under test: (C:\temp\jprt\T1\T\202507~1.OHA\TESTPR~1\WINDOW~1.0-F)
java version "1.7.0-2009-05-15-202507.ohair.jdk-fastdebug"
Java(TM) SE Runtime Environment (build 1.7.0-2009-05-15-202507.ohair.jdk-fastdebug-administrator_2009_05_15_23_02-b00)
Java HotSpot(TM) Client VM (build 16.0-b03, mixed mode, sharing)
Timeout signalled after 120 seconds


ACTION: build -- Passed. Build successful
REASON: Named class compiled on demand
TIME: 0.609 seconds
messages:
command: build RestrictedBundleTest
reason: Named class compiled on demand
elapsed time (seconds): 0.609

ACTION: compile -- Passed. Compilation successful
REASON: .class file out of date or does not exist
TIME: 0.609 seconds
messages:
command: compile C:\temp\jprt\T1\T\202507.ohair\source\test\java\util\ResourceBundle\RestrictedBundleTest.java
reason: .class file out of date or does not exist
elapsed time (seconds): 0.609
STDOUT:
STDERR:

ACTION: applet -- Error. Program `C:\temp\jprt\T1\T\202507~1.OHA\TESTPR~1\WINDOW~1.0-F\bin\java' interrupted! (timed out?)
REASON: User specified action: run applet RestrictedBundleTest.html
TIME: 120.0 seconds
messages:
command: applet RestrictedBundleTest.html
reason: User specified action: run applet RestrictedBundleTest.html
elapsed time (seconds): 120.0
STDOUT:
OK
STDERR:

TEST RESULT: Error. Program `C:\temp\jprt\T1\T\202507~1.OHA\TESTPR~1\WINDOW~1.0-F\bin\java' interrupted! (timed out?)