Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8056680 | emb-9 | Unassigned | P4 | Resolved | Fixed | b26 |
The compiler/6589834/Test_ia32.java works too long on linux-i586.
Looks like it takes too long time just to create 1000 threads and run them in the same time. And on slow machines (like vmsqe-p3-04) test time out. I attached the simplified case (Test.java) which works abnormally long on linux. Please note that it works fine on the Solaris.
Here is time for Solaris:
-->time java Test
Started......
real 0m0.170s
user 0m0.109s
sys 0m0.054s
Here is for any Linux (Core Quad):
-->time java Test
Started......
real 0m18.584s
user 1m13.561s
sys 0m0.040s
lm153972@vmsqe-core2q-16:~//ws/test>
If it will be decided as a Test Bug we could update the run() method in the test
by adding Thread.sleep() before main cycle.
>>> added 105, 108, 109
103 try {
104 ctrs = klass.getConstructors();
105 Thread.sleep(10);
106 } catch (SecurityException e) {
107 System.out.println(e);
108 } catch (Throwable t) {
109 }
Looks like it takes too long time just to create 1000 threads and run them in the same time. And on slow machines (like vmsqe-p3-04) test time out. I attached the simplified case (Test.java) which works abnormally long on linux. Please note that it works fine on the Solaris.
Here is time for Solaris:
-->time java Test
Started......
real 0m0.170s
user 0m0.109s
sys 0m0.054s
Here is for any Linux (Core Quad):
-->time java Test
Started......
real 0m18.584s
user 1m13.561s
sys 0m0.040s
lm153972@vmsqe-core2q-16:~//ws/test>
If it will be decided as a Test Bug we could update the run() method in the test
by adding Thread.sleep() before main cycle.
>>> added 105, 108, 109
103 try {
104 ctrs = klass.getConstructors();
105 Thread.sleep(10);
106 } catch (SecurityException e) {
107 System.out.println(e);
108 } catch (Throwable t) {
109 }
- backported by
-
JDK-8056680 [TESTBUG] The compiler/6589834/Test_ia32.java timed out
- Resolved