gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Re: [GUMP@vmgump]: Project tomcat-tc7.0.x-validate (in module tomcat-7.0.x) failed
Date Wed, 21 Aug 2013 04:39:46 GMT
On 2013-08-21, Konstantin Kolinko wrote:

> 2013/8/20 Mark Thomas <>:
>> 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/
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/
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/
Import from illegal package - junit.framework.TestCase.

>>> /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

> 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.


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.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message