Re: [platform-releng-dev] [eclipse-build]Build I20090304-0834 (Timestamp

[Thomas Watson <tjwatson@xxxxxxxxxx>]

The issue is more specific issue with fragment bundles which contribute to a package which already exists in the host bundle. Packages that are split across multiple host bundles are not effected because the certificate check is only done for classes loaded by the same class loader.

Tom



John Arthorne ---03/05/2009 09:26:33 AM---To clarify, the problem in OSGi was a problem where the same package contained classes with different signatures. So, there is

From:	John Arthorne <John_Arthorne@xxxxxxxxxx>
To:	"Eclipse platform release engineering list." <platform-releng-dev@xxxxxxxxxxx>
Date:	03/05/2009 09:26 AM
Subject:	Re: [platform-releng-dev] [eclipse-build]Build I20090304-0834 (Timestamp: 200903040834):Automated JUnit testing complete. Test failures/errors occurred.

---

To clarify, the problem in OSGi was a problem where the same package contained classes with different signatures. So, there is a potential problem here for bundles with split packages.

John Arthorne/Ottawa/IBM@IBMCA
Sent by: platform-releng-dev-bounces@xxxxxxxxxxx

03/05/2009 10:11 AM

Please respond to
"Eclipse platform release engineering list." <platform-releng-dev@xxxxxxxxxxx>

To	"Eclipse platform release engineering list." <platform-releng-dev@xxxxxxxxxxx>
cc
Subject	Re: [platform-releng-dev] [eclipse-build]Build I20090304-0834 (Timestamp: 200903040834):Automated JUnit testing complete. Test failures/errors occurred.

I don't see a problem here, since the old certificate was valid at the time it was used to create the signature. We had two similar certificate switches at the start of M5, and apart from some isolated cases where orbit bundles were signed with both certificates, it didn't cause any problems. Even if the 3.5 release contains bundles signed with the old certificates (because it didn't change since the certificates changed), it should be fine.

Thomas Watson <tjwatson@xxxxxxxxxx>
Sent by: platform-releng-dev-bounces@xxxxxxxxxxx

03/05/2009 09:55 AM

Please respond to
"Eclipse platform release engineering list." <platform-releng-dev@xxxxxxxxxxx>

To	"Eclipse platform release engineering list." <platform-releng-dev@xxxxxxxxxxx>
cc
Subject	Re: [platform-releng-dev] [eclipse-build]Build I20090304-0834 (Timestamp: 200903040834):Automated JUnit testing complete. Test failures/errors occurred.

This is a good point. It is similar to the issue you had with incorrect .api_description files. Should we force everyone to update their tags for all projects? Or do we consider this a point in time issue for developers living with I-Builds? At the end of the release normal users will download the full image and start from scratch so they will get the correct signers for all bundles.

BTW, does releng tools support retagging projects with no changes? I did not see a way and I had to manually retag equinox.common for the .api_description issue.

Tom

Olivier Thomann ---03/05/2009 08:36:55 AM---I think this is also a problem for users updating using p2 update from

From:	Olivier Thomann <Olivier_Thomann@xxxxxxxxxx>
To:	"Eclipse platform release engineering list." <platform-releng-dev@xxxxxxxxxxx>
Date:	03/05/2009 08:36 AM
Subject:	Re: [platform-releng-dev] [eclipse-build]Build I20090304-0834 (Timestamp: 200903040834):Automated JUnit testing complete. Test failures/errors occurred.

---

I think this is also a problem for users updating using p2 update from 
build to build. Even if the repo is flushed, as long as the version has 
not changed for all bundles, the old certificates will still be used by 
users that are using p2 update from build to build. The downloaded zips 
will contain the new certificates, but not when using p2 update.
In this case we can end up using old certificates for a long time.
Should not we force all bundles to change their versions in order to make 
sure we get rid of the old certificates ?
Did I miss something ?

Do we have a way to validate that all bundles are using the new 
certificates ?

Olivier




Thomas Watson <tjwatson@xxxxxxxxxx> 
Sent by: platform-releng-dev-bounces@xxxxxxxxxxx
2009-03-05 09:11
Please respond to
"Eclipse platform release engineering list." 
<platform-releng-dev@xxxxxxxxxxx>


To
"Eclipse platform release engineering list." 
<platform-releng-dev@xxxxxxxxxxx>
cc

Subject
Re: [platform-releng-dev]       [eclipse-build]Build    I20090304-0834 
(Timestamp:     200903040834):Automated JUnit testing complete. Test 
failures/errors occurred.






Thanks Kim and Martin.

This does appear to be the cause. My eye sight was not good enough in the 
middle of the night to notice that 
org.eclipse.core.runtime.compatibility.registry was signed with the old 
certificate (evident by the ECLIPSE.SF file) and the 
org.eclipse.equinox.registry bundle is signed by the new certificate 
(evident by the ECLIPSEF.SF file, not the extra 'F' character!!). This 
causes the mis-matching in certificates.

This also explains why the nightly builds pass, because we always have a 
version qualifier change then.

Tom



Kim Moir ---03/05/2009 06:09:31 AM---Yes, the certificate changed. When we 
run a build, we use the mirror app to compare the bundles created in the 
build, while u


From:

Kim Moir <Kim_Moir@xxxxxxxxxx>

To:

"Eclipse platform release engineering list." 
<platform-releng-dev@xxxxxxxxxxx>

Date:

03/05/2009 06:09 AM

Subject:

Re: [platform-releng-dev] [eclipse-build]Build I20090304-0834 (Timestamp: 
200903040834):Automated JUnit testing complete. Test failures/errors 
occurred.




Yes, the certificate changed. When we run a build, we use the mirror app 
to compare the bundles created in the build, while using the existing 
bundles in the repo as a baseline. Thus the older bundles with the same 
version and qualifier get incorporated into the new build. Since we have a 
new certificate, I think it would be wise for me to clean the i-builds 
repo to ensure we are building with bundles with the new certificate. 

Kim 



Thomas Watson <tjwatson@xxxxxxxxxx> 
Sent by: platform-releng-dev-bounces@xxxxxxxxxxx 
03/05/2009 12:33 AM 


Please respond to
"Eclipse platform release engineering list." 
<platform-releng-dev@xxxxxxxxxxx>



To
"Eclipse platform release engineering list." 
<platform-releng-dev@xxxxxxxxxxx> 
cc

Subject
Re: [platform-releng-dev] [eclipse-build]Build I20090304-0834 (Timestamp: 
200903040834):Automated JUnit testing complete. Test failures/errors 
occurred.








According to the logs captured during the osgi tests (
http://download.eclipse.org/eclipse/downloads/drops/I20090304-0834/testresults/linux.gtk.x86/org.eclipse.osgi.tests.AutomatedTests.txt
) it appears there is a difference in the certificates used to sign 
org.eclipse.equinox.registry and 
org.eclipse.core.runtime.compatibility.registry. Did something change in 
the signing process from the last I-Build to the respin? Another 
possibility is the org.eclipse.core.runtime.compatibility.registry bundle 
is getting overwritten during the test pass. I think we had similar issues 
with the junit directory bundle in the past.

At this point I don't think this failure affects the quality of the build. 
I will investigate more tomorrow. Tracked by bug 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=267150

Tom



eclipse-releng---03/04/2009 04:56:50 PM---Build I20090304-0834 (Timestamp: 
200903040834): Automated JUnit testing is complete. Test failures/errors 
occurred in the fol 

From: 

eclipse-releng@xxxxxxxxxxx 

To: 

platform-releng-dev@xxxxxxxxxxx 

Date: 

03/04/2009 04:56 PM 

Subject: 

[platform-releng-dev] [eclipse-build]Build I20090304-0834 (Timestamp: 
200903040834):Automated JUnit testing complete. Test failures/errors 
occurred.




Build I20090304-0834 (Timestamp: 200903040834):  Automated JUnit testing 
is complete.  Test failures/errors occurred in the following: 

org.eclipse.equinox.p2.tests_macosx.carbon.ppc_5.0
org.eclipse.osgi.tests_linux.gtk.x86
org.eclipse.osgi.tests_linux.gtk.x86_6.0
org.eclipse.osgi.tests_macosx.carbon.ppc_5.0
org.eclipse.osgi.tests_win32.win32.x86
org.eclipse.osgi.tests_win32.win32.x86_6.0
org.eclipse.pde.api.tools.tests_linux.gtk.x86
org.eclipse.pde.build.tests_linux.gtk.x86

HTTP Download:

http://download.eclipse.org/eclipse/downloads/drops/I20090304-0834 


_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev

_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev

_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev


_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev

_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev