You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Gu...@icarus.apache.org on 2003/03/03 11:51:48 UTC
[GUMP] Build Failure - Cocoon2
----------------------------------------------------
This email is autogenerated from the output from:
<http://cvs.apache.org/builds/gump/2003-03-03/xml-cocoon2.html>
----------------------------------------------------
Buildfile: build.xml
BUILD FAILED
Target `gump' does not exist in this project.
Total time: 1 second
Re: [GUMP] Build Failure - Cocoon2
Posted by Jeff Turner <je...@apache.org>.
On Mon, Mar 03, 2003 at 10:32:04AM -0500, Sam Ruby wrote:
> Stefano Mazzocchi wrote:
> >
> >Yes, preaching to the converted. I think that Forrestbot can be the only
> >serious unit test that can be useful to Cocoon.
>
> I am?
>
> <joke>Is there a word in Italian for people who assert that they are
> pious, but you don't tend to see them in church all that often?</joke>
>
> Forrestbot is a specific example. When that effort started, I tried to
> see if there was an potential synergy with Gump, but the perception I
> got was that that effort was exclusively about publishing and not about
> regression testing.
That is mostly true, although I've subsequently written add-on shell
scripts to always use the latest version of Forrest.
It would be fairly easy to throw in latest versions of the Cocoon and
Avalon jars, fetched from wherever Gump puts them.
I don't think Forrest would make a very good Cocoon test suite though,
because:
- Forrest doesn't exercise even 5% of what Cocoon offers.
- Forrest is trying to provide a service to users, not keep up with
bleeding edge Cocoon.
I think that resurrecting the Anteater[1] test scripts is a much better
plan. Each block could have a tests/ directory, with a handful of
Anteater scripts exercising the samples in that block. I once had a
fairly complete Cocoon test suite running (and 80% passing), but the
samples layout kept changing and it gradually became out of date.
--Jeff
[1] http://aft.sf.net
> My current "preaching" is an attempt to restart that discussion.
> Stefano, given your recent interest in Gump, now seems like an opportune
> time.
>
> I don't care if it is run on my machine or on somebody else's. I don't
> care if any gump code is used in the process. But I do think it would
> be helpful to run Forrest with up to the minute versions of everything
> in an effort to get more people talking, and talking earlier, with
> developers of components that they depend on.
>
> And I am willing to help.
>
> - Sam Ruby
>
>
Re: [GUMP] Build Failure - Cocoon2
Posted by Stefano Mazzocchi <st...@apache.org>.
Sam Ruby wrote:
> Stefano Mazzocchi wrote:
>
>>
>> Yes, preaching to the converted. I think that Forrestbot can be the
>> only serious unit test that can be useful to Cocoon.
>
>
> I am?
You are.
> <joke>Is there a word in Italian for people who assert that they are
> pious, but you don't tend to see them in church all that often?</joke>
:)
I said I'm converted, never said I'm pious :)
> Forrestbot is a specific example. When that effort started, I tried to
> see if there was an potential synergy with Gump, but the perception I
> got was that that effort was exclusively about publishing and not about
> regression testing.
The Forrest project started as a way to back gump on documentation for
apache stuff and later turned into something broader. My involvement
with it has suffered lack of time and focus, also because,
darwinistically speaking, others were taking care of it better than I could.
> My current "preaching" is an attempt to restart that discussion.
> Stefano, given your recent interest in Gump, now seems like an opportune
> time.
I agree. We also have a java-friendly machine to host it (moof).
> I don't care if it is run on my machine or on somebody else's. I don't
> care if any gump code is used in the process. But I do think it would
> be helpful to run Forrest with up to the minute versions of everything
> in an effort to get more people talking, and talking earlier, with
> developers of components that they depend on.
>
> And I am willing to help.
This is good news and I'm happy to talk, but I can't volunteer to help
since I have, unfortunately, different priorities at the moment.
Right now I want to cleanup the cocoon build system because I need it
for my stuff. I don't use Forrest ATM, nor cocoon uses forrest for its
documentation (yet), nor apache projects seems to like forrest that much.
To be honest, I'm sick of pushing for things to happen: I'm going to do
with I need and push to obtain what I think it's useful for me. Pure
sellfishness.
This said, I'd help whenever I could, but my time is very limited at the
moment and very focused on getting the cocoon core cleaned efficient and
ready to be released and create community involvement and development
tools that can keep the process running smoothly even when I'm not looking.
So, running forrestbot is cool and helps me, but there are much higher
priorities on my very personal todo list.
--
Stefano Mazzocchi <st...@apache.org>
Pluralitas non est ponenda sine necessitate [William of Ockham]
--------------------------------------------------------------------
Re: [GUMP] Build Failure - Cocoon2
Posted by Sam Ruby <ru...@apache.org>.
Stefano Mazzocchi wrote:
>
> Yes, preaching to the converted. I think that Forrestbot can be the only
> serious unit test that can be useful to Cocoon.
I am?
<joke>Is there a word in Italian for people who assert that they are
pious, but you don't tend to see them in church all that often?</joke>
Forrestbot is a specific example. When that effort started, I tried to
see if there was an potential synergy with Gump, but the perception I
got was that that effort was exclusively about publishing and not about
regression testing.
My current "preaching" is an attempt to restart that discussion.
Stefano, given your recent interest in Gump, now seems like an opportune
time.
I don't care if it is run on my machine or on somebody else's. I don't
care if any gump code is used in the process. But I do think it would
be helpful to run Forrest with up to the minute versions of everything
in an effort to get more people talking, and talking earlier, with
developers of components that they depend on.
And I am willing to help.
- Sam Ruby
Re: [GUMP] Build Failure - Cocoon2
Posted by Stefano Mazzocchi <st...@apache.org>.
Sam Ruby wrote:
> Stefano Mazzocchi wrote:
>
>> Gump@icarus.apache.org wrote:
>>
>>> ----------------------------------------------------
>>> This email is autogenerated from the output from:
>>> <http://cvs.apache.org/builds/gump/2003-03-03/xml-cocoon2.html>
>>> ----------------------------------------------------
>>>
>>> Buildfile: build.xml
>>>
>>> BUILD FAILED
>>> Target `gump' does not exist in this project.
>>
>>
>> Damn, forgot to update gump. This nagging thing is really useful :)
>
>
> As you can see from the nag you have seen on the dropping of projects
> provides evidence that you can have e-mails sent to any mailing list
> based on matching a regular expression against the output of any run.
>
> One of my favorites was adding the following to xml-fop:
>
> <regexp pattern="/Fatal error during transformation/"
> to="xalan-dev@xml.apache.org"/>
>
> Xalan has a fairly extensive test suite. Despite this, there was a
> change that caused a problem with one of fop's stylesheets. By
> observing that it worked on one day and failed on the next, the scope of
> potential changes that might have caused this was considerably reduced.
> I was able to narrow this down to a single change without understanding
> anything about the design or implementation of xalan by simply doing cvs
> updates specifying various timestamps and rerunning the build.
>
> Imagine the possibilities of running Forrest on various sites (w/o
> necessarily publishing the output), for no other reason than to see if
> recent changes to cocoon will break something downstream.
Yes, preaching to the converted. I think that Forrestbot can be the only
serious unit test that can be useful to Cocoon.
--
Stefano Mazzocchi <st...@apache.org>
Pluralitas non est ponenda sine necessitate [William of Ockham]
--------------------------------------------------------------------
Re: [GUMP] Build Failure - Cocoon2
Posted by Sam Ruby <ru...@apache.org>.
Stefano Mazzocchi wrote:
> Gump@icarus.apache.org wrote:
>
>> ----------------------------------------------------
>> This email is autogenerated from the output from:
>> <http://cvs.apache.org/builds/gump/2003-03-03/xml-cocoon2.html>
>> ----------------------------------------------------
>>
>> Buildfile: build.xml
>>
>> BUILD FAILED
>> Target `gump' does not exist in this project.
>
> Damn, forgot to update gump. This nagging thing is really useful :)
As you can see from the nag you have seen on the dropping of projects
provides evidence that you can have e-mails sent to any mailing list
based on matching a regular expression against the output of any run.
One of my favorites was adding the following to xml-fop:
<regexp pattern="/Fatal error during transformation/"
to="xalan-dev@xml.apache.org"/>
Xalan has a fairly extensive test suite. Despite this, there was a
change that caused a problem with one of fop's stylesheets. By
observing that it worked on one day and failed on the next, the scope of
potential changes that might have caused this was considerably reduced.
I was able to narrow this down to a single change without
understanding anything about the design or implementation of xalan by
simply doing cvs updates specifying various timestamps and rerunning the
build.
Imagine the possibilities of running Forrest on various sites (w/o
necessarily publishing the output), for no other reason than to see if
recent changes to cocoon will break something downstream.
http://www.xptester.org/_ZABLE%5B0%5D_/tab/9/excerpts/xptestvalues.htm
- Sam Ruby
Re: [GUMP] Build Failure - Cocoon2
Posted by Stefano Mazzocchi <st...@apache.org>.
Gump@icarus.apache.org wrote:
> ----------------------------------------------------
> This email is autogenerated from the output from:
> <http://cvs.apache.org/builds/gump/2003-03-03/xml-cocoon2.html>
> ----------------------------------------------------
>
> Buildfile: build.xml
>
> BUILD FAILED
> Target `gump' does not exist in this project.
Damn, forgot to update gump. This nagging thing is really useful :)
--
Stefano Mazzocchi <st...@apache.org>
Pluralitas non est ponenda sine necessitate [William of Ockham]
--------------------------------------------------------------------