You are viewing a plain text version of this content. The canonical link for it is here.

Posted to general@gump.apache.org by Vincent Massol <vm...@pivolis.com> on 2004/03/11 09:42:42 UTC

How to debug a Gump build problem? (was FW: [GUMP@lsd]: jakarta-cactus/jakarta-cactus-sample-servlet-12 failed)

Hi,

Below is a Gump build failure that has been going on for too long... I'd
like to solve it. However, I can't reproduce the test error it gives.
Everything runs fine here. Thus I think it can be caused either by a
different configuration or by the fact that it runs on a different OS.

My question is: What are the facilities given to projects to debug Gump
builds? 

More specifically: Do we have a shell account with read access to the
directory where Gump built the project?

Also, is there a ASP-like GUMP installation on an ASF machine where we
could have a shell account and execute Gump build on demand. Say for
example that I notice a problem. I need to turn debug on. I'd like to be
able to rerun Gump on that project immediately and not wait for the next
day. OTOH I do not want to have to install Gump on my machine as it is
quite difficult...

Thanks
-Vincent

> -----Original Message-----
> From: Vincent Massol [mailto:vmassol@apache.org]
> Sent: 11 March 2004 06:04
> To: cactus-dev@jakarta.apache.org
> Subject: [GUMP@lsd]: jakarta-cactus/jakarta-cactus-sample-servlet-12
> failed
> 
> To whom it may engage...
> 
> This is an automated request, but not an unsolicited one. For help
> understanding the request please visit
> http://gump.apache.org/nagged.html,
> and/or contact general@gump.apache.org.
> 
> Project jakarta-cactus-sample-servlet-12 has an issue affecting it's
> community integration, and has been outstanding for 8 runs. The
current
> state is 'Failed', for reason 'Build Failed'
> 
> Full details are available at:
http://lsd.student.utwente.nl/gump/jakarta-
> cactus/jakarta-cactus-sample-servlet-12.html, however some snippets
> follow:
> 
> -  -  -  -  - -- -- ------------------------------------ G U M P
> 
> Gump provided these annotations:
> 
>  - Info - Sole jar [/data3/gump/jakarta-cactus/samples/servlet/dist-
> 12/bin] identifier set to project name
>  - Info - Dependency on aspectj exists, no need to add for property
> aspectjrt.jar.
>  - Info - Dependency on jakarta-cactus-integration-ant-12 exists, no
need
> to add for property cactus.ant.jar.
>  - Info - Dependency on jakarta-tomcat exists, no need to add for
property
> cactus.home.tomcat3x.
>  - Info - Made directory [/data3/gump/jakarta-
> cactus/samples/servlet/target-12/test/classes/java]
>  - Info - Made directory [/data3/gump/jakarta-
> cactus/samples/servlet/target-12/test/classes/cactus]
>  - Error - Failed with reason build failed
> 
> 
> -  -  -  -  - -- -- ------------------------------------ G U M P
> Gump performed this work:
> 
> Work Name: build_jakarta-cactus_jakarta-cactus-sample-servlet-12
(Type:
> Build)
> State: Failed
> Elapsed: 0 hours, 0 minutes, 28 seconds
> Command Line: java -Djava.awt.headless=true -Dbuild.clonevm=true -
> Xbootclasspath/p:/data3/gump/xml-
> xerces2/java/build/xercesImpl.jar:/data3/gump/xml-
> xerces2/java/build/xmlParserAPIs.jar org.apache.tools.ant.Main -debug
-
> Dgump.merge=/data3/gump/gump-install/work/merge.xml -
> Dbuild.sysclasspath=only -Dlog4j.jar=/data3/gump/logging-log4j/log4j-
> 20040311.jar -Djunit.jar=/data3/gump/dist/junit/junit.jar -
> Dhttpunit.jar=/data3/gump/httpunit/lib/httpunit.jar -
> Dcommons.logging.jar=/data3/gump/jakarta-commons/logging/dist/commons-
> logging.jar -Dnekohtml.jar=/data3/gump/opt/nekohtml-0.9.1/nekohtml.jar
-
> Dcommons.httpclient.jar=/data3/gump/jakarta-
> commons/httpclient/dist/commons-httpclient.jar -Dcactus.port=8082 -
> Dcactus.home.tomcat3x=/data3/gump/jakarta-tomcat/build/tomcat -
> Dcactus.ant.jar=/data3/gump/jakarta-cactus/integration/ant/dist-
> 12/lib/cactus-ant-20040311.jar -Dservlet.jar=/data3/gump/jakarta-
> servletapi/dist/lib/servlet.jar -Dproject.version=20040311 -
> Daspectjrt.jar=/data3/gump/opt/aspectj1.1/lib/aspectjrt.jar -
> Dcactus.jar=/data3/gump/jakarta-cactus/framework/dist-12/lib/cactus-
> 20040311.jar -f samples/servlet/build.xml dist
> [Working Directory: /data3/gump/jakarta-cactus]
> ---------------------------------------------
> 
> BUILD FAILED
> /data3/gump/jakarta-cactus/samples/servlet/build.xml:330: The
following
> error occurred while executing this line:
>
/data3/gump/jakarta-cactus/samples/servlet/target-12/sample/build.xml:32
0:
> Test org.apache.cactus.sample.servlet.unit.TestBasicAuthentication
failed
> 	at
>
org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHe
lp
> er.java:536)
> 	at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:383)
> 	at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:268)
> 	at org.apache.tools.ant.Task.perform(Task.java:363)
> 	at org.apache.tools.ant.Target.execute(Target.java:300)
> 	at org.apache.tools.ant.Target.performTasks(Target.java:327)
> 	at org.apache.tools.ant.Project.executeTarget(Project.java:1213)
> 	at
org.apache.tools.ant.Project.executeTargets(Project.java:1061)
> 	at org.apache.tools.ant.Main.runBuild(Main.java:667)
> 	at org.apache.tools.ant.Main.startAnt(Main.java:187)
> 	at org.apache.tools.ant.Main.start(Main.java:151)
> 	at org.apache.tools.ant.Main.main(Main.java:234)
> Caused by: /data3/gump/jakarta-cactus/samples/servlet/target-
> 12/sample/build.xml:320: Test
> org.apache.cactus.sample.servlet.unit.TestBasicAuthentication failed
> 	at
>
org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask
.j
> ava:651)
> 	at
>
org.apache.cactus.integration.ant.CactusTask.executeInContainer(CactusTa
sk
> .java:449)
> 	at
>
org.apache.cactus.integration.ant.CactusTask.execute(CactusTask.java:213
)
> 	at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:268)
> 	at org.apache.tools.ant.Task.perform(Task.java:363)
> 	at org.apache.tools.ant.Target.execute(Target.java:300)
> 	at org.apache.tools.ant.Target.performTasks(Target.java:327)
> 	at org.apache.tools.ant.Project.executeTarget(Project.java:1213)
> 	at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:381)
> 	... 10 more
> --- Nested Exception ---
>
/data3/gump/jakarta-cactus/samples/servlet/target-12/sample/build.xml:32
0:
> Test org.apache.cactus.sample.servlet.unit.TestBasicAuthentication
failed
> 	at
>
org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask
.j
> ava:651)
> 	at
>
org.apache.cactus.integration.ant.CactusTask.executeInContainer(CactusTa
sk
> .java:449)
> 	at
>
org.apache.cactus.integration.ant.CactusTask.execute(CactusTask.java:213
)
> 	at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:268)
> 	at org.apache.tools.ant.Task.perform(Task.java:363)
> 	at org.apache.tools.ant.Target.execute(Target.java:300)
> 	at org.apache.tools.ant.Target.performTasks(Target.java:327)
> 	at org.apache.tools.ant.Project.executeTarget(Project.java:1213)
> 	at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:381)
> 	at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:268)
> 	at org.apache.tools.ant.Task.perform(Task.java:363)
> 	at org.apache.tools.ant.Target.execute(Target.java:300)
> 	at org.apache.tools.ant.Target.performTasks(Target.java:327)
> 	at org.apache.tools.ant.Project.executeTarget(Project.java:1213)
> 	at
org.apache.tools.ant.Project.executeTargets(Project.java:1061)
> 	at org.apache.tools.ant.Main.runBuild(Main.java:667)
> 	at org.apache.tools.ant.Main.startAnt(Main.java:187)
> 	at org.apache.tools.ant.Main.start(Main.java:151)
> 	at org.apache.tools.ant.Main.main(Main.java:234)
> 
> Total time: 26 seconds
> ---------------------------------------------
> 
> 
> 
> 
> To subscribe to this information via syndicated feeds:
> RSS: http://lsd.student.utwente.nl/gump/jakarta-cactus/jakarta-cactus-
> sample-servlet-12.rss | Atom:
http://lsd.student.utwente.nl/gump/jakarta-
> cactus/jakarta-cactus-sample-servlet-12.atom
> 
> --
> Gump http://gump.apache.org/
> [lsd]
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-dev-help@jakarta.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org

Re: How to debug a Gump build problem?

Posted by "Adam R. B. Jack" <aj...@trysybase.com>.

> Uh, Adam and Antoine asked access to moof and I gave it to them. I
> didn't do anything else.
>
> Guys, status?

I'd point you to a posting (yesterday) with a subject of 'gump on moof', but
our eyebrowse index seems dorked. Can you see it?

regards

Adam


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org

Re: How to debug a Gump build problem?

Posted by Stefano Mazzocchi <st...@apache.org>.

Stefan Bodewig wrote:

> Currently Gump doesn't run on any ASF machine, unless Stefano's
> efforts on moof have come further along than I thought.

Uh, Adam and Antoine asked access to moof and I gave it to them. I 
didn't do anything else.

Guys, status?

-- 
Stefano.

Re: How to debug a Gump build problem?

Posted by Michael Davey <Mi...@coderage.org>.

Stefan Bodewig wrote:

>On Thu, 11 Mar 2004, Vincent Massol <vm...@pivolis.com> wrote:
>  
>
>>The biggest problem is that Gump doesn't run the build in the same
>>than projects are running their builds! It's using sysclasspathonly
>>feature and that's not the way it's run by project.
>>    
>>
[snip]

>>Maybe an alternative would be for Gump to try to run the project
>>using sysclasspatonly first and then if it fails, it will run
>>"normally". The reports would show both outcomes. That would provide
>>useful feedback.
>>    
>>
>
>Sure.  This is part of the idea set on how to determine who is
>responsible for a failing build.
>  
>
I think a big part of the problem is that individual projects tend to either
include snapshots of their dependencies or profide a get-deps style
target that downloads snapshots of their dependencies from ibiblio.

While this is fine for a release, because the dependecies are effectively
hard-coded even for CVS HEAD, it is easy to forget to update the
dependencies over time.

I can see three possible solutions:

1.  provide some logic in Gump to understand both snapshots of
dependencies in CVS and the Ant <get tag; nag if it looks like the
hard-coded dependencies are falling behind. 

2.  encourage projects to provide an Ant target or Maven goal that
cvs checkout's and builds each dependancy.  This target would only
be used by developers to test integration. 

3.  Ask ibiblio to provide softlinks called "*latest*.jar" that point to
the latest version of each project in each directory.  Ask projects to
upload their latest jar to ibiblio as part of their release process.  Ask
projects to remove their dependencies from their CVS and provide
a get-deps target/goal instead.  Ask projects to use "*latest*" in
their get-deps target/goal in CVS HEAD, only changing them
to a specific version temporarily at release time.

(1)  may be difficult to acomplish with projects dependant on, for
example, xml-xerces1.

(2) would probably not be all that useful as there would be no
guarantee that cvs HEAD is buildable - as we see every day with
Gump.

(3) expects a lot of everyone.  If projects follow good practice by
tagging a release, it wouldn't take much work to get Gump to
monitor which projects are friends of solution 3.

-- 
Michael

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org