One of the MISC_REGRESSION tests started failing intermittently with
the 2007.09.07 nightly. In that nightly, I merged Serv_Baseline with
the 20070907063323.rasbold.compiler_hsx11_merge push to main/baseline.
I've added Chuck R. to the interest list for this bug.
Here is my analysis report entry:
New MISC_REGRESSION failures (from 2007.09.07)
sun/tools/jstat/jstatPrintCompilationOutput1.sh
This test failed due to unexpected output ("Should have been
marked for deoptimization") on Solaris AMD64 Server VM (machine
sunjava-64-02), Solaris X86 Server VM (machine colfax004),
Solaris SPARC Client VM (machine vm-ultra80-01), Win32 Client
VM (machine cheesepuff) and Win32 Server VM (machine vm-8450r-3).
In the 2007.09.08 nightly, this test also failed on Solaris
SPARC-64 Server VM (machine jtgb4u2e).
Last failure on 2007.09.08 with Solaris X86 Server, Solaris SPARC-64 Server, Win32 Client and Win32 Server VMs.
Previous failure on 2007.09.07 with Solaris AMD64 Server, Solaris X86 Server, Solaris SPARC Client, Win32 Client and Win32 Server VMs.
Here is a link to a passing run:
http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-09-07/Serv_Baseline/vm/solaris-i586/client/comp/vm-solaris-i586_client_comp_MISC_REGRESSION2007-09-07-23-36-30/sun/tools/jstat/jstatPrintCompilationOutput1.jtr
passing output appears to have just two lines.
Here are links to the failing 5 runs from 2007.09.07:
http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-09-07/Serv_Baseline/vm/solaris-i586/server/comp/vm-solaris-i586_server_comp_MISC_REGRESSION2007-09-07-23-41-45/sun/tools/jstat/jstatPrintCompilationOutput1.jtr
http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-09-07/Serv_Baseline/vm/windows-i586/client/comp/vm-windows-i586_client_comp_MISC_REGRESSION2007-09-07-23-42-00/sun/tools/jstat/jstatPrintCompilationOutput1.jtr
http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-09-07/Serv_Baseline/vm/windows-i586/server/comp/vm-windows-i586_server_comp_MISC_REGRESSION2007-09-07-23-40-50/sun/tools/jstat/jstatPrintCompilationOutput1.jtr
http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-09-07/Serv_Baseline/vm/solaris-sparc/client/comp/vm-solaris-sparc_client_comp_MISC_REGRESSION2007-09-07-23-40-03/sun/tools/jstat/jstatPrintCompilationOutput1.jtr
http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-09-07/Serv_Baseline/vm/solaris-amd64/server/comp/vm-solaris-amd64_server_comp_MISC_REGRESSION2007-09-07-23-41-49/sun/tools/jstat/jstatPrintCompilationOutput1.jtr
Here are links to the failing 4 runs from 2007.09.08:
http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-09-08/Serv_Baseline/vm/solaris-i586/server/comp/vm-solaris-i586_server_comp_MISC_REGRESSION2007-09-08-22-43-04/sun/tools/jstat/jstatPrintCompilationOutput1.jtr
http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-09-08/Serv_Baseline/vm/windows-i586/client/comp/vm-windows-i586_client_comp_MISC_REGRESSION2007-09-08-22-43-41/sun/tools/jstat/jstatPrintCompilationOutput1.jtr
http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-09-08/Serv_Baseline/vm/windows-i586/server/comp/vm-windows-i586_server_comp_MISC_REGRESSION2007-09-08-22-45-56/sun/tools/jstat/jstatPrintCompilationOutput1.jtr
http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-09-08/Serv_Baseline/vm/solaris-sparcv9/server/comp/vm-solaris-sparcv9_server_comp_MISC_REGRESSION2007-09-08-22-51-02/sun/tools/jstat/jstatPrintCompilationOutput1.jtr
the 2007.09.07 nightly. In that nightly, I merged Serv_Baseline with
the 20070907063323.rasbold.compiler_hsx11_merge push to main/baseline.
I've added Chuck R. to the interest list for this bug.
Here is my analysis report entry:
New MISC_REGRESSION failures (from 2007.09.07)
sun/tools/jstat/jstatPrintCompilationOutput1.sh
This test failed due to unexpected output ("Should have been
marked for deoptimization") on Solaris AMD64 Server VM (machine
sunjava-64-02), Solaris X86 Server VM (machine colfax004),
Solaris SPARC Client VM (machine vm-ultra80-01), Win32 Client
VM (machine cheesepuff) and Win32 Server VM (machine vm-8450r-3).
In the 2007.09.08 nightly, this test also failed on Solaris
SPARC-64 Server VM (machine jtgb4u2e).
Last failure on 2007.09.08 with Solaris X86 Server, Solaris SPARC-64 Server, Win32 Client and Win32 Server VMs.
Previous failure on 2007.09.07 with Solaris AMD64 Server, Solaris X86 Server, Solaris SPARC Client, Win32 Client and Win32 Server VMs.
Here is a link to a passing run:
http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-09-07/Serv_Baseline/vm/solaris-i586/client/comp/vm-solaris-i586_client_comp_MISC_REGRESSION2007-09-07-23-36-30/sun/tools/jstat/jstatPrintCompilationOutput1.jtr
passing output appears to have just two lines.
Here are links to the failing 5 runs from 2007.09.07:
http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-09-07/Serv_Baseline/vm/solaris-i586/server/comp/vm-solaris-i586_server_comp_MISC_REGRESSION2007-09-07-23-41-45/sun/tools/jstat/jstatPrintCompilationOutput1.jtr
http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-09-07/Serv_Baseline/vm/windows-i586/client/comp/vm-windows-i586_client_comp_MISC_REGRESSION2007-09-07-23-42-00/sun/tools/jstat/jstatPrintCompilationOutput1.jtr
http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-09-07/Serv_Baseline/vm/windows-i586/server/comp/vm-windows-i586_server_comp_MISC_REGRESSION2007-09-07-23-40-50/sun/tools/jstat/jstatPrintCompilationOutput1.jtr
http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-09-07/Serv_Baseline/vm/solaris-sparc/client/comp/vm-solaris-sparc_client_comp_MISC_REGRESSION2007-09-07-23-40-03/sun/tools/jstat/jstatPrintCompilationOutput1.jtr
http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-09-07/Serv_Baseline/vm/solaris-amd64/server/comp/vm-solaris-amd64_server_comp_MISC_REGRESSION2007-09-07-23-41-49/sun/tools/jstat/jstatPrintCompilationOutput1.jtr
Here are links to the failing 4 runs from 2007.09.08:
http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-09-08/Serv_Baseline/vm/solaris-i586/server/comp/vm-solaris-i586_server_comp_MISC_REGRESSION2007-09-08-22-43-04/sun/tools/jstat/jstatPrintCompilationOutput1.jtr
http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-09-08/Serv_Baseline/vm/windows-i586/client/comp/vm-windows-i586_client_comp_MISC_REGRESSION2007-09-08-22-43-41/sun/tools/jstat/jstatPrintCompilationOutput1.jtr
http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-09-08/Serv_Baseline/vm/windows-i586/server/comp/vm-windows-i586_server_comp_MISC_REGRESSION2007-09-08-22-45-56/sun/tools/jstat/jstatPrintCompilationOutput1.jtr
http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-09-08/Serv_Baseline/vm/solaris-sparcv9/server/comp/vm-solaris-sparcv9_server_comp_MISC_REGRESSION2007-09-08-22-51-02/sun/tools/jstat/jstatPrintCompilationOutput1.jtr
- relates to
-
JDK-6471009 Significantly higher CPU usage in jvm1.6 build 97/98 vs jvm1.5.0_06-b05 on DOTS ATCJ2 test
- Resolved