Re: [GUMP@vmgump]: Project tomcat-tc7.0.x-validate (in module tomcat-7.0.x) failed
Am 14. Januar 2015 08:15:55 MEZ, schrieb Bill Barker billbar...@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 gene...@gump.apache.org. Project tomcat-tc7.0.x-validate has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-tc7.0.x-validate : Tomcat 7.x, a web server implementing Java Servlet 3.0, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-validate/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on checkstyle exists, no need to add for property checkstyle.jar. -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-validate/gump_work/build_tomcat-7.0.x_tomcat-tc7.0.x-validate.html Work Name: build_tomcat-7.0.x_tomcat-tc7.0.x-validate (Type: Build) Work ended in a state of : Failed Elapsed: 29 secs Command Line: /usr/lib/jvm/java-8-oracle/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dcheckstyle.jar=/srv/gump/public/workspace/checkstyle/target/checkstyle-6.3-SNAPSHOT.jar -Dexecute.validate=true validate [Working Directory: /srv/gump/public/workspace/tomcat-7.0.x] 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/packages/antlr/antlr-3.1.3.jar:/srv/gump/public/workspace/checkstyle/target/checkstyle-6.3-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/beanutils/dist/commons-beanutils-20150114.jar:/srv/gump/public/workspace/apache-commons/cli/target/commons-cli-1.3-SNAPSHOT.jar:/srv/gump/packages/commons-collections3/commons-collections-3.2.1.jar:/srv/gump/public/workspace/apache-commons/exec/target/commons-exec-1.3.1-SNAPSHOT.j ar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-20150114.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-20150114.jar:/srv/gump/public/workspace/apache-commons/validator/dist/commons-validator-20150114.jar:/srv/gump/packages/guava/guava-18.0.jar - Buildfile: /srv/gump/public/workspace/tomcat-7.0.x/build.xml build-prepare: [delete] Deleting directory /srv/gump/public/workspace/tomcat-7.0.x/output/build/temp [mkdir] Created dir: /srv/gump/public/workspace/tomcat-7.0.x/output/build/temp compile-prepare: download-validate: proxyflags: setproxy: testexist: [echo] Testing for /srv/gump/public/workspace/checkstyle/target/checkstyle-6.3-SNAPSHOT.jar downloadfile: validate: [mkdir] Created dir: /srv/gump/public/workspace/tomcat-7.0.x/output/res/checkstyle [checkstyle] Running Checkstyle 6.3-SNAPSHOT on 2581 files [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/test/org/apache/catalina/startup/TestTomcat.java:56: Wrong order for 'org.apache.catalina.core.StandardHost' import. Oops. I will correct it this evening, when I am home again. Regards Felix BUILD FAILED /srv/gump/public/workspace/tomcat-7.0.x/build.xml:510: Got 1 errors and 0 warnings. Total time: 29 seconds - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-validate/rss.xml - Atom: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-validate/atom.xml == Gump Tracking Only === Produced by Apache Gump(TM) version 2.3. Gump Run 20150114060004, vmgump.apache.org:vmgump:20150114060004 Gump E-mail Identifier (unique within run) #1. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [GUMP@vmgump]: Project tomcat-tc7.0.x-validate (in module tomcat-7.0.x) failed
2015-01-14 9:34 GMT+02:00 Felix Schumacher felix.schumac...@internetallee.de: Am 14. Januar 2015 08:15:55 MEZ, schrieb Bill Barker billbar...@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 gene...@gump.apache.org. Project tomcat-tc7.0.x-validate has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - tomcat-tc7.0.x-validate : Tomcat 7.x, a web server implementing Java Servlet 3.0, ... Full details are available at: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-validate/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on checkstyle exists, no need to add for property checkstyle.jar. -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-validate/gump_work/build_tomcat-7.0.x_tomcat-tc7.0.x-validate.html Work Name: build_tomcat-7.0.x_tomcat-tc7.0.x-validate (Type: Build) Work ended in a state of : Failed Elapsed: 29 secs Command Line: /usr/lib/jvm/java-8-oracle/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dcheckstyle.jar=/srv/gump/public/workspace/checkstyle/target/checkstyle-6.3-SNAPSHOT.jar -Dexecute.validate=true validate [Working Directory: /srv/gump/public/workspace/tomcat-7.0.x] 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/packages/antlr/antlr-3.1.3.jar:/srv/gump/public/workspace/checkstyle/target/checkstyle-6.3-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/beanutils/dist/commons-beanutils-20150114.jar:/srv/gump/public/workspace/apache-commons/cli/target/commons-cli-1.3-SNAPSHOT.jar:/srv/gump/packages/commons-collections3/commons-collections-3.2.1.jar:/srv/gump/public/workspace/apache-commons/exec/target/commons-exec-1.3.1-SNAPSHOT.j ar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-20150114.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-20150114.jar:/srv/gump/public/workspace/apache-commons/validator/dist/commons-validator-20150114.jar:/srv/gump/packages/guava/guava-18.0.jar - Buildfile: /srv/gump/public/workspace/tomcat-7.0.x/build.xml build-prepare: [delete] Deleting directory /srv/gump/public/workspace/tomcat-7.0.x/output/build/temp [mkdir] Created dir: /srv/gump/public/workspace/tomcat-7.0.x/output/build/temp compile-prepare: download-validate: proxyflags: setproxy: testexist: [echo] Testing for /srv/gump/public/workspace/checkstyle/target/checkstyle-6.3-SNAPSHOT.jar downloadfile: validate: [mkdir] Created dir: /srv/gump/public/workspace/tomcat-7.0.x/output/res/checkstyle [checkstyle] Running Checkstyle 6.3-SNAPSHOT on 2581 files [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/test/org/apache/catalina/startup/TestTomcat.java:56: Wrong order for 'org.apache.catalina.core.StandardHost' import. Oops. I will correct it this evening, when I am home again. I corrected it ;) Regards, Violeta Regards Felix BUILD FAILED /srv/gump/public/workspace/tomcat-7.0.x/build.xml:510: Got 1 errors and 0 warnings. Total time: 29 seconds - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-validate/rss.xml - Atom: http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-validate/atom.xml == Gump Tracking Only === Produced by Apache Gump(TM) version 2.3. Gump Run 20150114060004, vmgump.apache.org:vmgump:20150114060004 Gump E-mail Identifier (unique within run) #1. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [GUMP@vmgump]: Project tomcat-tc7.0.x-validate (in module tomcat-7.0.x) failed
On 20/08/2013 00:50, Bill Barker wrote: snip/ validate: [mkdir] Created dir: /srv/gump/public/workspace/tomcat-7.0.x/output/res/checkstyle [checkstyle] Running Checkstyle 5.7-SNAPSHOT on 2388 files [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/DefaultTestCase.java:22:1: Import from illegal package - junit.framework.TestCase. [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/TestAsyncQueue.java:24:1: Import from illegal package - junit.framework.TestCase. [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/TestSizePreservation.java:22:1: Import from illegal package - junit.framework.TestCase. BUILD FAILED /srv/gump/public/workspace/tomcat-7.0.x/build.xml:451: Got 3 errors and 0 warnings. Gump doesn't appear to be using the latest source code for this build. As far as I can tell, the project is set up so it should use the latest source from svn. What am I missing? Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [GUMP@vmgump]: Project tomcat-tc7.0.x-validate (in module tomcat-7.0.x) failed
2013/8/20 Mark Thomas ma...@apache.org: On 20/08/2013 00:50, Bill Barker wrote: snip/ validate: [mkdir] Created dir: /srv/gump/public/workspace/tomcat-7.0.x/output/res/checkstyle [checkstyle] Running Checkstyle 5.7-SNAPSHOT on 2388 files [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/DefaultTestCase.java:22:1: Import from illegal package - junit.framework.TestCase. [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/TestAsyncQueue.java:24:1: Import from illegal package - junit.framework.TestCase. [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/TestSizePreservation.java:22:1: Import from illegal package - junit.framework.TestCase. BUILD FAILED /srv/gump/public/workspace/tomcat-7.0.x/build.xml:451: Got 3 errors and 0 warnings. Gump doesn't appear to be using the latest source code for this build. As far as I can tell, the project is set up so it should use the latest source from svn. What am I missing? 1) First, model-level log http://vmgump.apache.org/gump/public/tomcat-7.0.x/index.html says *** Failed to update from source control.Stale contents *** and the following: [[[ svn: URL 'http://svn.apache.org/repos/asf/tomcat/trunk/modules/jdbc-pool' of exis... ting directory 'tomcat-7.0.x/modules/jdbc-pool' does not match expected URL 'htt... p://svn.apache.org/repos/asf/tomcat/tc7.0.x/trunk/modules/jdbc-pool' ]]] I think removing the whole directory and performing a clean svn checkout should fix this. (The modules/jdbc-pool directory was an external that pulled sources from Tomcat trunk, but nowadays it is just an ordinary subdirectory. This change happened more than a year ago. I think most of the sources in the working copy are up-to-date, but that particular directory is stale. It explains why it went unnoticed for quite some time). 2) Second, I suspect that svn update happens when a Gump run starts. That may be several hours before the actual build. I do not see any indication of what revision number was used for the build. Is it possible to remove --quiet flag from svn update command? With that flag removed it would print a) list of updated files, b) svn revision number to which the working copy was updated. http://vmgump.apache.org/gump/public/tomcat-7.0.x/gump_work/update_tomcat-7.0.x.html Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: [GUMP@vmgump]: Project tomcat-tc7.0.x-validate (in module tomcat-7.0.x) failed
On 2013-08-21, Konstantin Kolinko wrote: 2013/8/20 Mark Thomas ma...@apache.org: On 20/08/2013 00:50, Bill Barker wrote: snip/ validate: [mkdir] Created dir: /srv/gump/public/workspace/tomcat-7.0.x/output/res/checkstyle [checkstyle] Running Checkstyle 5.7-SNAPSHOT on 2388 files [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/DefaultTestCase.java:22:1: Import from illegal package - junit.framework.TestCase. [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/TestAsyncQueue.java:24:1: Import from illegal package - junit.framework.TestCase. [checkstyle] /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/TestSizePreservation.java:22:1: Import from illegal package - junit.framework.TestCase. BUILD FAILED /srv/gump/public/workspace/tomcat-7.0.x/build.xml:451: Got 3 errors and 0 warnings. Gump doesn't appear to be using the latest source code for this build. As far as I can tell, the project is set up so it should use the latest source from svn. What am I missing? 1) First, model-level log http://vmgump.apache.org/gump/public/tomcat-7.0.x/index.html says *** Failed to update from source control.Stale contents *** [...] I think removing the whole directory and performing a clean svn checkout should fix this. Oh, I missed that in the logs, directory removed, the next Gump run (at 6AM UTC) will perform a fresh checkout. 2) Second, I suspect that svn update happens when a Gump run starts. It happens just before the first project defined in the module is built. That may be several hours before the actual build. Right now the whole Gump run takes about two-and-a-half hours, I don't think this will be a big issue. I do not see any indication of what revision number was used for the build. Is it possible to remove --quiet flag from svn update command? With that flag removed it would print a) list of updated files, b) svn revision number to which the working copy was updated. http://vmgump.apache.org/gump/public/tomcat-7.0.x/gump_work/update_tomcat-7.0.x.html I just see the documentation for this is missing. The svn element (and all other SCM and builder related elements) support two attributes verbose and debug which enable more detailed output when set to true. For svn both have the same effect and just remove the --quiet. Stefan - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
