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: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
