-
Bug
-
Resolution: Duplicate
-
P3
-
None
-
15
java/awt/image/BufferedImage/ICMColorDataTest/ICMColorDataTest.java
has a timeout of 300000 ! I wonder if the author thought that was
milliseconds, since 300,000 seconds is a very long time.
The test really does run a long time. In one of the FASTEST runs I
can see on a test job on Windows it took about 1hr 20mins.
[2020-03-19T09:07:00,184Z] TEST: java/awt/image/BufferedImage/ICMColorDataTest/ICMColorDataTest.java
[2020-03-19T09:07:00,184Z] build: 2.294 seconds
[2020-03-19T09:07:00,184Z] compile: 2.294 seconds
[2020-03-19T09:07:00,184Z] main: 2514.554 seconds
[2020-03-19T09:07:00,184Z] TEST RESULT: Passed. Execution successful
Sometimes it runs slow enough that the entire jtreg job is timed out and killed
I don't know why this test needs to run so long but I don't think we can afford a test which probably is increasing the wall clock run time for the entire job from 30 mins to 90 minuts
has a timeout of 300000 ! I wonder if the author thought that was
milliseconds, since 300,000 seconds is a very long time.
The test really does run a long time. In one of the FASTEST runs I
can see on a test job on Windows it took about 1hr 20mins.
[2020-03-19T09:07:00,184Z] TEST: java/awt/image/BufferedImage/ICMColorDataTest/ICMColorDataTest.java
[2020-03-19T09:07:00,184Z] build: 2.294 seconds
[2020-03-19T09:07:00,184Z] compile: 2.294 seconds
[2020-03-19T09:07:00,184Z] main: 2514.554 seconds
[2020-03-19T09:07:00,184Z] TEST RESULT: Passed. Execution successful
Sometimes it runs slow enough that the entire jtreg job is timed out and killed
I don't know why this test needs to run so long but I don't think we can afford a test which probably is increasing the wall clock run time for the entire job from 30 mins to 90 minuts
- duplicates
-
JDK-8233028 Investigate slow performance of ICMColorDataTest on Windows x64
-
- Open
-