Re: Discontinue Apache POI in Gump
Done via https://svn.apache.org/viewvc?view=revision=1823548, I removed the poi.xml and removed it from gump.xml, I did not find any other occurences of "POI" in there. Thanks... Dominik. On Wed, Feb 7, 2018 at 10:09 PM, Stefan Bodewig <bode...@apache.org> wrote: > On 2018-02-07, Dominik Stadler wrote: > > > The Apache POI PMC held a vote ( > > http://mail-archives.apache.org/mod_mbox/poi-dev/201802. > mbox/%3cCABdJj56tn5hL_a+gADZD6bC4txxfUUph1aHyqhyDowMkw > +p...@mail.gmail.com%3e) > > and came to the conclusion that Gump does not provide enough value for > > us to keep putting in the effort maintaining it. > > This reminds me I wanted to reach out to the few projects that still use > Gump. Good timing. > > > Thus we would like to remove Apache POI from the Gump setup. > > > Should I just give it a try myself as everybody has commit access? > > I had a quick look and no other project depends on POI so it should be > safe to remove the project descriptor as well as the refernce to it from > the gump.xml profile. If you want to give it a try, go ahead. Please ask > if you need a hand. > > Cheers > > Stefan > > - > To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org > For additional commands, e-mail: dev-h...@poi.apache.org > >
Discontinue Apache POI in Gump
Hi Gump PMC, The Apache POI PMC held a vote ( http://mail-archives.apache.org/mod_mbox/poi-dev/201802.mbox/%3ccabdjj56tn5hl_a+gadzd6bc4txxfuuph1ahyqhydowmkw+p...@mail.gmail.com%3e) and came to the conclusion that Gump does not provide enough value for us to keep putting in the effort maintaining it. Thus we would like to remove Apache POI from the Gump setup. Should I just give it a try myself as everybody has commit access? Thanks... Dominik.
Fwd: svn commit: r1808663 - /gump/metadata/project/commons-math-3.x.xml
Hi, thanks for cleaning up after me, I tried to run it locally and it seemed to succeed, but some things around Gump are still a mystery to me, e.g. the ant/maven/pom-magic... Dominik. -- Forwarded message -- From:Date: Mon, Sep 18, 2017 at 1:54 AM Subject: svn commit: r1808663 - /gump/metadata/project/commons-math-3.x.xml To: comm...@gump.apache.org Author: billbarker Date: Sun Sep 17 23:54:22 2017 New Revision: 1808663 URL: http://svn.apache.org/viewvc?rev=1808663=rev Log: Fix MVN coodinates and build order Modified: gump/metadata/project/commons-math-3.x.xml Modified: gump/metadata/project/commons-math-3.x.xml URL: http://svn.apache.org/viewvc/gump/metadata/project/commons- math-3.x.xml?rev=1808663=1808662=1808663=diff == --- gump/metadata/project/commons-math-3.x.xml (original) +++ gump/metadata/project/commons-math-3.x.xml Sun Sep 17 23:54:22 2017 @@ -24,8 +24,8 @@ - - + + @@ -39,6 +39,7 @@ - + +
Re: Fwd: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed
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" <bode...@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-unsubscr...@poi.apache.org > For additional commands, e-mail: dev-h...@poi.apache.org > >
Re: Fwd: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed
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 <bode...@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-unsubscr...@poi.apache.org > For additional commands, e-mail: dev-h...@poi.apache.org > > Index: /opt/apache/gump-live/metadata/dtd/project.dtd === --- /opt/apache/gump-live/metadata/dtd/project.dtd (Revision 1766220) +++ /opt/apache/gump-live/metadata/dtd/project.dtd (Arbeitskopie) @@ -96,6 +96,7 @@ basedir CDATA #IMPLIED verbose CDATA #IMPLIED debug CDATA #IMPLIED + timeout CDATA #IMPLIED vmCDATA #IMPLIED > - + Index: /opt/apache/gump-live/python/gump/core/build/ant.py === --- /opt/apache/gump-live/python/gump/core/build/ant.py (Revision 1766220) +++ /opt/apache/gump-live/python/gump/core/build/ant.py (Arbeitskopie) @@ -101,6 +101,12 @@ # The ant build file (or none == build.xml) buildfile = ant.getBuildFile() +# Optional 'timeout' +if ant.hasTimeout: +timeout = ant.getTimeout() +else: +timeout = setting.TIMEOUT + # Optional 'verbose' or 'debug' verbose=ant.isVerbose() debug=ant.isDebug() @@ -119,7 +125,7 @@ # Run java on apache Ant... cmd=Cmd(javaCommand,'build_'+project.getModule().getName()+'_'+project.getName(), -basedir,{'CLASSPATH':classpath}) +basedir,{'CLASSPATH':classpath}, timeout) # These are workspace + project system properties cmd.addNamedParameters(sysproperties) Index: /opt/apache/gump-live/python/gump/core/model/builder.py === --- /opt/apache/gump-live/python/gump/core/model/builder.py (Revision 1766220) +++ /opt/apache/gump-live/python/gump/core/model/builder.py (Arbeitskopie) @@ -236,6 +236,10 @@ self.target = self.getDomAttributeValue('target') # Import the buildfile self.buildfile = self.getDomAttributeValue('buildfile') +# Import the timeout +self.timeout = self.getDomAttributeValue('timeout') +if self.timeout is not None: + self.timeout = float(self.timeout) def hasTarget(self): if self.target: @@ -253,6 +257,14 @@ def getBuildFile(self): return self.buildfile +def hasTimeout(self): +if self.timeout: +return True +return False + +def getTimeout(self): + return self.timeout + def dump(self, indent = 0, output = sys.stdout): """ Display the contents of this object """ Builder.dump(self, indent, output) @@ -261,6 +273,8 @@ output.write(i+'Target: ' + self.getTarget() + '\n')
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] :-(Date: Thu, Oct 20, 2016 at 3:48 AM Subject: [GUMP@vmgump]: Project ooxml-schemas (in module poi) failed To: d...@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
Re: svn commit: r1725406 - /gump/metadata/project/santuario.xml
Thanks for fixing! I was stumped by the error message and could not find out how to solve this. Dominik. On Tue, Jan 19, 2016 at 3:32 AM,wrote: > Author: billbarker > Date: Tue Jan 19 02:32:30 2016 > New Revision: 1725406 > > URL: http://svn.apache.org/viewvc?rev=1725406=rev > Log: > Allow it to use our jars, plus build order > > Modified: > gump/metadata/project/santuario.xml > > Modified: gump/metadata/project/santuario.xml > URL: > http://svn.apache.org/viewvc/gump/metadata/project/santuario.xml?rev=1725406=1725405=1725406=diff > > == > --- gump/metadata/project/santuario.xml (original) > +++ gump/metadata/project/santuario.xml Tue Jan 19 02:32:30 2016 > @@ -30,12 +30,15 @@ > > > > + > > > > > > > + > + > > > > > >
Re: Projects not listed in main gump.xml file?
Thanks for the explanation and historical links. Would maybe be good to state something around this on the main page to not give the impression that the project is fully active when it is in fact in kind of a maintenance mode? Thanks... Dominik. On Sat, Jan 16, 2016 at 10:54 PM, Konstantin Kolinko <knst.koli...@gmail.com > wrote: > 2016-01-16 22:48 GMT+03:00 Dominik Stadler <cen...@apache.org>: > > Hi, > > > > while looking at some failures/warnings of the gump-build, I found that > > quite a list of defined projects is not actually included in the default > > profile/gump.xml file. > > > > Is this on purpose? Some of these are defined at least as optional > > dependencies on some projects... > > > > Thanks... Dominik. > > > > > > $ for i in project/*.xml;do grep -q project/`basename $i` > profile/gump.xml > > || echo "Not found: $i"; done > > Not found: project/anakia.xml > > Not found: project/freemarker.xml > > Not found: project/httpcomponents.xml > > Not found: project/jaas.xml > > Not found: project/jena.xml > > Not found: project/jmxremote.xml > > Not found: project/jndi.xml > > Not found: project/jsse.xml > > Not found: project/junit3.xml > > Not found: project/ldap.xml > > Not found: project/mockito.xml > > Not found: project/packaged-bcel.xml > > Not found: project/rhino.xml > > Not found: project/velocity-anakia.xml > > Not found: project/velocity-dvsl.xml > > Not found: project/velocity-engine2.xml > > Not found: project/velocity-engine.xml > > Not found: project/velocity-maven.xml > > Not found: project/velocity-texen.xml > > Not found: project/velocity-tools.xml > > Not found: project/xml-xmlbeans.xml > > See svn history of profile/gump.xml > E.g. anakia was removed in this commit: > http://svn.apache.org/viewvc?view=revision=1512820 > of 2013-08-10 > > My guess is that somebody forgot to remove project/anakia.xml (among > ~170 files removed in that commit) for some trivial reason, being > confused by something. > > (Theoretically one may say that you also need to search other > profiles, though only profile/gump.xml is used by the current running > instance.) > > July-August 2013 was when Stefan reached out to other projects asking > whether they find Gump useful and removed a number of unneeded > projects. See the archives. > > > http://mail-archives.apache.org/mod_mbox/gump-general/201307.mbox/%3C87a9lg77tm.fsf%40v35516.1blu.de%3E > > > http://mail-archives.apache.org/mod_mbox/gump-general/201308.mbox/%3C87fvuh9yq9.fsf%40v35516.1blu.de%3E > > Best regards, > Konstantin Kolinko > > - > To unsubscribe, e-mail: general-unsubscr...@gump.apache.org > For additional commands, e-mail: general-h...@gump.apache.org > >
Projects not listed in main gump.xml file?
Hi, while looking at some failures/warnings of the gump-build, I found that quite a list of defined projects is not actually included in the default profile/gump.xml file. Is this on purpose? Some of these are defined at least as optional dependencies on some projects... Thanks... Dominik. $ for i in project/*.xml;do grep -q project/`basename $i` profile/gump.xml || echo "Not found: $i"; done Not found: project/anakia.xml Not found: project/freemarker.xml Not found: project/httpcomponents.xml Not found: project/jaas.xml Not found: project/jena.xml Not found: project/jmxremote.xml Not found: project/jndi.xml Not found: project/jsse.xml Not found: project/junit3.xml Not found: project/ldap.xml Not found: project/mockito.xml Not found: project/packaged-bcel.xml Not found: project/rhino.xml Not found: project/velocity-anakia.xml Not found: project/velocity-dvsl.xml Not found: project/velocity-engine2.xml Not found: project/velocity-engine.xml Not found: project/velocity-maven.xml Not found: project/velocity-texen.xml Not found: project/velocity-tools.xml Not found: project/xml-xmlbeans.xml