BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 7 notifys should have been sent *** G U M P [GUMP@vmgump]: Project taglibs-standard-spec (in module tomcat-taglibs) failed [GUMP@vmgump]: Project apacheds-server-tools (in module apacheds) failed [GUMP@vmgump]: Project syncrepl (in module apacheds) failed [GUMP@vmgump]: Project apacheds-service (in module apacheds) failed [GUMP@vmgump]: Project apacheds-all (in module apacheds) failed [GUMP@vmgump]: Project apacheds-kerberos-test (in module apacheds) failed [GUMP@vmgump]: Project apacheds-ldap-client-test (in module apacheds) failed *** G U M P [GUMP@vmgump]: Project taglibs-standard-spec (in module tomcat-taglibs) 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 general@gump.apache.org. Project taglibs-standard-spec has an issue affecting its community integration. This issue affects 37 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-id : Commons Identifier Package - commons-jelly : Commons Jelly - commons-jelly-tags-ant : Commons Jelly - commons-jelly-tags-ant-test : 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-define-test : Commons Jelly - commons-jelly-tags-dynabean : Commons Jelly - commons-jelly-tags-email : Commons Jelly - commons-jelly-tags-fmt : Commons Jelly - commons-jelly-tags-fmt-test : Commons Jelly - commons-jelly-tags-html : Commons Jelly - commons-jelly-tags-http : Commons Jelly - commons-jelly-tags-interaction : Commons Jelly - commons-jelly-tags-jface : Commons Jelly - commons-jelly-tags-jms : Commons Jelly - commons-jelly-tags-jsl : Commons Jelly - commons-jelly-tags-jsl-test : Commons Jelly - commons-jelly-tags-junit : Commons Jelly - commons-jelly-tags-log : Commons Jelly - commons-jelly-tags-memory : Commons Jelly - commons-jelly-tags-regexp : 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-velocity : Commons Jelly - commons-jelly-tags-xml : Commons Jelly - commons-jelly-tags-xmlunit : Commons Jelly - commons-jelly-test : Commons Jelly - taglibs-standard-spec : JSP Taglibs Full details are available at: http://vmgump.apache.org/gump/public/tomcat-taglibs/taglibs-standard-spec/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole jar output [taglibs-standard-spec-1.2-SNAPSHOT.jar] identifier set to project name -DEBUG- (Apache Gump generated) Apache Maven Settings in: /srv/gump/public/workspace/tomcat-taglibs/standard/spec/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/tomcat-taglibs/standard/spec/pom.xml -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/tomcat-taglibs/taglibs-standard-spec/gump_work/build_tomcat-taglibs_taglibs-standard-spec.html Work Name: build_tomcat-taglibs_taglibs-standard-spec (Type: Build) Work ended in a state of : Failed Elapsed: 1 sec Command Line: /opt/maven2/bin/mvn --batch-mode --settings /srv/gump/public/workspace/tomcat-taglibs/standard/spec/gump_mvn_settings.xml install [Working Directory: /srv/gump/public/workspace/tomcat-taglibs/standard/spec] M2_HOME: /opt/maven2 - 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:616) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find
Re: Modules using Git cannot update themselves on vmgump
I've been fighting this from time to time with little success (the URL speficied *is* the default configured remote). It might be a good idea to allow users to configure a branch other than master, so I'm going to add a branch attribute which defaults to master and add this to the command line. This seems to work on vmgump as well as the FreeBSD jail. This may take a few days. This is partly done by now, at least the working copies on vmgump can now be updated as well. The code needs an additional tweak so a working copy validates it is on the correct branch, I hope to add it later this week. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
[jira] [Resolved] (GUMP-155) Gump complains that the HiveMind build failed, when it does not
[ https://issues.apache.org/jira/browse/GUMP-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig resolved GUMP-155. - Resolution: Invalid Gump complains that the HiveMind build failed, when it does not --- Key: GUMP-155 URL: https://issues.apache.org/jira/browse/GUMP-155 Project: Gump Issue Type: Bug Reporter: Howard M. Lewis Ship I get emails from Gump all the time that claim there's an error, but there's no indication of what the error is (notice that all the tests passed): 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 jakarta-hivemind has an issue affecting its community integration. This issue affects 3 projects, and has been outstanding for 61 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - jakarta-hivemind : HiveMind is a services and configuration microkernel - jakarta-hivemind-library : HiveMind is a services and configuration microkernel - jakarta-tapestry : Component-based web application framework organized around i... Full details are available at: http://vmgump.apache.org/gump/public/jakarta-hivemind/jakarta-hivemind/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [hivemind-28092005.jar] identifier set to project name -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-hivemind/jakarta-hivemind/gump_work/build_jakarta-hivemind_jakarta-hivemind.html Work Name: build_jakarta-hivemind_jakarta-hivemind (Type: Build) Work ended in a state of : Failed Elapsed: 42 secs Command Line: java -Djava.awt.headless=true -Dant.build.clonevm=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Djava.classes.dir=target/classes -Djunit-available=true -Djavacc.home=/usr/local/gump/packages/javacc-3.1 -Ddownload-warning-marker-displayed=true -Dtest.classes.dir=target/test-classes -Dproject.version=28092005 [Working Directory: /usr/local/gump/public/workspace/jakarta-hivemind/framework] CLASSPATH:
[jira] [Resolved] (GUMP-147) Complain if a project does not provide all the outputs it states
[ https://issues.apache.org/jira/browse/GUMP-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig resolved GUMP-147. - Resolution: Fixed Fix Version/s: (was: Gump3-alpha-7) Complain if a project does not provide all the outputs it states Key: GUMP-147 URL: https://issues.apache.org/jira/browse/GUMP-147 Project: Gump Issue Type: New Feature Components: Python-based Gump Affects Versions: Gump3-alpha-7 Reporter: Leo Simons We should have a post-processing plugin (maybe one-per-output-type) that looks for successfully built projects, then goes and peeks if each and every of the outputs it specifies now actually exists (probably os.exists() and sometimes os.isfile() and os.isdir() if appropriate). If not, the plugin should mark the failure on the output. The logreporter should be modified to include this information with each project (this is probably a METADATA FAILURE), eg loop over all outputs for all projects and check_failure on each of them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
