Loading...

XML

Word

Printable

Type: Bug
Resolution: Not an Issue
Priority: P4
Fix Version/s: tbd
Affects Version/s: 11, 12
Component/s: hotspot
Labels:

Subcomponent:
test
CPU:

generic
OS:

generic

During my analysis of jdk/jdk CI test failures, I'm seeing a
number of test timeouts that appear to be caused by some
failure in JTREG's "agentvm" mode.

This bug is intended as a gathering place for sightings of
test time outs in "agentvm" mode only! In particular, the JTREG
test needs to fail with a message like this one:

result: Error. Agent error: java.lang.Exception: Agent 3 timed out with a timeout of 1200 seconds; check console log for any additional details

In the above message, "Agent 3" is an example.

Please DO NOT add sightings to this bug unless they are
hangs related to "agentvm" mode and they timeout in
about 20 minutes (1200 seconds).

duplicates

JDK-8212630 jtreg/gc/logging/TestMetaSpaceLog.java failed with Agent timed out

Resolved

JDK-8212631 gc/arguments/TestUseCompressedOopsErgo.java#id1 timed out

Closed

JDK-8213833 runtime/LoadClass/TestResize.java timeout

Closed

JDK-8208212 java/lang/Class/forName/modules/TestDriver.java timed out

Closed

relates to

CODETOOLS-7902346 Need better message when test times out in agentvm mode

Resolved

JDK-8204529 gc/TestAllocateHeapAtMultiple.java fail with Agent 7 timed out

Resolved

JDK-8212628 gc/arguments/TestSerialHeapSizeFlags.java failed with "Agent communication error: java.net.SocketException: Broken pipe (Write failed)"

Closed

JDK-8205532 tests timeout intermittently on Solaris SPARC in "agentvm" mode

Closed

(3 relates to)

Assignee:: Unassigned

Reporter:: Daniel Daugherty

Votes:: 0 Vote for this issue

Watchers:: 20 Start watching this issue

Created:: 2018-06-22 08:02

Updated:: 2018-12-14 16:39

Resolved:: 2018-12-14 16:39

Details

Description

Attachments

Issue Links

Activity

People

Dates