Re: [eclipse-dev] Problems running JDT Core Model JUnit tests in N200310

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [eclipse-dev] Problems running JDT Core Model JUnit tests in N20031007 and I20031007

From: Sonia Dimitrov <Sonia_Dimitrov@xxxxxxxxxx>
Date: Tue, 7 Oct 2003 13:52:31 -0400
Delivered-to: eclipse-dev@xxxxxxxxxxx
List-archive: <http://dev.eclipse.org/pipermail/eclipse-dev/>
List-help: <mailto:eclipse-dev-request@eclipse.org?subject=help>
List-subscribe: <http://dev.eclipse.org/mailman/listinfo/eclipse-dev>, <mailto:eclipse-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <http://dev.eclipse.org/mailman/listinfo/eclipse-dev>, <mailto:eclipse-dev-request@eclipse.org?subject=unsubscribe>

Here is the console output and thread dump from the JDT Core Model test:

16ms for 200 roots
Dense cycle check (5 participants) : 203 ms
Dense cycle check (10 participants) : 594 ms
Dense cycle check (20 participants) : 968 ms
No cycle check (5 participants) : 281 ms, backward references, one step (projects created and classpaths set in one batch)
No cycle check (10 participants) : 406 ms, backward references, one step (projects created and classpaths set in one batch)
No cycle check (20 participants) : 843 ms, backward references, one step (projects created and classpaths set in one batch)
No cycle check (5 participants) : 156 ms, forward references, one step (projects created and classpaths set in one batch)
No cycle check (10 participants) : 422 ms, forward references, one step (projects created and classpaths set in one batch)
No cycle check (20 participants) : 1109 ms, forward references, one step (projects created and classpaths set in one batch)
No cycle check (5 participants) : 140 ms, backward references, two steps (projects created first, then classpaths are set)
No cycle check (10 participants) : 453 ms, backward references, two steps (projects created first, then classpaths are set)
No cycle check (20 participants) : 750 ms, backward references, two steps (projects created first, then classpaths are set)
No cycle check (5 participants) : 156 ms, forward references, two steps (projects created first, then classpaths are set)
No cycle check (10 participants) : 437 ms, forward references, two steps (projects created first, then classpaths are set)
No cycle check (20 participants) : 828 ms, forward references, two steps (projects created first, then classpaths are set)
""
""
""
Full thread dump Java HotSpot(TM) Client VM (1.4.2-b28 mixed mode):

"Worker-1" prio=5 tid=0x02f17b50 nid=0x72c in Object.wait() [34ef000..34efd94]
at java.lang.Object.wait(Native Method)
- waiting on <0x105238c0> (a org.eclipse.core.internal.jobs.WorkerPool)
at org.eclipse.core.internal.jobs.WorkerPool.sleep(WorkerPool.java:108)
- locked <0x105238c0> (a org.eclipse.core.internal.jobs.WorkerPool)
at org.eclipse.core.internal.jobs.WorkerPool.startJob(WorkerPool.java:134)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

"Worker-0" prio=5 tid=0x02ec39a8 nid=0x648 in Object.wait() [340f000..340fd94]
at java.lang.Object.wait(Native Method)
- waiting on <0x105238c0> (a org.eclipse.core.internal.jobs.WorkerPool)
at org.eclipse.core.internal.jobs.WorkerPool.sleep(WorkerPool.java:108)
- locked <0x105238c0> (a org.eclipse.core.internal.jobs.WorkerPool)
at org.eclipse.core.internal.jobs.WorkerPool.startJob(WorkerPool.java:134)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

"Java indexing" daemon prio=4 tid=0x02e191d8 nid=0xfa4 in Object.wait() [329f000..329fd94]
at java.lang.Object.wait(Native Method)
- waiting on <0x10784220> (a org.eclipse.jdt.internal.core.search.indexing.IndexManager)
at java.lang.Object.wait(Object.java:429)
at org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:358)
- locked <0x10784220> (a org.eclipse.jdt.internal.core.search.indexing.IndexManager)
at java.lang.Thread.run(Thread.java:534)

"Signal Dispatcher" daemon prio=10 tid=0x0003da10 nid=0xfbc waiting on condition [0..0]

"Finalizer" daemon prio=9 tid=0x009bfbd0 nid=0xb5c in Object.wait() [2b5f000..2b5fd94]
at java.lang.Object.wait(Native Method)
- waiting on <0x104f8f68> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)
- locked <0x104f8f68> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)

"Reference Handler" daemon prio=10 tid=0x009be7a0 nid=0x9c0 in Object.wait() [2b1f000..2b1fd94]
at java.lang.Object.wait(Native Method)
- waiting on <0x104f8fd0> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:429)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:115)
- locked <0x104f8fd0> (a java.lang.ref.Reference$Lock)

"main" prio=5 tid=0x00035308 nid=0xc84 in Object.wait() [7e000..7fc3c]
at java.lang.Object.wait(Native Method)
- waiting on <0x107ba930> (a org.eclipse.core.internal.jobs.ImplicitJobs$ThreadJob)
at org.eclipse.core.internal.jobs.ImplicitJobs$ThreadJob.joinRun(ImplicitJobs.java:65)
- locked <0x107ba930> (a org.eclipse.core.internal.jobs.ImplicitJobs$ThreadJob)
at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:195)
at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:113)
at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:94)
at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:1520)
at org.eclipse.core.internal.resources.Resource.delete(Resource.java:624)
at org.eclipse.core.internal.resources.Project.delete(Project.java:274)
at org.eclipse.jdt.core.tests.model.AbstractJavaModelTests.deleteResource(AbstractJavaModelTests.java:492)
at org.eclipse.jdt.core.tests.model.AbstractJavaModelTests.deleteProject(AbstractJavaModelTests.java:467)
at org.eclipse.jdt.core.tests.model.CopyMoveElementsTests.testMoveMethodsWithCancelInDifferentProject(CopyMoveElementsTests.java:2416)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.runTest(SuiteOfTestCases.java:98)
at junit.framework.TestSuite.run(TestSuite.java:203)
at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.superRun(SuiteOfTestCases.java:82)
at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$1.protect(SuiteOfTestCases.java:70)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.run(SuiteOfTestCases.java:79)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:320)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:199)
at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:34)
at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:30)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:298)
at org.eclipse.core.launcher.Main.run(Main.java:764)
at org.eclipse.core.launcher.Main.main(Main.java:598)

"VM Thread" prio=5 tid=0x009fb6c0 nid=0xef0 runnable

"VM Periodic Task Thread" prio=10 tid=0x009fc208 nid=0xe98 waiting on condition
"Suspend Checker Thread" prio=10 tid=0x009c1868 nid=0x6ac runnable

Olivier Thomann/Ottawa/IBM@IBMCA
Sent by: eclipse-dev-admin@xxxxxxxxxxx

10/07/2003 10:50 AM
Please respond to eclipse-dev

To: eclipse-dev@xxxxxxxxxxx
cc:
Subject: Re: [eclipse-dev] Problems running JDT Core Model JUnit tests in N20031007 and I20031007

Could not reproduce. So we definitely need some feedback from the test harness to find out where the tests are hanging and/or the thread dumps. Thanks, Olivier Sonia Dimitrov/Ottawa/I BM@IBMCA To Sent by: eclipse-dev@xxxxxxxxxxx eclipse-dev-admin cc @eclipse.org Subject [eclipse-dev] Problems running JDT 10/07/03 09:28 AM Core Model JUnit tests in N20031007 and I20031007 Please respond to eclipse-dev@eclip se.org The JDT Core Model JUnit tests both "hung" on Windows only in builds N20031007 and I20031007. I was unable to get a thread dump for this, however will try to reproduce when the testing is complete. JDT Core team, please let me know if my assistance is required to troubleshoot this problem any further. Sonia _______________________________________________ eclipse-dev mailing list eclipse-dev@xxxxxxxxxxx http://dev.eclipse.org/mailman/listinfo/eclipse-dev

References:
- Re: [eclipse-dev] Problems running JDT Core Model JUnit tests in N20031007 and I20031007
  - From: Olivier Thomann

Prev by Date: Re: [eclipse-dev] [eclipse-build]Build I20031007 (Timestamp: 200310070800):Automated JUnit Testing complete. Test failures/errors occurred.
Next by Date: Re: [eclipse-dev] [eclipse-build]Build I20031007 (Timestamp: 200310070800):Automated JUnit Testing complete. Test failures/errors occurred.
Previous by thread: Re: [eclipse-dev] Problems running JDT Core Model JUnit tests in N20031007 and I20031007
Next by thread: [eclipse-dev] Proposal to reduce mailing list noise
Index(es):
- Date
- Thread

Breadcrumbs