RT_DEMO tests were added recently for c2_baseline Nightly testing (10/18/2004).
From the beginning of RT_DEMO testing we have this failure:
=== Meet Not Symmetric ===
VM option 'CompileThreshold=100'
t = NULL+bot
this= rawptr:BotPTR
mt=(t meet this)= rawptr:BotPTR
t_dual= NULL+top
this_dual= rawptr:TopPTR
mt_dual= rawptr:TopPTR
mt_dual meet t_dual= NULL
mt_dual meet this_dual= rawptr:TopPTR
# To suppress the following error report, specify this argument
# after -XX: or in .hotspotrc: SuppressErrorAt=/type.cpp:453]
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# Internal Error (/net/prt-solx86-q1-6/PrtBuildDir/workspace/src/share/vm/opto/type.cpp, 453), pid=852, tid=9
#
# Java VM: Java HotSpot(TM) Server VM (20041018075437.nips.ivsched-debug mixed mode)
#
# Error: meet not symmetric
# An error report file with more information is saved as hs_err_pid852.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
Current thread is 9
Dumping core ...
It always fails on several platforms: linux-x86, linux-amd64, solaris-x86.
And one time on solaris-sparc64.
To reproduce on solaris-x86:
ksh /net/vmsqe.sfbay/export/backup/UNIFIED-DTF/DTWS/suites/RT_DEMO/testbase/doit -vm /net/vmsqe.sfbay/export/nightly/mantis/JDK/c2_baseline/jdk1.6/solaris-i586/bin/java -vmopts "-server -DHANGINGJAVA702 -XX:CompileThreshold=100" -demo
It usally fails during Java2Demo test.
I attached hs_err file for solaris-x86 and solaris-sparc64 runs.
I copied it from the test run directories:
/net/vmsqe.sfbay/export/nightly/mantis/DTWS/results/10-19-04/ServerVM/solx86/comp/C2_Baseline/RT_DEMO-NIGHTLY-C2_Baseline-ServerVM-comp-solx86-2004-10-20-02-09-44/hs_err_pid1727.log
/net/vmsqe.sfbay/export/nightly/mantis/DTWS/results/10-19-04/ServerVM/64BITSOLSPARC/comp/C2_Baseline/RT_DEMO-NIGHTLY-C2_Baseline-ServerVM-comp-64BITSOLSPARC-2004-10-20-05-44-07/hs_err_pid941.log
Please note, there is a problem with testing.
The Java2Demo test continue run while the runThis thinks it finished and
starts the next test SwingSet2. So both tests run at the same time.
###@###.### 10/28/04 01:03 GMT
From the beginning of RT_DEMO testing we have this failure:
=== Meet Not Symmetric ===
VM option 'CompileThreshold=100'
t = NULL+bot
this= rawptr:BotPTR
mt=(t meet this)= rawptr:BotPTR
t_dual= NULL+top
this_dual= rawptr:TopPTR
mt_dual= rawptr:TopPTR
mt_dual meet t_dual= NULL
mt_dual meet this_dual= rawptr:TopPTR
# To suppress the following error report, specify this argument
# after -XX: or in .hotspotrc: SuppressErrorAt=/type.cpp:453]
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# Internal Error (/net/prt-solx86-q1-6/PrtBuildDir/workspace/src/share/vm/opto/type.cpp, 453), pid=852, tid=9
#
# Java VM: Java HotSpot(TM) Server VM (20041018075437.nips.ivsched-debug mixed mode)
#
# Error: meet not symmetric
# An error report file with more information is saved as hs_err_pid852.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
Current thread is 9
Dumping core ...
It always fails on several platforms: linux-x86, linux-amd64, solaris-x86.
And one time on solaris-sparc64.
To reproduce on solaris-x86:
ksh /net/vmsqe.sfbay/export/backup/UNIFIED-DTF/DTWS/suites/RT_DEMO/testbase/doit -vm /net/vmsqe.sfbay/export/nightly/mantis/JDK/c2_baseline/jdk1.6/solaris-i586/bin/java -vmopts "-server -DHANGINGJAVA702 -XX:CompileThreshold=100" -demo
It usally fails during Java2Demo test.
I attached hs_err file for solaris-x86 and solaris-sparc64 runs.
I copied it from the test run directories:
/net/vmsqe.sfbay/export/nightly/mantis/DTWS/results/10-19-04/ServerVM/solx86/comp/C2_Baseline/RT_DEMO-NIGHTLY-C2_Baseline-ServerVM-comp-solx86-2004-10-20-02-09-44/hs_err_pid1727.log
/net/vmsqe.sfbay/export/nightly/mantis/DTWS/results/10-19-04/ServerVM/64BITSOLSPARC/comp/C2_Baseline/RT_DEMO-NIGHTLY-C2_Baseline-ServerVM-comp-64BITSOLSPARC-2004-10-20-05-44-07/hs_err_pid941.log
Please note, there is a problem with testing.
The Java2Demo test continue run while the runThis thinks it finished and
starts the next test SwingSet2. So both tests run at the same time.
###@###.### 10/28/04 01:03 GMT