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

Bug 363720

Summary: Test failures due to expired keystore
Product: [Eclipse Project] PDE Reporter: DJ Houghton <dj.houghton>
Component: BuildAssignee: DJ Houghton <dj.houghton>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: aniefer, curtis.windatt.public
Version: 3.8Keywords: readme
Target Milestone: 3.8 M4   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:
Bug Depends on:    
Bug Blocks: 363994    

Description DJ Houghton CLA 2011-11-14 11:36:30 EST 
There are test failures in the latest builds because the keystore in the tests has expired. I'll generate a new one.
Comment 2 Curtis Windatt CLA 2011-11-16 09:51:32 EST 
Are the failures in the I build related?

http://download.eclipse.org/eclipse/downloads/drops/I20111115-0800/testresults/html/org.eclipse.pde.build.tests_macosx.cocoa.x86_5.0.html

Missing entry in archive: [META-INF/PDE_BUIL.DSA]

junit.framework.AssertionFailedError: Missing entry in archive: [META-INF/PDE_BUIL.DSA]
at org.eclipse.pde.build.tests.PDETestCase.assertZipContents(PDETestCase.java:226)
at org.eclipse.pde.build.tests.PDETestCase.assertZipContents(PDETestCase.java:232)
at org.eclipse.pde.build.tests.PDETestCase.assertZipContents(PDETestCase.java:200)
at org.eclipse.pde.build.internal.tests.p2.PublishingTests.testBug265726(PublishingTests.java:928)
at org.eclipse.pde.build.tests.PDETestCase.runTest(PDETestCase.java:61)
...
Comment 3 DJ Houghton CLA 2011-11-16 10:56:17 EST 
Not sure, I had problems running these tests locally yesterday and was hoping their failures in the nightly was just a blip. I'll try and talk to Andrew today to see if he has background info.
Comment 4 DJ Houghton CLA 2011-11-16 13:38:06 EST 
With Andrew's help we figured out it was because the keystore was generated with the wrong algorithm. I've regenerated it as well as included a readme (with instructions) in the tests so we know better for next time.

Also another tidbit of info from Andrew is if you are trying to run some of the tests in 4.x and they are failing because of dependencies, you may have to set:
		properties.put("filteredDependencyCheck", "false");
This is because of the difference in feature structure between 3.x and 4.x. We may have to do this for all our tests once we switch over to testing against 4.x in the automated builds.
Comment 5 Curtis Windatt CLA 2011-12-06 17:34:27 EST 
The tests have been passing fine during milestone week.  Verified.