-
Bug
-
Resolution: Fixed
-
P5
-
8
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8045669 | 8u25 | Mattias Tobiasson | P5 | Resolved | Fixed | b01 |
JDK-8043150 | 8u20 | Mattias Tobiasson | P5 | Resolved | Fixed | b17 |
JDK-8053614 | emb-8u26 | Mattias Tobiasson | P5 | Resolved | Fixed | b17 |
java/lang/management/MemoryMXBean/LowMemoryTestConcMarkSweepGC.sh
was ever failed in JDK8 TL nightly with "timeout".
Notice that we use "make" run regression tests in nightly thus run with -timeoutFactor:4 (defined by makefile)
----------messages:(6/259)----------
JDK under test: (/Users/aurora/sandbox/jdk)
java version "1.8.0-ea"
Java(TM) SE Runtime Environment (build 1.8.0-ea-langtools-nightly-h850-20131125-b118-b00)
Java HotSpot(TM) 64-Bit Server VM (build 25.0-b59, mixed mode)
Timeout signaled after 2,400 seconds
#section:build
----------messages:(3/113)----------
command: build LowMemoryTest
reason: User specified action: run build LowMemoryTest
elapsed time (seconds): 0.0
result: Passed. All files up to date
#section:shell
----------messages:(3/166)----------
command: shell LowMemoryTestConcMarkSweepGC.sh
reason: User specified action: run shell/timeout=600 LowMemoryTestConcMarkSweepGC.sh
elapsed time (seconds): 2400.008
----------System.out:(9/438)----------
runOne -XX:+UseConcMarkSweepGC LowMemoryTest
Setting threshold for CMS Old Gen from 0 to 36241408. Current used = 0
AllocatorThread is doing task 1
Notification for CMS Old Gen [type = java.management.memory.threshold.exceeded count = 1]
usage = init = 126615552(123648K) used = 126615552(123648K) committed = 126615552(123648K) max = 362414080(353920K)
Waiting
SweepThread is doing task 1
Notify
AllocatorThread is doing task 2
----------System.err:(0/0)----------
was ever failed in JDK8 TL nightly with "timeout".
Notice that we use "make" run regression tests in nightly thus run with -timeoutFactor:4 (defined by makefile)
----------messages:(6/259)----------
JDK under test: (/Users/aurora/sandbox/jdk)
java version "1.8.0-ea"
Java(TM) SE Runtime Environment (build 1.8.0-ea-langtools-nightly-h850-20131125-b118-b00)
Java HotSpot(TM) 64-Bit Server VM (build 25.0-b59, mixed mode)
Timeout signaled after 2,400 seconds
#section:build
----------messages:(3/113)----------
command: build LowMemoryTest
reason: User specified action: run build LowMemoryTest
elapsed time (seconds): 0.0
result: Passed. All files up to date
#section:shell
----------messages:(3/166)----------
command: shell LowMemoryTestConcMarkSweepGC.sh
reason: User specified action: run shell/timeout=600 LowMemoryTestConcMarkSweepGC.sh
elapsed time (seconds): 2400.008
----------System.out:(9/438)----------
runOne -XX:+UseConcMarkSweepGC LowMemoryTest
Setting threshold for CMS Old Gen from 0 to 36241408. Current used = 0
AllocatorThread is doing task 1
Notification for CMS Old Gen [type = java.management.memory.threshold.exceeded count = 1]
usage = init = 126615552(123648K) used = 126615552(123648K) committed = 126615552(123648K) max = 362414080(353920K)
Waiting
SweepThread is doing task 1
Notify
AllocatorThread is doing task 2
----------System.err:(0/0)----------
- backported by
-
JDK-8043150 LowMemoryTestConcMarkSweepGC.sh fails intermittently with timeout
-
- Resolved
-
-
JDK-8045669 LowMemoryTestConcMarkSweepGC.sh fails intermittently with timeout
-
- Resolved
-
-
JDK-8053614 LowMemoryTestConcMarkSweepGC.sh fails intermittently with timeout
-
- Resolved
-
- duplicates
-
JDK-6486147 LowMemoryTestConcMarkSweepGC.sh fails intermittently with wrong MemoryNotificationInfo count.
-
- Closed
-