[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: Fw: [platform-releng-dev] [eclipse-build]Build I20090324-1325 (Timestamp: 200903241325):Automated JUnit testing complete. Test failures/errors occurred.
|
API tools is all re-tagged and ready to go.
Michael Rennie
Curtis Windatt---03/25/2009 09:24:27 AM---I have retagged the pde ui bundles (including ua, ds, doc). Mike is in the process of tagging PDE
![]()
From: | ![]()
Curtis Windatt/Ottawa/IBM@IBMCA |
![]()
To: | ![]()
"Eclipse platform release engineering list." <platform-releng-dev@xxxxxxxxxxx> |
![]()
Date: | ![]()
03/25/2009 09:24 AM |
![]()
Subject: | ![]()
Re: Fw: [platform-releng-dev] [eclipse-build]Build I20090324-1325 (Timestamp: 200903241325):Automated JUnit testing complete. Test failures/errors occurred. |
I have retagged the pde ui bundles (including ua, ds, doc). Mike is in the process of tagging PDE API tooling.
Curtis
From: | Kim Moir/Ottawa/IBM@IBMCA |
To: | "Eclipse platform release engineering list." <platform-releng-dev@xxxxxxxxxxx> |
Date: | 25/03/2009 06:35 AM |
Subject: | Re: Fw: [platform-releng-dev] [eclipse-build]Build I20090324-1325 (Timestamp: 200903241325):Automated JUnit testing complete. Test failures/errors occurred. |
When a rebuild happens due to compile errors, the contributing team needs to retag all the bundles with compile errors. The build process is designed so that the bundles that a user gets by downloading a zip and by updating with p2 will exactly the same. Thus, if a user had downloaded yesterday's 8am i-build or updated to the 8am i-build they would get the pde bundles with compile errors. If the user then tried to update to yesterday's 1325 build, they wouldn't get the new pde bundles because the tags are the same. So the build process isn't broken.
Andrew is actually giving a talk on this very topic at eclipsecon today :-)
http://www.eclipsecon.org/2009/sessions?id=585
Could the pde team please submit this week's submission again with new tags and I'll start another I-build.
thanks!
Kim
Daniel Megert <daniel_megert@xxxxxxxxxx>
Sent by: platform-releng-dev-bounces@xxxxxxxxxxx
03/25/2009 06:15 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 | Fw: [platform-releng-dev] [eclipse-build]Build I20090324-1325 (Timestamp: 200903241325):Automated JUnit testing complete. Test failures/errors occurred. |
|
OK, I think I found the problem: when PDE fixed their contribution they
only retagged the pde.core bundle which they missed previously. Now, it
looks like all source of the build is checked out from the CVS repository
and compiled and hence no compile errors get reported during the build.
However, when the build is assembled p2 (repo) is used and the old pde.ui
bundle gets used as the version did no change.
If this is correct then we urgently need to fix the build process so that
the source used to compile and the bits used to assemble the build are the
same. Otherwise the result is doomed as the latest test failures show.
Dani
----- Forwarded by Daniel Megert/Zurich/IBM on 25.03.2009 11:07 -----.
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Daniel Megert/Zurich/IBM |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|"Eclipse platform release engineering list." <platform-releng-dev@xxxxxxxxxxx> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|25.03.2009 10:07 |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Re: [platform-releng-dev] [eclipse-build]Build I20090324-1325 (Timestamp: 200903241325):Automated JUnit testing complete. Test failures/errors|
|occurred. |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
The JDT UI and LTK failures are caused by compile errors in PDE types. I
would have expected this from the 0800 build but not after PDE corrected
its build input and after seeing no compile errors reported by the build.
Below is the compile error.
Kim, could it be that the results got mingled? They look the same as in the
0800 build where there were indeed PDE compiler errors. Or maybe the PDE
team has a clue what's wrong here.
Dani
Unresolved compilation problems: The import
org.eclipse.pde.internal.core.text.bundle cannot be resolved The method
getBundle(IFile, IProgressMonitor) from the type BundleManifestChange
refers to the missing type Bundle BundleTextChangeListener cannot be
resolved to a type BundleTextChangeListener cannot be resolved to a type
BundleModel cannot be resolved to a type BundleSymbolicNameHeader cannot be
resolved to a type BundleSymbolicNameHeader cannot be resolved to a type
java.lang.Error: Unresolved compilation problems:
The import org.eclipse.pde.internal.core.text.bundle cannot be resolved
The method getBundle(IFile, IProgressMonitor) from the type
BundleManifestChange refers to the missing type Bundle
BundleTextChangeListener cannot be resolved to a type
BundleTextChangeListener cannot be resolved to a type
BundleModel cannot be resolved to a type
BundleSymbolicNameHeader cannot be resolved to a type
BundleSymbolicNameHeader cannot be resolved to a type
at
org.eclipse.pde.internal.ui.refactoring.ContainerRenameParticipant.<init>
(ContainerRenameParticipant.java:25)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at java.lang.Class.newInstance0(Class.java:350)
at java.lang.Class.newInstance(Class.java:303))
at
org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension
(RegistryStrategyOSGI.java:170)
at
org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension
(ExtensionRegistry.java:874)
at
org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension
(ConfigurationElement.java:243):
at
org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension
(ConfigurationElementHandle.java:51)
at
org.eclipse.ltk.internal.core.refactoring.ParticipantDescriptor.createParticipant
(ParticipantDescriptor.java:86)
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|eclipse-releng@xxxxxxxxxxx |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|platform-releng-dev@xxxxxxxxxxx |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|25.03.2009 04:04 |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|[platform-releng-dev] [eclipse-build]Build I20090324-1325 (Timestamp: 200903241325):Automated JUnit testing complete. Test failures/errors |
|occurred. |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
Build I20090324-1325 (Timestamp: 200903241325): Automated JUnit testing is
complete. Test failures/errors occurred in the following:
org.eclipse.jdt.ui.tests.refactoring_linux.gtk.x86
org.eclipse.jdt.ui.tests.refactoring_linux.gtk.x86_6.0
org.eclipse.jdt.ui.tests.refactoring_macosx.carbon.ppc_5.0
org.eclipse.jdt.ui.tests.refactoring_win32.win32.x86
org.eclipse.jdt.ui.tests.refactoring_win32.win32.x86_6.0
org.eclipse.ltk.core.refactoring.tests_linux.gtk.x86
org.eclipse.ltk.core.refactoring.tests_linux.gtk.x86_6.0
org.eclipse.ltk.core.refactoring.tests_macosx.carbon.ppc_5.0
org.eclipse.ltk.core.refactoring.tests_win32.win32.x86
org.eclipse.ltk.core.refactoring.tests_win32.win32.x86_6.0
org.eclipse.pde.ui.tests_linux.gtk.x86
org.eclipse.pde.ui.tests_linux.gtk.x86_6.0
org.eclipse.pde.ui.tests_macosx.carbon.ppc_5.0
org.eclipse.pde.ui.tests_win32.win32.x86
org.eclipse.pde.ui.tests_win32.win32.x86_6.0
org.eclipse.releng.tests_win32.win32.x86_6.0
HTTP Download:
http://download.eclipse.org/eclipse/downloads/drops/I20090324-1325
_______________________________________________
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

