[Jikesrvm-issues] [ jikesrvm-Bugs-1591798 ] DaCapo eclipse benchmark fails

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Bugs item #1591798, was opened at 2006-11-07 16:11
Message generated for change (Comment added) made by peter_donald
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=712768&aid=1591798&group_id=128805

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
>Resolution: Duplicate
Priority: 7
Private: No
Submitted By: Robin Garner (rgarner)
>Assigned to: Peter Donald (peter_donald)
Summary: DaCapo eclipse benchmark fails

Initial Comment:
Since 4 Nov 2006, the DaCapo Eclipse benchmark has
failed consistently with the following stack dump:

===== DaCapo eclipse starting warmup =====
Exception in thread "main":
java.lang.NoClassDefFoundError: Could not find the
class org.eclipse.jdt.internal.launching.StandardVMType:
	org.eclipse.jdt.internal.launching.StandardVMType
	at
java.lang.Throwable.fillInStackTrace(Throwable.java:114)
	at java.lang.Throwable.<init>(Throwable.java:58)
	at java.lang.Throwable.<init>(Throwable.java:63)
	at java.lang.Error.<init>(Error.java:81)
	at java.lang.LinkageError.<init>(LinkageError.java:72)
	at
java.lang.NoClassDefFoundError.<init>(NoClassDefFoundError.java:74)
	at
com.ibm.jikesrvm.classloader.VM_TypeReference.resolveInternal(VM_TypeReference.java:593)
	at
com.ibm.jikesrvm.classloader.VM_TypeReference.resolve(VM_TypeReference.java:578)
	at
com.ibm.jikesrvm.VM_Runtime.unresolvedNewScalar(VM_Runtime.java:280)
	at
dacapo.eclipse.HarnessRunner.validJavaHome(HarnessRunner.java:38)
	at dacapo.eclipse.HarnessRunner.run(HarnessRunner.java:19)
	at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
	at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
	at
dacapo.eclipse.EclipseHarness.iterate(EclipseHarness.java:35)
	at dacapo.Benchmark.run(Benchmark.java:121)
	at dacapo.TestHarness.runBenchmark(TestHarness.java:299)
	at dacapo.TestHarness.main(TestHarness.java:240)
	at Harness.main(Harness.java:5)
Caused by: java.lang.ClassNotFoundException:
org.eclipse.jdt.internal.launching.StandardVMType
	at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:405)
	at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:350)
	at
org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(AbstractClassLoader.java:78)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
	at
com.ibm.jikesrvm.classloader.VM_TypeReference.resolveInternal(VM_TypeReference.java:591)
	at
com.ibm.jikesrvm.classloader.VM_TypeReference.resolve(VM_TypeReference.java:578)
	at
com.ibm.jikesrvm.VM_Runtime.unresolvedNewScalar(VM_Runtime.java:280)
	at
dacapo.eclipse.HarnessRunner.validJavaHome(HarnessRunner.java:38)
	at dacapo.eclipse.HarnessRunner.run(HarnessRunner.java:19)
	at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
	at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
	at
dacapo.eclipse.EclipseHarness.iterate(EclipseHarness.java:35)
	at dacapo.Benchmark.run(Benchmark.java:121)
	at dacapo.TestHarness.runBenchmark(TestHarness.java:299)
	at dacapo.TestHarness.main(TestHarness.java:240)
	at Harness.main(Harness.java:5)

----------------------------------------------------------------------

>Comment By: Peter Donald (peter_donald)
Date: 2007-05-23 11:14

Message:
Logged In: YES 
user_id=1642927
Originator: NO

The failure is covered by "[ 1722506 ] dacapo eclipse fails EOF
exceptions"

----------------------------------------------------------------------

Comment By: Robin Garner (rgarner)
Date: 2007-03-11 11:39

Message:
Logged In: YES 
user_id=203294
Originator: YES

This issue seems to be fixed - Eclipse now fails at a later point.  Rather
than close this and open a new issue, here's the latest stack dump:

/home/robing/tmp/dacapo-nightly-20070309/rvm_trunk/dist/FastAdaptiveGenMS_ia32-linux/rvm
-Declipse.java.home=/usr/lib/j2se/1.4 -Xmx512m -Xms512m -jar
dacapo-20070309.jar -s default -n 2 -scratch /tmp/24943 eclipse
===== DaCapo eclipse starting warmup =====
<setting up workspace...>
<creating
projects..............................................................>
<running tests at level 0...>
<performing build tests...>
	org.apache.ant (not open) opening cleaning building
	org.junit (not open) opening cleaning building
	org.eclipse.osgi (not open) opening cleaning building
<performing type hierarchy tests...>
	Hierarchy: org.eclipse.help.internal HelpPlugin
java.io.EOFException
	at java.lang.Throwable.fillInStackTrace(Throwable.java:106)
	at java.lang.Throwable.<init>(Throwable.java:50)
	at java.lang.Exception.<init>(Exception.java:66)
	at java.io.IOException.<init>(IOException.java:61)
	at java.io.EOFException.<init>(EOFException.java:63)
	at java.io.DataInputStream.readFully(DataInputStream.java:285)
	at java.io.DataInputStream.readInt(DataInputStream.java:320)
	at
org.eclipse.jdt.internal.core.index.DiskIndex.readCategoryTable(DiskIndex.java:555)
	at
org.eclipse.jdt.internal.core.index.DiskIndex.addQueryResults(DiskIndex.java:170)
	at org.eclipse.jdt.internal.core.index.Index.query(Index.java:118)
	at
org.eclipse.jdt.internal.core.search.matching.SuperTypeReferencePattern.queryIn(SuperTypeReferencePattern.java:234)
	at
org.eclipse.jdt.internal.core.search.matching.InternalSearchPattern.findIndexMatches(InternalSearchPattern.java:75)
	at
org.eclipse.jdt.internal.core.search.matching.MatchLocator.findIndexMatches(MatchLocator.java:307)
	at
org.eclipse.jdt.internal.core.search.PatternSearchJob.search(PatternSearchJob.java:114)
	at
org.eclipse.jdt.internal.core.search.SubTypeSearchJob.search(SubTypeSearchJob.java:37)
	at
org.eclipse.jdt.internal.core.search.PatternSearchJob.execute(PatternSearchJob.java:64)
	at
org.eclipse.jdt.internal.core.search.processing.JobManager.performConcurrentJob(JobManager.java:261)
	at
org.eclipse.jdt.internal.core.hierarchy.IndexBasedHierarchyBuilder.searchAllPossibleSubTypes(IndexBasedHierarchyBuilder.java:493)
	at
org.eclipse.jdt.internal.core.hierarchy.IndexBasedHierarchyBuilder.determinePossibleSubTypes(IndexBasedHierarchyBuilder.java:382)
	at
org.eclipse.jdt.internal.core.hierarchy.IndexBasedHierarchyBuilder.build(IndexBasedHierarchyBuilder.java:119)
	at
org.eclipse.jdt.internal.core.hierarchy.TypeHierarchy.compute(TypeHierarchy.java:320)
	at
org.eclipse.jdt.internal.core.hierarchy.TypeHierarchy.refresh(TypeHierarchy.java:1255)
	at
org.eclipse.jdt.internal.core.CreateTypeHierarchyOperation.executeOperation(CreateTypeHierarchyOperation.java:90)
	at
org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:718)
	at
org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:777)
	at
org.eclipse.jdt.internal.core.SourceType.newTypeHierarchy(SourceType.java:716)
	at
dacapo.eclipse.EclipseTypeHierarchyTests.allTypes(EclipseTypeHierarchyTests.java:27)
	at
dacapo.eclipse.EclipseTypeHierarchyTests.doTests(EclipseTypeHierarchyTests.java:14)
	at dacapo.eclipse.EclipseTests.runtests(EclipseTests.java:100)
	at dacapo.eclipse.HarnessRunner.run(HarnessRunner.java:21)
	at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
	at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
	at dacapo.eclipse.EclipseHarness.iterate(EclipseHarness.java:35)
	at dacapo.Benchmark.run(Benchmark.java:126)
	at dacapo.TestHarness.runBenchmark(TestHarness.java:301)
	at dacapo.TestHarness.main(TestHarness.java:242)
	at Harness.main(Harness.java:5)

----------------------------------------------------------------------

Comment By: Ian Rogers (captain5050)
Date: 2006-11-09 03:01

Message:
Logged In: YES 
user_id=308843

Maybe I was reading a partial result. It seems we're now
getting a different eclipse regression.

Ian

----------------------------------------------------------------------

Comment By: Ian Rogers (captain5050)
Date: 2006-11-09 02:39

Message:
Logged In: YES 
user_id=308843

It looks like this is now passing (from your website). We're
still failing 2 DaCapo tests, but this seems to be the best
result ever? I think we can close the bug anyway (NB I can't
close someone else's bug). I've opened up an RFE on the
reflection problem that was the cause of it. Thanks,

Ian

----------------------------------------------------------------------

Comment By: Ian Rogers (captain5050)
Date: 2006-11-08 06:43

Message:
Logged In: YES 
user_id=308843

I've addressed one issue in 10950, hopefully this will
resolve the regression. We should probably modify how we
perform resolution of classes during reflection to match
that of other JVMs. This patch moves us back to the
behaviour prior to 10944 - ie we resolve classes when we get
their class from their type.

Ian

----------------------------------------------------------------------

Comment By: Ian Rogers (captain5050)
Date: 2006-11-08 00:19

Message:
Logged In: YES 
user_id=308843

This probably relates to patch #10944 which changed the JTOC
layout, but more importantly probably for this bug, changes
parts of VM_Type. Principally these are so that we create a
java.lang.Class wrapper for a VM_Type when the VM_Type is
constructed. This shouldn't be causing this problem so I'm
scratching my head looking for the cause.

Ian

----------------------------------------------------------------------

Comment By: Robin Garner (rgarner)
Date: 2006-11-07 17:18

Message:
Logged In: YES 
user_id=203294

This happens in both uniprocessor and dual processor
configurations, and only started happening from the 4th of
November.  See 
http://cs.anu.edu.au/people/Robin.Garner/dacapo/regressions/ 
for logs and history.

-- Robin

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=712768&aid=1591798&group_id=128805