JDK-7020857 : TEST_BUG: com/sun/jdi/FieldWatchpoints.java failing intermittently
  • Type: Bug
  • Component: core-svc
  • Sub-Component: debugger
  • Affected Version: 7
  • Priority: P3
  • Status: Resolved
  • Resolution: Cannot Reproduce
  • OS: generic
  • CPU: generic
  • Submitted: 2011-02-19
  • Updated: 2014-08-08
  • Resolved: 2013-08-21
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8
8Resolved
Related Reports
Relates :  
Relates :  
Relates :  
Description
TESTFAIL:com/sun/jdi/FieldWatchpoints.java

is timing out intermitently in JPRT. Here's an example of a TL build that is close to jdk7-b130:

-------------------------------

TEST: com/sun/jdi/FieldWatchpoints.java
JDK under test: C:\temp\jprt\P2\T\110204~1.AB2\TESTPR~1\WINDOW~1.1-P
Timeout signalled after 480 seconds


ACTION: build -- Passed. All files up to date
REASON: User specified action: run build TestScaffold VMConnection TargetListener TargetAdapter 
TIME:   0.0 seconds
messages:
command: build TestScaffold VMConnection TargetListener TargetAdapter
reason: User specified action: run build TestScaffold VMConnection TargetListener TargetAdapter 
elapsed time (seconds): 0.0

ACTION: compile -- Passed. Compilation successful
REASON: User specified action: run compile -g FieldWatchpoints.java 
TIME:   0.062 seconds
messages:
command: compile -g C:\temp\jprt\P2\T\110204.ab23780\source\test\com\sun\jdi\FieldWatchpoints.java
reason: User specified action: run compile -g FieldWatchpoints.java 
elapsed time (seconds): 0.062

ACTION: build -- Passed. All files up to date
REASON: Named class compiled on demand
TIME:   0.0 seconds
messages:
command: build FieldWatchpoints
reason: Named class compiled on demand
elapsed time (seconds): 0.0

ACTION: main -- Error. Program `C:\temp\jprt\P2\T\110204~1.AB2\TESTPR~1\WINDOW~1.1-P\bin\java' interrupted! (timed out?)
REASON: User specified action: run main/othervm FieldWatchpoints 
TIME:   480.007 seconds
messages:
command: main FieldWatchpoints
reason: User specified action: run main/othervm FieldWatchpoints 
elapsed time (seconds): 480.007
STDOUT:
JVM version:1.7.0-internal
JDI version: 1.6
JVM description: Java Debug Interface (Reference Implementation) version 1.6 
Java Debug Wire Protocol (Reference Implementation) version 1.6
JVM Debug Interface version 1.2
JVM version 1.7.0-internal (Java HotSpot(TM) Client VM, mixed mode, sharing)
Field modified: ModificationWatchpoint@FieldWatchpointsDebugee:49 in thread main
Field modified: ModificationWatchpoint@FieldWatchpointsDebugee:50 in thread main
aField is: 11
Field accessed: AccessWatchpoint@FieldWatchpointsDebugee:55 in thread main
STDERR:
run args: [FieldWatchpointsDebugee]

TEST RESULT: Error. Program `C:\temp\jprt\P2\T\110204~1.AB2\TESTPR~1\WINDOW~1.1-P\bin\java' interrupted! (timed out?)
Another one:

--------------------------------------------------
TEST: com/sun/jdi/FieldWatchpoints.java
JDK under test: (C:\temp\jprt\P1\T\232024~1.SMA\TESTPR~1\WINDOW~1.2-P)
openjdk version "1.7.0-internal"
OpenJDK Runtime Environment (build 1.7.0-internal-201103132320.smarks.jdk-testbaseline-b00)
Java HotSpot(TM) 64-Bit Server VM (build 21.0-b03, mixed mode)
Timeout signalled after 480 seconds


ACTION: build -- Passed. All files up to date
REASON: User specified action: run build TestScaffold VMConnection TargetListener TargetAdapter 
TIME:   0.0 seconds
messages:
command: build TestScaffold VMConnection TargetListener TargetAdapter
reason: User specified action: run build TestScaffold VMConnection TargetListener TargetAdapter 
elapsed time (seconds): 0.0

ACTION: compile -- Passed. Compilation successful
REASON: User specified action: run compile -g FieldWatchpoints.java 
TIME:   0.062 seconds
messages:
command: compile -g C:\temp\jprt\P1\T\232024.smarks\source\test\com\sun\jdi\FieldWatchpoints.java
reason: User specified action: run compile -g FieldWatchpoints.java 
elapsed time (seconds): 0.062

ACTION: build -- Passed. All files up to date
REASON: Named class compiled on demand
TIME:   0.0 seconds
messages:
command: build FieldWatchpoints
reason: Named class compiled on demand
elapsed time (seconds): 0.0

ACTION: main -- Error. Program `C:\temp\jprt\P1\T\232024~1.SMA\TESTPR~1\WINDOW~1.2-P\bin\java' interrupted! (timed out?)
REASON: User specified action: run main/othervm FieldWatchpoints 
TIME:   480.0 seconds
messages:
command: main FieldWatchpoints
reason: User specified action: run main/othervm FieldWatchpoints 
elapsed time (seconds): 480.0
STDOUT:
JVM version:1.7.0-internal
JDI version: 1.6
JVM description: Java Debug Interface (Reference Implementation) version 1.6 
Java Debug Wire Protocol (Reference Implementation) version 1.6
JVM Debug Interface version 1.2
JVM version 1.7.0-internal (Java HotSpot(TM) 64-Bit Server VM, mixed mode, sharing)
Field modified: ModificationWatchpoint@FieldWatchpointsDebugee:49 in thread main
Field modified: ModificationWatchpoint@FieldWatchpointsDebugee:50 in thread main
aField is: 11
Field accessed: AccessWatchpoint@FieldWatchpointsDebugee:55 in thread main
STDERR:
run args: [FieldWatchpointsDebugee]

TEST RESULT: Error. Program `C:\temp\jprt\P1\T\232024~1.SMA\TESTPR~1\WINDOW~1.2-P\bin\java' interrupted! (timed out?)
--------------------------------------------------

Comments
Thanks, Staffan. We tend to look at nightlies at different angles. For me it is always hotspot set of test suites for the runtime repo, but other repos (including core-libs and TL) do not include all the JDI tests.
21-08-2013

Yes, there is confusion about "nigthlies" as there are many different nightly testing runs. The core libraries' nightlies do not include the com/sun/jdi jtreg tests. The Hotspot nightlies for the runtime repo do include these tests.
21-08-2013

Sorry for a confusion, Stuart. This particular test is JTREG test, not NSK. But it is still being run by Aurora in nightlies. The JPRT setup does not impact it.
21-08-2013

We might be talking about different nightlies as well as different tests. Indeed, the JTREG JDI tests are no longer run by typical JPRT jobs (e.g., Lana's integration jobs) nor by the TL nightly job run by Aurora. The NSK JDI tests might be different tests, and they might also be run by a different nightly (hotspot?).
21-08-2013

Stuart, The JTREG JDI tests have been removed from the "core" set of the JPRT. The NSK JDI tests are still being run by Aurora in nightlies.
21-08-2013

The tests are still being run by the VM nightlies.
21-08-2013

Note, the JDI tests have been removed from the "core" testset because of high incidence of failures, so they're not being run by Aurora or JPRT. I've heard (but have not investigated) that the issue with the JDI tests is in some common framework that they use, not necessarily a problem in any particular test. So, to see the intermittent failures, I'd recommend running a few JPRT jobs that run all the JDI tests on all the platforms.
21-08-2013

I cannot find any records in aurora of this test failing in this way for the last year or so. I can see other failures of the test, but not this one. I have run the test 1000 times on linux x86-64 with no failures.
21-08-2013