Summary: | [perfs] One failure while running Platform/Ant performance tests | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Frederic Fusier <frederic_fusier> |
Component: | Ant | Assignee: | Platform-Ant-Inbox <platform-ant-inbox> |
Status: | VERIFIED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | darin.eclipse, Michael_Rennie |
Version: | 3.5 | Keywords: | performance, test |
Target Milestone: | 3.5 M7 | ||
Hardware: | PC | ||
OS: | Linux-GTK | ||
Whiteboard: | |||
Bug Depends on: | |||
Bug Blocks: | 270824 |
Description
Frederic Fusier
2009-04-01 09:28:24 EDT
Note that this failure does not occur on Windows machine, only on Linux ones... The normal test suite also had a failure (I20090401-1325) for a different test but the same symptoms - testRunToLineSkipBreakpointSepVM: Program did not suspend, launch terminated. junit.framework.AssertionFailedError: Program did not suspend, launch terminated. at org.eclipse.ant.tests.ui.debug.AbstractAntDebugTest.launchAndWait(AbstractAntDebugTest.java:170) at org.eclipse.ant.tests.ui.debug.AbstractAntDebugTest.launchAndWait(AbstractAntDebugTest.java:144) at org.eclipse.ant.tests.ui.debug.AbstractAntDebugTest.launchToLineBreakpoint(AbstractAntDebugTest.java:347) at org.eclipse.ant.tests.ui.debug.AbstractAntDebugTest.launchToLineBreakpoint(AbstractAntDebugTest.java:330) at org.eclipse.ant.tests.ui.debug.RunToLineTests.runToLine(RunToLineTests.java:168) at org.eclipse.ant.tests.ui.debug.RunToLineTests.testRunToLineSkipBreakpointSepVM(RunToLineTests.java:112) at org.eclipse.ant.tests.ui.AbstractAntUIBuildTest.access$0(AbstractAntUIBuildTest.java:1) at org.eclipse.ant.tests.ui.AbstractAntUIBuildTest$1.run(AbstractAntUIBuildTest.java:44) at java.lang.Thread.run(Thread.java:619) I cannot see the failure in the I20090410-0800 perf results page. Coudl you confirm that this bug has been fixed? TIA We have had very limited success reproducing the bug locally. It appears to be a timing issue - we wait for a suspend event that sometimes seems to never come. This is a transient failure that has happened historically in some debug tests. Unless the problem persists reliably, I suggest to mark this one as works for me. Verified for RC1 with I20090430-2300 (aka M7) results (In reply to comment #6) > Verified for RC1 with I20090430-2300 (aka M7) results > Sorry, should read: Verified for M7... |