Re: [cbi-dev] Problems building Eclipse Platform from the R4_3_maintance

[David M Williams <david_williams@xxxxxxxxxx>]

> And
then I get the error about the empty zip file. Do you know if there is
a way of working out what zip file is causing the problem?

No, not directly ... but,
I've sometimes found it helpful to look directly at, or in, the /target
folder and see what's there. 

The other "tricks"
I use when debugging is to of course search the log for 
/\[ERROR\] 
to see if there was was an
earlier ERROR
And occasionally search for
things like "could not download", for "failed to" ....
but, I've not found a good heuristic for these phrases, and usually has
lots of false hits. 

This appears complicated
enough that I suggest you open a bug ... I think in the "CBI"
component, under "Technology" 
 https://bugs.eclipse.org/bugs/enter_bug.cgi?product=CBI

If nothing else, would make it easier
to attach logs (zipped up, they get a lot smaller)  or directory listing
of target, and similar. 

Thanks, 





From:      
 Phil Mason <phil.mason@xxxxxxxxxxxx>
To:      
 Common-build Developers
discussion <cbi-dev@xxxxxxxxxxx>, 
Date:      
 02/26/2014 11:23 AM
Subject:    
   Re: [cbi-dev]
Problems building Eclipse Platform from the R4_3_maintance branch
Sent by:    
   cbi-dev-bounces@xxxxxxxxxxx

---

> ... if you have your
own one company repo
 
No, I’m trying to make things
as simple as possible. All I do is clone the upstream repos and then run
“mvn clean verify” on them. In fact I’m now going out of my way to ensure
that each run is as clean as possible. To that end I’m using -Dmaven.repo.local
to specify a different .m2/repo for each build run, which, like you, I
suspect is mostly paranoia but until I can work out what caused my builds
to transition from success to failure that seems to be the order of the
day.
 
> the same "pack.gz"
file each time. So, if you can look at detail or the log,
 
I’m running mvn with -e
and -X which I think should be all the logging I can get and the last thing
I see before the problem is 
 
  [INFO] --- tycho-packaging-plugin:0.19.0:package-feature
(default-package-feature) @ org.eclipse.e4.rcp ---
  [DEBUG] Configuring
mojo org.eclipse.tycho:tycho-packaging-plugin:0.19.0:package-feature from
plugin realm ClassRealm[plugin>org.eclipse.tycho:tycho-packaging-plugin:0.19.0,
parent: sun.misc.Launcher$AppClassLoader@2771f735]
  [DEBUG] Configuring
mojo 'org.eclipse.tycho:tycho-packaging-plugin:0.19.0:package-feature'
with basic configurator -->
  [DEBUG]   (s)
addMavenDescriptor = false
  [DEBUG]   (f)
archive = org.apache.maven.archiver.MavenArchiveConfiguration@68fb4f1f
  [DEBUG]   (f)
basedir = /dev/shm/pmason/eclipse.platform.releng.aggregator/eclipse.platform.ui/features/org.eclipse.e4.rcp
  [DEBUG]   (f)
deployableFeature = false
  [DEBUG]   (f)
finalName = org.eclipse.e4.rcp-1.2.2-SNAPSHOT
  [DEBUG]   (f)
outputDirectory = /dev/shm/pmason/eclipse.platform.releng.aggregator/eclipse.platform.ui/features/org.eclipse.e4.rcp/target
  [DEBUG]   (f)
project = MavenProject: org.eclipse.e4.feature:org.eclipse.e4.rcp:1.2.2-SNAPSHOT
@ /dev/shm/pmason/eclipse.platform.releng.aggregator/eclipse.platform.ui/features/org.eclipse.e4.rcp/pom.xml
  [DEBUG]   (f)
qualifier = v20140206-1358
  [DEBUG]   (f)
session = org.apache.maven.execution.MavenSession@3a646783
  [DEBUG]   (f)
strictBinIncludes = false
  [DEBUG]   (f)
target = /dev/shm/pmason/eclipse.platform.releng.aggregator/eclipse.platform.ui/features/org.eclipse.e4.rcp/target/site
  [DEBUG]   (f)
useDefaultExcludes = true
  [DEBUG] -- end configuration
--
 
After which it goes on to
list the reactor summary which shows that 
 
[INFO] org.eclipse.equinox.launcher.gtk.aix.ppc64
........ SUCCESS [0.761s]
[INFO] org.eclipse.e4.rcp
................................ FAILURE [0.195s]
 
And then I get the error
about the empty zip file. Do you know if there is a way of working out
what zip file is causing the problem?
 
All the best
 
Phil
 
From: cbi-dev-bounces@xxxxxxxxxxx
[mailto:cbi-dev-bounces@xxxxxxxxxxx]
On Behalf Of David M Williams
Sent: 25 February 2014 10:25 PM
To: Common-build Developers discussion
Subject: Re: [cbi-dev] Problems building Eclipse Platform from the
R4_3_maintance branch
 

And, sorry I didn't think of this earlier ... but ... the "empty zip
file" failure sounds like exactly what you get when p2 has trouble
with a pack.gz file. There are several reasons why it might, and p2 itself
does a fair job of recovering ... but ... if you have your own one company
repo, or something like that, you might be having trouble with the same
"pack.gz" file each time. So, if you can look at detail or the
log, or file, and see which one it is, there might be ways of finding out
if it is truely a bad pack.gz file, or ... if its one of the other 101
things that can go wrong with pack.gz files. (Its sometimes hard to tell,
since the tmp/"zip" file that's temporarily created has a funny
hash name, but you can still sometimes 'peek inside" or something
to see if it says anything). 

I'm not sure (perhaps Tycho expert could speak up here?) but I don't think
Tycho always uses p2 "directly" -- I know it does for some things
... but not sure it does for downloading pack.gz files. (Bug
373173 )
So, I'm not sure the usual "p2 solutions" would work, but if
it does use p2 directly there are ways to turn off "mirroring"
in case you are getting the bad file from a "bad mirror" (That's
the -Declipse.p2.mirrors=false in my script) ... plus, if you have to "use
a company mirror" or something then you might try 
-Dorg.eclipse.update.jarprocessor.pack200=@none
to skip using pack.gz files completely (it's take longer, but ... longer
and works, is better than shorter and fails). 

Lastly ... There is a wiki with some good tips on "testing mirroring"
... such as which .options to turn on, to log which mirrors each jar comes
from, etc. It'd be a full days work ... but, might be very helpful to you.
Also ... this all assumes Tycho uses p2 to "fetch from mirrors"
which I am not 100% sure of.  That wiki is 
https://wiki.eclipse.org/Equinox/p2/p2.mirrorsURL
or more specifically I'm thinking the .options in this section might be
helpful? 
https://wiki.eclipse.org/Equinox/p2/p2.mirrorsURL#How_to_test.3F
(Now that I think of it, I'm not even sure how to specify .options with
Tycho ... but ... bet some reader of this list does). 

Or ... could be my advice is way off base :/ ... and, sorry, doubt I'd
have time to try your script for some time.  Perhaps you could try
from a different network ... have a cup of coffee while you use their free
wi-fi or something :) 

Hope some of this helps you or someone else! 





From:        Phil
Mason <phil.mason@xxxxxxxxxxxx>
To:        Common-build
Developers discussion <cbi-dev@xxxxxxxxxxx>,
Date:        02/25/2014
04:39 PM 
Subject:        Re:
[cbi-dev] Problems building Eclipse Platform from the R4_3_maintance branch
Sent by:        cbi-dev-bounces@xxxxxxxxxxx

---

Hi David, 
  
> Could it be -Dtycho.localArtifacts=ignore ?
  
This doesn’t seem to be enough on its own, I still get the “empty zip
file” failure. 
  
> What platform are you using? Linux is what I build on.
  
I’m building on RHEL5 (though the tools like Java and Maven, are not the
default versions). 
  
> I create my own "tmp" repo and local maven repo.
  
Are these the same repo each time or are they cleaned out in between builds?
  
I’m working with your script, trying to modify it in the minimum way required
so that it will run on my systems, so far I have only had the same failure.
I’m still waiting for a couple of builds to complete though so I can’t
be sure it doesn’t contain the clue I’m looking for. I’ll get back to
you in the morning. 
  
I've attached an updated version of the building script I was using and
my toolchain.xml. This version uses a temporary folder for the .m2/repository
folder (so it should be clean before each build) and takes an argument
for what to checkout and it fails with both R4_3 and R4_3_maintenance.
The only thing that should need changing is some paths in the toolchains.xml
file (or simply replace it with the one from your ~/.m2).
  
I think this script follows pretty closely the platform building instructions
here 
  
http://wiki.eclipse.org/Platform-releng/Platform_Build
  
Are you able to run this and see if it fails for you?
  
Thanks in advance if you are.
  
All the best 
  
Phil 
  
  
From: cbi-dev-bounces@xxxxxxxxxxx
[mailto:cbi-dev-bounces@xxxxxxxxxxx]
On Behalf Of David M Williams
Sent: 21 February 2014 3:41 AM
To: Common-build Developers discussion
Subject: Re: [cbi-dev] Problems building Eclipse Platform from the
R4_3_maintance branch 
  
I must admit, I've tried 3 or 4 times, and always works for me. The type
of scripts I use I put in repo just so others can see them as examples
...   
http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/scripts/dwExamples?h=david_williams/testbranch
in case they help someone see the "key differences". 
Could it be -Dtycho.localArtifacts=ignore
? 
Notice I "unset" a lot of variables and set minimal path to make
sure nothing else is "influencing" the build. 
I create my own "tmp" repo and local maven repo. 
But I've tried R4_3_maintenance (twice), master, and the tag R4_3_1 and
all built to completion. 
What platform are you using? Linux is what I build on. 
Hope the scripts gives you some ideas. 
Good luck, 






From:        Thanh
Ha <thanh.ha@xxxxxxxxxxx>
To:        cbi-dev@xxxxxxxxxxx,
Date:        02/20/2014
02:28 PM 
Subject:        Re:
[cbi-dev] Problems building Eclipse Platform from the R4_3_maintance branch
Sent by:        cbi-dev-bounces@xxxxxxxxxxx

---

So it failed again with "org.eclipse.platform-feature" but then
after 
this failure the build succeeded for me.

Unfortunately I don't know what the problem is (maybe others on the 
mailing list might know) but it seems if you keep rerunning the build 
again without cleaning up eventually it'll succeed.


Thanh



On 19/02/14 11:24 PM, Thanh Ha wrote:
> Hi Phil,
>
> I was able to finally reproduce the issue after doing a fresh clone
> and clearing my ~/.m2/repository. Except in my case it failed on a
> different module than what you pasted. Below is the full error output
> of what I saw on my run. It looks like tycho-packaging-plugin tries
to 
> open a zip file and fails thus throwing the error.
>
> What I noticed is that for the module the build fails on the /target
> directory is always empty at this state so I suspect the reason the
> zip part fails is because it's trying to check an a zip file that
> doesn't exist assuming it's looking for the file that should be in
> /target.
>
> If I run "mvn clean verify -Pbree-libs" again (without cleaning
> anything up) after getting this error the build actually gets further
> and then failed on a different module but if I build again that module
> succeeds the next time. What I've noticed is it always failes on 
> "feature" modules and I'm not sure why but seems pretty
odd. It seems 
> as if these modules just fail on first build but succeed on 2nd build
> of them.
>
> At the moment I've run into this failure twice for 2 seperate modules
> (o.e.equinox.p2.core-feature and org.eclipse.jdt-feature) and am 
> rerunning a 3rd build now. I'll see how much further it gets, it's
> late for me now so I'll check up on the build tomorrow.
>
>
> Thanh
>
>
> [ERROR] Failed to execute goal 
> org.eclipse.tycho:tycho-packaging-plugin:0.19.0:package-feature 
> (default-package-feature) on project 
> org.eclipse.equinox.p2.rcp.feature: Execution default-package-feature
> of goal 
> org.eclipse.tycho:tycho-packaging-plugin:0.19.0:package-feature 
> failed: Could not determine installation size: error in opening zip
> file -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal 
> org.eclipse.tycho:tycho-packaging-plugin:0.19.0:package-feature 
> (default-package-feature) on project 
> org.eclipse.equinox.p2.rcp.feature: Execution default-package-feature
> of goal 
> org.eclipse.tycho:tycho-packaging-plugin:0.19.0:package-feature 
> failed: Could not determine installation size
>         at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
>         at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>         at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>         at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>         at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>         at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>         at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>         at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>         at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
>         at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>         at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:606)
>         at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>         at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>         at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>         at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-package-feature of goal 
> org.eclipse.tycho:tycho-packaging-plugin:0.19.0:package-feature 
> failed: Could not determine installation size
>         at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
>         at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>         ... 19 more
> Caused by: java.lang.RuntimeException: Could not determine 
> installation size
>         at 
> org.eclipse.tycho.packaging.FeatureXmlTransformer.getInstallSize(FeatureXmlTransformer.java:130)
>         at 
> org.eclipse.tycho.packaging.FeatureXmlTransformer$1.visitPlugin(FeatureXmlTransformer.java:77)
>         at 
> org.eclipse.tycho.core.osgitools.AbstractArtifactDependencyWalker.traversePlugin(AbstractArtifactDependencyWalker.java:205)
>         at 
> org.eclipse.tycho.core.osgitools.AbstractArtifactDependencyWalker.traverseFeature(AbstractArtifactDependencyWalker.java:85)
>         at 
> org.eclipse.tycho.core.osgitools.AbstractArtifactDependencyWalker.traverseFeature(AbstractArtifactDependencyWalker.java:62)
>         at 
> org.eclipse.tycho.packaging.FeatureXmlTransformer.transform(FeatureXmlTransformer.java:47)
>         at 
> org.eclipse.tycho.packaging.PackageFeatureMojo.expandVersionQualifiers(PackageFeatureMojo.java:233)
>         at 
> org.eclipse.tycho.packaging.PackageFeatureMojo.execute(PackageFeatureMojo.java:116)
>         at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>         ... 20 more
> Caused by: java.util.zip.ZipException: error in opening zip file
>         at java.util.zip.ZipFile.open(Native Method)
>         at java.util.zip.ZipFile.<init>(ZipFile.java:215)
>         at java.util.zip.ZipFile.<init>(ZipFile.java:145)
>         at java.util.jar.JarFile.<init>(JarFile.java:153)
>         at java.util.jar.JarFile.<init>(JarFile.java:117)
>         at 
> org.eclipse.tycho.packaging.FeatureXmlTransformer.getInstallSize(FeatureXmlTransformer.java:116)
>         ... 28 more
>
> _______________________________________________
> cbi-dev mailing list
> cbi-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cbi-dev
>

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cbi-dev
[attachment "brcm-toolchains.xml" deleted by David M Williams/Raleigh/IBM]
[attachment "build.sh" deleted by David M Williams/Raleigh/IBM]
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cbi-dev_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cbi-dev