Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 243476

Summary: Test failure in PatchTest5
Product: [Eclipse Project] Equinox Reporter: John Arthorne <john.arthorne>
Component: p2Assignee: P2 Inbox <equinox.p2-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: pascal
Version: 3.4   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description John Arthorne CLA 2008-08-07 14:19:28 EDT 
This failure occurred in I20080806-1300

unit.framework.AssertionFailedError: expected:<4> but was:<0>
at org.eclipse.equinox.p2.tests.planner.PatchTest5.testInstall(PatchTest5.java:53)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206)
at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:35)
at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:31)
at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:574)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:195)
at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:32)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
at org.eclipse.core.launcher.Main.main(Main.java:30)
Comment 1 John Arthorne CLA 2008-08-07 14:38:58 EDT 
This test did not fail for me when run on my machine, either run alone or as part of the entire p2 test suite. I'll keep this open to figure out if there is an intermittent failure here.  From looking at the test itself it's hard to imagine a reason for timing to affect the outcome.
Comment 2 John Arthorne CLA 2008-09-16 10:35:39 EDT 
This failed again in the 3.5 M2 test candidate build, so I have disabled the test until we find the source of the problem.
Comment 3 Pascal Rapicault CLA 2008-11-25 15:36:29 EST 

*** This bug has been marked as a duplicate of bug 254481 ***