BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 3 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Project jaxen-from-packaged-dom4j (in module jaxen) failed [EMAIL PROTECTED]: Project myfaces (in module myfaces) failed [EMAIL PROTECTED]: Project xml-security-tests (in module xml-security) failed *** G U M P [EMAIL PROTECTED]: Project jaxen-from-packaged-dom4j (in module jaxen) failed 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 [EMAIL PROTECTED] Project jaxen-from-packaged-dom4j has an issue affecting its community integration. This issue affects 130 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - ant-xdocs-proposal : Java based build tool - apollo : Apollo Project - apollo-jndi-config : Apollo Project - authx-example : Apache Authentication and Authorization Framework - authx-script : Apache Authentication and Authorization Framework - cocoon : Java XML Framework - cocoon-block-asciiart : Java XML Framework - cocoon-block-authentication-fw : Java XML Framework - cocoon-block-axis : Java XML Framework - cocoon-block-batik : Java XML Framework - cocoon-block-bsf : Java XML Framework - cocoon-block-chaperon : Java XML Framework - cocoon-block-cron : Java XML Framework - cocoon-block-databases : Java XML Framework - cocoon-block-deli : Java XML Framework - cocoon-block-eventcache : Java XML Framework - cocoon-block-fop : Java XML Framework - cocoon-block-hsqldb : Java XML Framework - cocoon-block-html : Java XML Framework - cocoon-block-itext : Java XML Framework - cocoon-block-javaflow : Java XML Framework - cocoon-block-jfor : Java XML Framework - cocoon-block-jms : Java XML Framework - cocoon-block-jsp : Java XML Framework - cocoon-block-linkrewriter : Java XML Framework - cocoon-block-lucene : Java XML Framework - cocoon-block-midi : Java XML Framework - cocoon-block-naming : Java XML Framework - cocoon-block-paranoid : Java XML Framework - cocoon-block-poi : Java XML Framework - cocoon-block-profiler : Java XML Framework - cocoon-block-proxy : Java XML Framework - cocoon-block-python : Java XML Framework - cocoon-block-qdox : Java XML Framework - cocoon-block-repository : Java XML Framework - cocoon-block-serializers : Java XML Framework - cocoon-block-session-fw : Java XML Framework - cocoon-block-slide : Java XML Framework - cocoon-block-slop : Java XML Framework - cocoon-block-stx : Java XML Framework - cocoon-block-taglib : Java XML Framework - cocoon-block-template : Java XML Framework - cocoon-block-velocity : Java XML Framework - cocoon-block-web3 : Java XML Framework - cocoon-block-webdav : Java XML Framework - cocoon-block-xmldb : Java XML Framework - cocoon-block-xsp : Java XML Framework - commons-feedparser : Generic FeedParser interface and concrete implementation... - commons-jelly : Commons Jelly - commons-jelly-tags-ant : Commons Jelly - commons-jelly-tags-antlr : Commons Jelly - commons-jelly-tags-avalon : Commons Jelly - commons-jelly-tags-bean : Commons Jelly - commons-jelly-tags-beanshell : Commons Jelly - commons-jelly-tags-betwixt : Commons Jelly - commons-jelly-tags-bsf : Commons Jelly - commons-jelly-tags-define : Commons Jelly - commons-jelly-tags-dynabean : Commons Jelly - commons-jelly-tags-email : Commons Jelly - commons-jelly-tags-fmt : Commons Jelly - commons-jelly-tags-html : Commons Jelly - commons-jelly-tags-http : Commons Jelly - commons-jelly-tags-interaction : Commons Jelly - commons-jelly-tags-jaxme : Commons Jelly - commons-jelly-tags-jetty : Commons Jelly - commons-jelly-tags-jface : Commons Jelly - commons-jelly-tags-jms : Commons Jelly - commons-jelly-tags-jmx : Commons Jelly - commons-jelly-tags-jsl : Commons Jelly - commons-jelly-tags-junit : Commons Jelly - commons-jelly-tags-log : Commons Jelly - commons-jelly-tags-memory : Commons Jelly - commons-jelly-tags-ojb : Commons Jelly - commons-jelly-tags-quartz : Commons Jelly - commons-jelly-tags-regexp : Commons Jelly - commons-jelly-tags-soap : Commons Jelly - commons-jelly-tags-sql : Commons Jelly - commons-jelly-tags-swing : Commons Jelly - commons-jelly-tags-swt : Commons Jelly - commons-jelly-tags-threads : Commons Jelly - commons-jelly-tags-util : Commons Jelly - commons-jelly-tags-validate : Commons Jelly - commons-jelly-tags-vel
BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 3 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Project jaxen-from-packaged-dom4j (in module jaxen) failed [EMAIL PROTECTED]: Project myfaces (in module myfaces) failed [EMAIL PROTECTED]: Project xml-security-tests (in module xml-security) failed *** G U M P [EMAIL PROTECTED]: Project jaxen-from-packaged-dom4j (in module jaxen) failed 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 [EMAIL PROTECTED] Project jaxen-from-packaged-dom4j has an issue affecting its community integration. This issue affects 130 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - ant-xdocs-proposal : Java based build tool - apollo : Apollo Project - apollo-jndi-config : Apollo Project - authx-example : Apache Authentication and Authorization Framework - authx-script : Apache Authentication and Authorization Framework - cocoon : Java XML Framework - cocoon-block-asciiart : Java XML Framework - cocoon-block-authentication-fw : Java XML Framework - cocoon-block-axis : Java XML Framework - cocoon-block-batik : Java XML Framework - cocoon-block-bsf : Java XML Framework - cocoon-block-chaperon : Java XML Framework - cocoon-block-cron : Java XML Framework - cocoon-block-databases : Java XML Framework - cocoon-block-deli : Java XML Framework - cocoon-block-eventcache : Java XML Framework - cocoon-block-fop : Java XML Framework - cocoon-block-hsqldb : Java XML Framework - cocoon-block-html : Java XML Framework - cocoon-block-itext : Java XML Framework - cocoon-block-javaflow : Java XML Framework - cocoon-block-jfor : Java XML Framework - cocoon-block-jms : Java XML Framework - cocoon-block-jsp : Java XML Framework - cocoon-block-linkrewriter : Java XML Framework - cocoon-block-lucene : Java XML Framework - cocoon-block-midi : Java XML Framework - cocoon-block-naming : Java XML Framework - cocoon-block-paranoid : Java XML Framework - cocoon-block-poi : Java XML Framework - cocoon-block-profiler : Java XML Framework - cocoon-block-proxy : Java XML Framework - cocoon-block-python : Java XML Framework - cocoon-block-qdox : Java XML Framework - cocoon-block-repository : Java XML Framework - cocoon-block-serializers : Java XML Framework - cocoon-block-session-fw : Java XML Framework - cocoon-block-slide : Java XML Framework - cocoon-block-slop : Java XML Framework - cocoon-block-stx : Java XML Framework - cocoon-block-taglib : Java XML Framework - cocoon-block-template : Java XML Framework - cocoon-block-velocity : Java XML Framework - cocoon-block-web3 : Java XML Framework - cocoon-block-webdav : Java XML Framework - cocoon-block-xmldb : Java XML Framework - cocoon-block-xsp : Java XML Framework - commons-feedparser : Generic FeedParser interface and concrete implementation... - commons-jelly : Commons Jelly - commons-jelly-tags-ant : Commons Jelly - commons-jelly-tags-antlr : Commons Jelly - commons-jelly-tags-avalon : Commons Jelly - commons-jelly-tags-bean : Commons Jelly - commons-jelly-tags-beanshell : Commons Jelly - commons-jelly-tags-betwixt : Commons Jelly - commons-jelly-tags-bsf : Commons Jelly - commons-jelly-tags-define : Commons Jelly - commons-jelly-tags-dynabean : Commons Jelly - commons-jelly-tags-email : Commons Jelly - commons-jelly-tags-fmt : Commons Jelly - commons-jelly-tags-html : Commons Jelly - commons-jelly-tags-http : Commons Jelly - commons-jelly-tags-interaction : Commons Jelly - commons-jelly-tags-jaxme : Commons Jelly - commons-jelly-tags-jetty : Commons Jelly - commons-jelly-tags-jface : Commons Jelly - commons-jelly-tags-jms : Commons Jelly - commons-jelly-tags-jmx : Commons Jelly - commons-jelly-tags-jsl : Commons Jelly - commons-jelly-tags-junit : Commons Jelly - commons-jelly-tags-log : Commons Jelly - commons-jelly-tags-memory : Commons Jelly - commons-jelly-tags-ojb : Commons Jelly - commons-jelly-tags-quartz : Commons Jelly - commons-jelly-tags-regexp : Commons Jelly - commons-jelly-tags-soap : Commons Jelly - commons-jelly-tags-sql : Commons Jelly - commons-jelly-tags-swing : Commons Jelly - commons-jelly-tags-swt : Commons Jelly - commons-jelly-tags-threads : Commons Jelly - commons-jelly-tags-util : Commons Jelly - commons-jelly-tags-validate : Commons Jelly - commons-jelly-tags-vel
Re: [GUMP@brutus]: Project lucene-java (in module lucene-java) failed
On Tue, 10 May 2005, Erik Hatcher <[EMAIL PROTECTED]> wrote: > I can (and probably will) change it such that is not run if > JavaCC is not present and adjust it so that the check for JavaCC is > only done on the targets that truly need it (but are not part of the > main build path). This may be tricky, given the way the task works. The task checks whether it finds javacc.jar or JavaCC.zip in a specific location relative to the javacchome attribute. In Gump you can't trust this alone since Gump will make Ant ignore the internal classpath of the task. Given that there really is a lot of convulted logic involved because the task supports four different versions with three different classnames and three different archive locations (and no, there is no one to one mapping of classname to archive location), you are probably best of creating a condition yourself. The logic would be something like Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: Project lucene-java (in module lucene-java) failed
On May 9, 2005, at 9:34 AM, Stefan Bodewig wrote: On Mon, 9 May 2005, Erik Hatcher <[EMAIL PROTECTED]> wrote: On May 9, 2005, at 3:57 AM, Stefan Bodewig wrote: Feel free to add any "new" dependencies Gump is missing. What's the process for me to add new dependencies? If the project you depend on is already known to Gump: * check out gump/projects/lucene-java.xml from CVS. * modify it (by adding a tag, you will understand how when you look into the descriptor). * commit it - yes, you can, every ASF committer can. If it a "new" project, i.e. something Gump doesn't build yet, you can either read about Gump descriptors on our homepage or come to [EMAIL PROTECTED] and ask for help. Stefan - thanks! I have, as you probably have seen, just committed a cosmetic change to the lucene-java.xml file while troubleshooting the latest failure caused by the missing JavaCC and saw that you had already taken care of it. JavaCC is not strictly required to build Lucene, as we commit the generated files, but in my refactorings I made it necessary, not necessarily intentionally. I can (and probably will) change it such that is not run if JavaCC is not present and adjust it so that the check for JavaCC is only done on the targets that truly need it (but are not part of the main build path). I'm now attentively tuned in to the Lucene Gump failures, and will jump in to help if needed. Hopefully the JavaCC adjustment you made is all that is needed to make Gump happy. Erik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 9 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Module icu4j failed [EMAIL PROTECTED]: Module xdoclet success, but with warnings. [EMAIL PROTECTED]: Project nant (in module nant) failed [EMAIL PROTECTED]: Project txt2html-task (in module jakarta-servletapi-5) success, but with warnings. [EMAIL PROTECTED]: Project icu4j (in module icu4j) failed [EMAIL PROTECTED]: Project jaxen-from-packaged-dom4j (in module jaxen) failed [EMAIL PROTECTED]: Project commons-jci (in module jakarta-commons-sandbox) failed [EMAIL PROTECTED]: Project myfaces (in module myfaces) failed [EMAIL PROTECTED]: Project xml-security-tests (in module xml-security) failed *** G U M P [EMAIL PROTECTED]: Module icu4j failed 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 [EMAIL PROTECTED] Module icu4j has an issue affecting its community integration, and has been outstanding for 61 runs. The current state of this module is 'Failed', with reason 'Update Failed'. Full details are available at: http://brutus.apache.org/gump/public/icu4j/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason update failed The following work was performed: http://brutus.apache.org/gump/public/icu4j/gump_work/update_icu4j.html Work Name: update_icu4j (Type: Update) Work ended in a state of : Failed Elapsed: 1 sec Command Line: cvs -q -z3 -d :ext:[EMAIL PROTECTED]:/icu checkout -P -d icu4j icu4j [Working Directory: /usr/local/gump/public/workspace/cvs] - IBM CANADA Ltd. CHS Server D25HTTP004 racky2u15 ** WARNING Access Restricted ** Permission denied (publickey,keyboard-interactive). cvs [checkout aborted]: end of file from server (consult above messages if any) - To subscribe to this information via syndicated feeds: - RSS: http://brutus.apache.org/gump/public/icu4j/rss.xml - Atom: http://brutus.apache.org/gump/public/icu4j/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2310052005, brutus:brutus-public:2310052005 Gump E-mail Identifier (unique within run) #1. *** G U M P [EMAIL PROTECTED]: Module xdoclet success, but with warnings. 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 [EMAIL PROTECTED] Module xdoclet contains errors. The current state of this module is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/xdoclet/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -ERROR- *** Failed to update from source control. Stale contents *** The following work was performed: http://brutus.apache.org/gump/public/xdoclet/gump_work/update_xdoclet.html Work Name: update_xdoclet (Type: Update) Work ended in a state of : Failed Elapsed: 3 mins 28 secs Command Line: cvs -q -z3 -d :pserver:[EMAIL PROTECTED]:/cvsroot/xdoclet update -P -d -A [Working Directory: /usr/local/gump/public/workspace/cvs/xdoclet] - cvs [update aborted]: writing to server: Broken pipe - To subscribe to this information via syndicated feeds: - RSS: http://brutus.apache.org/gump/public/xdoclet/rss.xml - Atom: http://brutus.apache.org/gump/public/xdoclet/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2310052005, brutus:brutus-public:2310052005 Gump E-mail Identifier (unique within run) #2. *** G U M P [EMAIL PROTECTED]: Project nant (in module nant) failed 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 [EMAIL PROTECTED] Project nant has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 228 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - nant : NAnt is a free .NET build tool. In theory it is kind of like... Full details are available at: http://brutus.apache.org/gump/public/nant/nant/index.html That said, some information snippets are provided here. The
BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 9 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Module icu4j failed [EMAIL PROTECTED]: Module xdoclet success, but with warnings. [EMAIL PROTECTED]: Project nant (in module nant) failed [EMAIL PROTECTED]: Project txt2html-task (in module jakarta-servletapi-5) success, but with warnings. [EMAIL PROTECTED]: Project icu4j (in module icu4j) failed [EMAIL PROTECTED]: Project jaxen-from-packaged-dom4j (in module jaxen) failed [EMAIL PROTECTED]: Project commons-jci (in module jakarta-commons-sandbox) failed [EMAIL PROTECTED]: Project myfaces (in module myfaces) failed [EMAIL PROTECTED]: Project xml-security-tests (in module xml-security) failed *** G U M P [EMAIL PROTECTED]: Module icu4j failed 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 [EMAIL PROTECTED] Module icu4j has an issue affecting its community integration, and has been outstanding for 61 runs. The current state of this module is 'Failed', with reason 'Update Failed'. Full details are available at: http://brutus.apache.org/gump/public/icu4j/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason update failed The following work was performed: http://brutus.apache.org/gump/public/icu4j/gump_work/update_icu4j.html Work Name: update_icu4j (Type: Update) Work ended in a state of : Failed Elapsed: 1 sec Command Line: cvs -q -z3 -d :ext:[EMAIL PROTECTED]:/icu checkout -P -d icu4j icu4j [Working Directory: /usr/local/gump/public/workspace/cvs] - IBM CANADA Ltd. CHS Server D25HTTP004 racky2u15 ** WARNING Access Restricted ** Permission denied (publickey,keyboard-interactive). cvs [checkout aborted]: end of file from server (consult above messages if any) - To subscribe to this information via syndicated feeds: - RSS: http://brutus.apache.org/gump/public/icu4j/rss.xml - Atom: http://brutus.apache.org/gump/public/icu4j/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2310052005, brutus:brutus-public:2310052005 Gump E-mail Identifier (unique within run) #1. *** G U M P [EMAIL PROTECTED]: Module xdoclet success, but with warnings. 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 [EMAIL PROTECTED] Module xdoclet contains errors. The current state of this module is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/xdoclet/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -ERROR- *** Failed to update from source control. Stale contents *** The following work was performed: http://brutus.apache.org/gump/public/xdoclet/gump_work/update_xdoclet.html Work Name: update_xdoclet (Type: Update) Work ended in a state of : Failed Elapsed: 3 mins 28 secs Command Line: cvs -q -z3 -d :pserver:[EMAIL PROTECTED]:/cvsroot/xdoclet update -P -d -A [Working Directory: /usr/local/gump/public/workspace/cvs/xdoclet] - cvs [update aborted]: writing to server: Broken pipe - To subscribe to this information via syndicated feeds: - RSS: http://brutus.apache.org/gump/public/xdoclet/rss.xml - Atom: http://brutus.apache.org/gump/public/xdoclet/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2310052005, brutus:brutus-public:2310052005 Gump E-mail Identifier (unique within run) #2. *** G U M P [EMAIL PROTECTED]: Project nant (in module nant) failed 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 [EMAIL PROTECTED] Project nant has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 228 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - nant : NAnt is a free .NET build tool. In theory it is kind of like... Full details are available at: http://brutus.apache.org/gump/public/nant/nant/index.html That said, some information snippets are provided here. The
Re: Effects of failing Gump runs
On 10-05-2005 10:32, "Stefan Bodewig" <[EMAIL PROTECTED]> wrote: > last week we had failing JDK 1.5, Kaffe and test builds for different > reasons, yesterday the non-official public build failed. I haven't > investigated why they failed so far, since I've been fighting the > side-effects. I have tried to figure it out in several cases. Failure so far. A lot of our errors are "transient". Perhaps we could have a try/finally in the right location to remove lock files. Adam, any pointers? Cheers, Leo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Effects of failing Gump runs
Hi, last week we had failing JDK 1.5, Kaffe and test builds for different reasons, yesterday the non-official public build failed. I haven't investigated why they failed so far, since I've been fighting the side-effects. If Gump fails it will now (1) Not remove the lock files in the .../workspace/cvs or .../staging directories if there are any. (2) Keep some integrate.py process hanging around. (3) May even leave .../gump/gump.lock in place. (1) leads to new processes of new Gump runs hanging forever and probably happens if either an update or sync process was active when Gump failed. It is possible that (2) doesn't happen all the time, but there've been about twenty processes from yesterday when I logged in to Brutus to see why the official run didn't seem to be active. (3) happenend last week, it did not happen yesterday for the public run. I manually removed the locks yesterday. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
