You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Dominik Stadler <ce...@apache.org> on 2016/10/20 08:27:48 UTC
Fwd: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed
Hi Gumpers!
Since some time one of the steps in the POI builds inside Gump is failing,
see below. We think it is related to the 1 hour timeout that is applied by
default. We do not see any big changes in the POI source code at the time
it started, so am not sure why it started and how to debug/remedy this.
The step compiles a big number of files, but finishes in a few minutes
usually. Our builds on the Apache Jenkins instance usually take up to 40
minutes for the complete build which includes a number of additional steps,
so we are not sure why it is taking so long here, maybe the machine is
quite limited on memory/CPU?
Is there a simple way to try to increase the timeout for this specific
build?
Thanks... Dominik.
---------- Forwarded message ----------
From: Gump [HEAD] :-( <ge...@gump.apache.org>
Date: Thu, Oct 20, 2016 at 3:48 AM
Subject: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed
To: dev@poi.apache.org
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project ooxml-schemas has an issue affecting its community integration.
This issue affects 5 projects,
and has been outstanding for 10 runs.
The current state of this project is 'Failed', with reason 'Build Timed
Out'.
For reference only, the following projects are affected by this:
- ooxml-schemas : POI
- org.apache.poi : POI
- poi : POI
- poi-ooxml-schemas : POI
- poi-test : POI
Full details are available at:
http://vmgump.apache.org/gump/public/poi/ooxml-schemas/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-DEBUG- Sole jar output [ooxml-schemas-[0-9]*[0-9T].jar] identifier set to
project name
-INFO- Failed with reason build timed out
-INFO- Failed to extract fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/poi/ooxml-schemas/gump_
work/build_poi_ooxml-schemas.html
Work Name: build_poi_ooxml-schemas (Type: Build)
Work ended in a state of : Failed
Elapsed: 1 hour 3 secs
Command Line: /usr/lib/jvm/java-8-oracle/bin/java -Djava.awt.headless=true
-Dbuild.sysclasspath=only -Dant.build.clonevm=true
org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml
compile-ooxml-xsds
[Working Directory: /srv/gump/public/workspace/poi]
CLASSPATH: /usr/lib/jvm/java-8-oracle/lib/tools.jar:/srv/gump/
public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/
workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/
workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/
workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/
workspace/ant/dist/lib/ant-junit4.jar:/srv/gump/public/
workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/
workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/
public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/
gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/
workspace/poi/ooxml-lib/curvesapi-1.04.jar:/srv/gump/
public/workspace/poi/ooxml-lib/xmlbeans-2.6.0.jar.orig:/
srv/gump/public/workspace/poi/compile-lib/bcpkix-jdk15on-1.
54.jar:/srv/gump/public/workspace/poi/compile-lib/
bcprov-ext-jdk15on-1.54.jar:/srv/gump/public/workspace/poi/
compile-lib/slf4j-api-1.7.12.jar
---------------------------------------------
Buildfile: /srv/gump/public/workspace/poi/build.xml
check-jars:
fetch-jars:
check-ooxml-jars:
fetch-ooxml-jars:
init:
[echo] Using Ant: Apache Ant(TM) version 1.10.0alpha compiled on
October 20 2016 from ${ant.home}, Ant detected Java 1.8 (may be different
than actual Java sometimes...)
[echo] Using Java: 1.8.0_60/1.8.0_60-b27/25.60-b23/Java HotSpot(TM)
64-Bit Server VM from Oracle Corporation on Linux: 3.13.0-66-generic
[echo] Using Findbugs: 3.0.1 for Java 1.8.0_60
check-ooxml-xsds:
fetch-ooxml-xsds:
[get] Getting: http://www.ecma-international.
org/publications/files/ECMA-ST/Office%20Open%20XML%201st%
20edition%20Part%204%20(PDF).zip
[get] To: /srv/gump/public/workspace/poi/ooxml-lib/OfficeOpenXML-
Part4.zip
[get] Getting: http://www.ecma-international.
org/publications/files/ECMA-ST/Office%20Open%20XML%201st%
20edition%20Part%202%20(PDF).zip
[get] To: /srv/gump/public/workspace/poi/ooxml-lib/OfficeOpenXML-
Part2.zip
[get] Getting: https://www.w3.org/TR/2002/REC-xmldsig-core-20020212/
xmldsig-core-schema.xsd
[get] To: /srv/gump/public/workspace/poi/ooxml-lib/xmldsig-core-
schema.xsd
[get] Getting: http://uri.etsi.org/01903/v1.3.2/XAdES.xsd
[get] To: /srv/gump/public/workspace/poi/ooxml-lib/XAdES.xsd
[get] Getting: http://uri.etsi.org/01903/v1.4.1/XAdESv141.xsd
[get] To: /srv/gump/public/workspace/poi/ooxml-lib/XAdESv141.xsd
[unzip] Expanding: /srv/gump/public/workspace/
poi/ooxml-lib/OfficeOpenXML-Part4.zip into /srv/gump/public/workspace/
poi/ooxml-lib
[unzip] Expanding: /srv/gump/public/workspace/
poi/ooxml-lib/OfficeOpenXML-Part2.zip into /srv/gump/public/workspace/
poi/ooxml-lib
[unzip] Expanding: /srv/gump/public/workspace/
poi/ooxml-lib/OfficeOpenXML-Part4.zip into /srv/gump/public/workspace/
poi/ooxml-lib
check-compiled-ooxml-xsds:
compile-ooxml-xsds:
[mkdir] Created dir: /srv/gump/public/workspace/poi/build/xmlbean-xsds
[mkdir] Created dir: /srv/gump/public/workspace/
poi/build/xmlbean-sources
[mkdir] Created dir: /srv/gump/public/workspace/
poi/build/xmlbean-classes
[copy] Copying 2 files to /srv/gump/public/workspace/
poi/build/xmlbean-xsds
[copy] Copying 87 resources to /srv/gump/public/workspace/
poi/build/xmlbean-xsds
[xmlbean] Time to build schema type system: 5.037 seconds
[xmlbean] Time to generate code: 11.171 seconds
[copy] Copying 7 files to /srv/gump/public/workspace/
poi/build/xmlbean-sources
[javac] Compiling 4575 source files to /srv/gump/public/workspace/
poi/build/xmlbean-classes
---------------------------------------------
To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/poi/ooxml-schemas/rss.xml
- Atom: http://vmgump.apache.org/gump/public/poi/ooxml-schemas/atom.xml
============================== Gump Tracking Only ===
Produced by Apache Gump(TM) version 2.3.
Gump Run 20161020000012, vmgump.apache.org:vmgump:20161020000012
Gump E-mail Identifier (unique within run) #1.
--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: Fwd: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed
Posted by Stefan Bodewig <bo...@apache.org>.
On 2016-10-23, Dominik Stadler wrote:
> Thanks for applying this quickly and fixing the missing import.
You're welcome. Most likely the import wasn't strictly necessary as
imports sometimes seem to work transitively in Python - I'm in no way a
Python developer myself.
> The run now finished after 1 hour and 9 minutes, so it seems it took
> just a bit too much time before.
Yes, I've seen it. Glad it worked.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Fwd: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed
Posted by Stefan Bodewig <bo...@apache.org>.
On 2016-10-23, Dominik Stadler wrote:
> Thanks for applying this quickly and fixing the missing import.
You're welcome. Most likely the import wasn't strictly necessary as
imports sometimes seem to work transitively in Python - I'm in no way a
Python developer myself.
> The run now finished after 1 hour and 9 minutes, so it seems it took
> just a bit too much time before.
Yes, I've seen it. Glad it worked.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: Fwd: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed
Posted by Dominik Stadler <do...@gmx.at>.
Thanks for applying this quickly and fixing the missing import. The run now
finished after 1 hour and 9 minutes, so it seems it took just a bit too
much time before.
Thanks... Dominik
On Oct 21, 2016 5:31 PM, "Stefan Bodewig" <bo...@apache.org> wrote:
> Hi Dominik
>
> On 2016-10-20, Dominik Stadler wrote:
>
> > Since some time one of the steps in the POI builds inside Gump is
> failing,
> > see below. We think it is related to the 1 hour timeout that is applied
> by
> > default.
>
> Yes, looks that way.
>
> > The step compiles a big number of files, but finishes in a few minutes
> > usually. Our builds on the Apache Jenkins instance usually take up to 40
> > minutes for the complete build which includes a number of additional
> steps,
> > so we are not sure why it is taking so long here, maybe the machine is
> > quite limited on memory/CPU?
>
> Yes, vmgump is a pretty limited. We are in the process of replacing it,
> but it may take a while until we get there.
>
> > Is there a simple way to try to increase the timeout for this specific
> > build?
>
> This is not implemented, although most of the infrastructure would be
> there.
>
> In case anybody with some working Python knowledge can spare a bit of
> time: https://svn.apache.org/repos/asf/gump/live/ holds the code.
>
> All builders create an instance of gump.util.process.Cmd and the timeout
> value could be configured via a constructor arg. For POI it would be
> enough to add an optional timeout property to
> gump.core.model.builder.Ant (likely Builder would be the better place)
> and use that from gump.core.build.Ant.getAntCommand - the builder
> instance is project.ant.
>
> I'm not sure how quick I'd be able to make the changes myself, I'm
> switching between a couple of tasks (including the new VM for gump)
> right now.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
>
Re: Fwd: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed
Posted by Dominik Stadler <do...@gmx.at>.
Thanks for applying this quickly and fixing the missing import. The run now
finished after 1 hour and 9 minutes, so it seems it took just a bit too
much time before.
Thanks... Dominik
On Oct 21, 2016 5:31 PM, "Stefan Bodewig" <bo...@apache.org> wrote:
> Hi Dominik
>
> On 2016-10-20, Dominik Stadler wrote:
>
> > Since some time one of the steps in the POI builds inside Gump is
> failing,
> > see below. We think it is related to the 1 hour timeout that is applied
> by
> > default.
>
> Yes, looks that way.
>
> > The step compiles a big number of files, but finishes in a few minutes
> > usually. Our builds on the Apache Jenkins instance usually take up to 40
> > minutes for the complete build which includes a number of additional
> steps,
> > so we are not sure why it is taking so long here, maybe the machine is
> > quite limited on memory/CPU?
>
> Yes, vmgump is a pretty limited. We are in the process of replacing it,
> but it may take a while until we get there.
>
> > Is there a simple way to try to increase the timeout for this specific
> > build?
>
> This is not implemented, although most of the infrastructure would be
> there.
>
> In case anybody with some working Python knowledge can spare a bit of
> time: https://svn.apache.org/repos/asf/gump/live/ holds the code.
>
> All builders create an instance of gump.util.process.Cmd and the timeout
> value could be configured via a constructor arg. For POI it would be
> enough to add an optional timeout property to
> gump.core.model.builder.Ant (likely Builder would be the better place)
> and use that from gump.core.build.Ant.getAntCommand - the builder
> instance is project.ant.
>
> I'm not sure how quick I'd be able to make the changes myself, I'm
> switching between a couple of tasks (including the new VM for gump)
> right now.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
>
Re: Fwd: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed
Posted by Stefan Bodewig <bo...@apache.org>.
On 2016-10-23, Stefan Bodewig wrote:
> Many thanks Dominik
> On 2016-10-22, Dominik Stadler wrote:
>> thanks for the hints, I added this locally, it seems to work when I run the
>> ooxml-schemas target. I am not a Python expert, but the changes seemed easy
>> enough, see attached diffs.
> I've applied a sligtly modified version of it (tabs to spaces) and the
> current build uses the patched version. Also I've uses a timeout of two
> hours rather than three for now.
http://vmgump.apache.org/gump/public/poi/ooxml-schemas/index.html
1 hour 9 mins 20 secs
:-)
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Fwd: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed
Posted by Stefan Bodewig <bo...@apache.org>.
Many thanks Dominik
On 2016-10-22, Dominik Stadler wrote:
> thanks for the hints, I added this locally, it seems to work when I run the
> ooxml-schemas target. I am not a Python expert, but the changes seemed easy
> enough, see attached diffs.
I've applied a sligtly modified version of it (tabs to spaces) and the
current build uses the patched version. Also I've uses a timeout of two
hours rather than three for now.
> I had to split it into two files as the metadata directory is an
> svn-external.
Every Apache committer has write access to the metadata tree. If two
hours aren't enough you should be able to extend the timeout further.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Fwd: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed
Posted by Dominik Stadler <do...@gmx.at>.
Hi Andi,
Yes, you are right, this might be. But as it did work for a long time
before, and I think even sometimes now, I thought it might just exceed the
1 hour timeout by a small margin and so I wanted to try with a longer
timeout first before going the route of more investigation into the actual
build-times here.
Dominik.
On Sat, Oct 22, 2016 at 8:00 PM, Andreas Beeker <ki...@apache.org>
wrote:
> Hi Dominik,
>
> we actually don't know which step of downloading/generating/compiling
> takes so long.
> I thought about echoing timestamps, so we can find the culprit.
> My wild guess is, that it is a memory limitation and it will simply
> garbage collect too much while compiling ...
>
> Andi
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
>
Re: Fwd: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed
Posted by Andreas Beeker <ki...@apache.org>.
Hi Dominik,
we actually don't know which step of downloading/generating/compiling takes so long.
I thought about echoing timestamps, so we can find the culprit.
My wild guess is, that it is a memory limitation and it will simply garbage collect too much while compiling ...
Andi
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: Fwd: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed
Posted by Dominik Stadler <do...@gmx.at>.
Hi,
thanks for the hints, I added this locally, it seems to work when I run the
ooxml-schemas target. I am not a Python expert, but the changes seemed easy
enough, see attached diffs.
I had to split it into two files as the metadata directory is an
svn-external.
Regards... Dominik.
On Fri, Oct 21, 2016 at 5:31 PM, Stefan Bodewig <bo...@apache.org> wrote:
> Hi Dominik
>
> On 2016-10-20, Dominik Stadler wrote:
>
> > Since some time one of the steps in the POI builds inside Gump is
> failing,
> > see below. We think it is related to the 1 hour timeout that is applied
> by
> > default.
>
> Yes, looks that way.
>
> > The step compiles a big number of files, but finishes in a few minutes
> > usually. Our builds on the Apache Jenkins instance usually take up to 40
> > minutes for the complete build which includes a number of additional
> steps,
> > so we are not sure why it is taking so long here, maybe the machine is
> > quite limited on memory/CPU?
>
> Yes, vmgump is a pretty limited. We are in the process of replacing it,
> but it may take a while until we get there.
>
> > Is there a simple way to try to increase the timeout for this specific
> > build?
>
> This is not implemented, although most of the infrastructure would be
> there.
>
> In case anybody with some working Python knowledge can spare a bit of
> time: https://svn.apache.org/repos/asf/gump/live/ holds the code.
>
> All builders create an instance of gump.util.process.Cmd and the timeout
> value could be configured via a constructor arg. For POI it would be
> enough to add an optional timeout property to
> gump.core.model.builder.Ant (likely Builder would be the better place)
> and use that from gump.core.build.Ant.getAntCommand - the builder
> instance is project.ant.
>
> I'm not sure how quick I'd be able to make the changes myself, I'm
> switching between a couple of tasks (including the new VM for gump)
> right now.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
>
Re: Fwd: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed
Posted by Dominik Stadler <do...@gmx.at>.
Hi,
thanks for the hints, I added this locally, it seems to work when I run the
ooxml-schemas target. I am not a Python expert, but the changes seemed easy
enough, see attached diffs.
I had to split it into two files as the metadata directory is an
svn-external.
Regards... Dominik.
On Fri, Oct 21, 2016 at 5:31 PM, Stefan Bodewig <bo...@apache.org> wrote:
> Hi Dominik
>
> On 2016-10-20, Dominik Stadler wrote:
>
> > Since some time one of the steps in the POI builds inside Gump is
> failing,
> > see below. We think it is related to the 1 hour timeout that is applied
> by
> > default.
>
> Yes, looks that way.
>
> > The step compiles a big number of files, but finishes in a few minutes
> > usually. Our builds on the Apache Jenkins instance usually take up to 40
> > minutes for the complete build which includes a number of additional
> steps,
> > so we are not sure why it is taking so long here, maybe the machine is
> > quite limited on memory/CPU?
>
> Yes, vmgump is a pretty limited. We are in the process of replacing it,
> but it may take a while until we get there.
>
> > Is there a simple way to try to increase the timeout for this specific
> > build?
>
> This is not implemented, although most of the infrastructure would be
> there.
>
> In case anybody with some working Python knowledge can spare a bit of
> time: https://svn.apache.org/repos/asf/gump/live/ holds the code.
>
> All builders create an instance of gump.util.process.Cmd and the timeout
> value could be configured via a constructor arg. For POI it would be
> enough to add an optional timeout property to
> gump.core.model.builder.Ant (likely Builder would be the better place)
> and use that from gump.core.build.Ant.getAntCommand - the builder
> instance is project.ant.
>
> I'm not sure how quick I'd be able to make the changes myself, I'm
> switching between a couple of tasks (including the new VM for gump)
> right now.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
>
Re: Fwd: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed
Posted by Stefan Bodewig <bo...@apache.org>.
Hi Dominik
On 2016-10-20, Dominik Stadler wrote:
> Since some time one of the steps in the POI builds inside Gump is failing,
> see below. We think it is related to the 1 hour timeout that is applied by
> default.
Yes, looks that way.
> The step compiles a big number of files, but finishes in a few minutes
> usually. Our builds on the Apache Jenkins instance usually take up to 40
> minutes for the complete build which includes a number of additional steps,
> so we are not sure why it is taking so long here, maybe the machine is
> quite limited on memory/CPU?
Yes, vmgump is a pretty limited. We are in the process of replacing it,
but it may take a while until we get there.
> Is there a simple way to try to increase the timeout for this specific
> build?
This is not implemented, although most of the infrastructure would be
there.
In case anybody with some working Python knowledge can spare a bit of
time: https://svn.apache.org/repos/asf/gump/live/ holds the code.
All builders create an instance of gump.util.process.Cmd and the timeout
value could be configured via a constructor arg. For POI it would be
enough to add an optional timeout property to
gump.core.model.builder.Ant (likely Builder would be the better place)
and use that from gump.core.build.Ant.getAntCommand - the builder
instance is project.ant.
I'm not sure how quick I'd be able to make the changes myself, I'm
switching between a couple of tasks (including the new VM for gump)
right now.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: Fwd: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed
Posted by Stefan Bodewig <bo...@apache.org>.
Hi Dominik
On 2016-10-20, Dominik Stadler wrote:
> Since some time one of the steps in the POI builds inside Gump is failing,
> see below. We think it is related to the 1 hour timeout that is applied by
> default.
Yes, looks that way.
> The step compiles a big number of files, but finishes in a few minutes
> usually. Our builds on the Apache Jenkins instance usually take up to 40
> minutes for the complete build which includes a number of additional steps,
> so we are not sure why it is taking so long here, maybe the machine is
> quite limited on memory/CPU?
Yes, vmgump is a pretty limited. We are in the process of replacing it,
but it may take a while until we get there.
> Is there a simple way to try to increase the timeout for this specific
> build?
This is not implemented, although most of the infrastructure would be
there.
In case anybody with some working Python knowledge can spare a bit of
time: https://svn.apache.org/repos/asf/gump/live/ holds the code.
All builders create an instance of gump.util.process.Cmd and the timeout
value could be configured via a constructor arg. For POI it would be
enough to add an optional timeout property to
gump.core.model.builder.Ant (likely Builder would be the better place)
and use that from gump.core.build.Ant.getAntCommand - the builder
instance is project.ant.
I'm not sure how quick I'd be able to make the changes myself, I'm
switching between a couple of tasks (including the new VM for gump)
right now.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org