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
On Thu, 11 Mar 2004, Vincent Massol [EMAIL PROTECTED] wrote:
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.
It fails on lsd as well as gump.covalent.net, so it fails using Gumpy
or traditional Gump
and then if it fails, it will run normally. The
reports would show both outcomes. That would provide useful feedback.
Thanks
-Vincent
-Original Message-
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Sent: 11 March 2004 10:06
To: [EMAIL PROTECTED]
Subject: Re: How to debug a Gump build problem
On Thu, 11 Mar 2004, Vincent Massol [EMAIL PROTECTED] wrote:
It's a pity that
http://lsd.student.utwente.nl/gump/jakarta-cactus/jakarta-cactus-sample-
servlet-13.html has a pre-req failure as we would have been able to
see if it passed the tests fine (it's using Tomcat 4.x and not
Tomcat
-Original Message-
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Sent: 11 March 2004 10:45
To: [EMAIL PROTECTED]
Subject: Re: How to debug a Gump build problem?
On Thu, 11 Mar 2004, Vincent Massol [EMAIL PROTECTED] wrote:
It's a pity that
http://lsd.student.utwente.nl/gump
On Thu, 11 Mar 2004, Vincent Massol [EMAIL PROTECTED] wrote:
What would be very useful is to check the /tmp directory.
tomcat3x.zip in my home dir.
Cheers
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Vincent,
I've rerun the build with tcpdump running to get an idea of what is
actually happening:
- GET /cactus-sample-servlet-cactified/ServletRedirector?Cactus_Service=RUN_TEST
- 200 OK
- GET /cactus-sample-servlet-cactified/ServletRedirector?Cactus_Service=RUN_TEST
- 200 OK
- GET
Vincent Massol wrote:
My question is: What are the facilities given to projects to debug Gump
builds?
not that much, at the moment. The main gumpy runs on a machine in our
flat's living room.
More specifically: Do we have a shell account with read access to the
directory where Gump built the
13:14
To: [EMAIL PROTECTED]
Subject: Re: How to debug a Gump build problem?
Vincent,
I've rerun the build with tcpdump running to get an idea of what is
actually happening:
- GET /cactus-sample-servlet-
cactified/ServletRedirector?Cactus_Service=RUN_TEST
- 200 OK
- GET /cactus-sample
2004 15:08
To: 'Gump code and data'
Subject: RE: How to debug a Gump build problem?
Wow. Good debugging! Thanks Stefan for your help.
I'm trying to run the cactus build on cvs.apache.org to see if I can
reproduce the problem. I'll let you know as I make progress.
Thanks
-Vincent
Stefan Bodewig wrote:
On Thu, 11 Mar 2004, Vincent Massol [EMAIL PROTECTED] 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
11 matches
Mail list logo
