BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 12 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Module castor success, but with warnings. [EMAIL PROTECTED]: Module eyebrowse success, but with warnings. [EMAIL PROTECTED]: Project txt2html-task (in module jakarta-servletapi-5) success, but with warnings. [EMAIL PROTECTED]: Module struts success, but with warnings. [EMAIL PROTECTED]: Module lenya success, but with warnings. [EMAIL PROTECTED]: Project jtidy-cvs (in module jtidy) failed [EMAIL PROTECTED]: Project jetty-plus (in module jetty) failed [EMAIL PROTECTED]: Project excalibur-event (in module excalibur) success [EMAIL PROTECTED]: Project excalibur-thread (in module excalibur) success [EMAIL PROTECTED]: Project groovy (in module groovy) failed [EMAIL PROTECTED]: Project maven (in module maven) failed [EMAIL PROTECTED]: Project maven-bootstrap (in module maven) failed *** G U M P [EMAIL PROTECTED]: Module castor success, but with warnings. To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Module castor contains errors. The current state of this module is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/castor/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -ERROR- *** Failed to update from source control. Stale contents *** The following work was performed: http://brutus.apache.org/gump/public/castor/gump_work/update_castor.html Work Name: update_castor (Type: Update) Work ended in a state of : Failed Elapsed: Command Line: cvs -q -z3 -d :pserver:[EMAIL PROTECTED]:2401/cvs/castor update -P -d -A [Working Directory: /usr/local/gump/public/workspace/cvs/castor] - cvs [update aborted]: connect to castor.exolab.org(65.222.219.20):2401 failed: No route to host - To subscribe to this information via syndicated feeds: - RSS: http://brutus.apache.org/gump/public/castor/rss.xml - Atom: http://brutus.apache.org/gump/public/castor/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2409122004, brutus:brutus-public:2409122004 Gump E-mail Identifier (unique within run) #1. *** G U M P [EMAIL PROTECTED]: Module eyebrowse success, but with warnings. To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Module eyebrowse contains errors. The current state of this module is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/eyebrowse/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -ERROR- *** Failed to update from source control. Stale contents *** The following work was performed: http://brutus.apache.org/gump/public/eyebrowse/gump_work/update_eyebrowse.html Work Name: update_eyebrowse (Type: Update) Work ended in a state of : Failed Elapsed: 3 mins 5 secs Command Line: cvs -q -z3 -d :pserver:[EMAIL PROTECTED]:2401/cvs update -P -d -A [Working Directory: /usr/local/gump/public/workspace/cvs/eyebrowse] - cvs [update aborted]: unrecognized auth response from cvs.tigris.org: cvs pserver: Invalid reply from auth server (32063) looking for (guest) - To subscribe to this information via syndicated feeds: - RSS: http://brutus.apache.org/gump/public/eyebrowse/rss.xml - Atom: http://brutus.apache.org/gump/public/eyebrowse/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2409122004, brutus:brutus-public:2409122004 Gump E-mail Identifier (unique within run) #2. *** G U M P [EMAIL PROTECTED]: Project txt2html-task (in module jakarta-servletapi-5) success, but with warnings. To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project txt2html-task contains errors. The current state of this project is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/jakarta-servletapi-5/txt2html-task/index.html That said, some information snippets are provided here. The following annotations
Re: [RT] Gump 3.0 - Database Model
Since I received no pushback on my proposal, let's move on discussing the database model. I see this model is good enough for certain aspects of the proposed 3.0, but not for all. We can't store the metadata in it, in order to perform builds from, there is clearly insufficient information. That said, I am more than happy to start on a 3.0 break-up by splitting the outputs from the presentation of those outputs via this model. That said, I still need more information on the contents of ids (and such), to verify the model is correct. Here are some initial reactions: One thing I noticed you mentioned was a desire for this database model to allow Gump to be distributed. I like that goal. We can't assume one host can do all builds (although Brutus is doing a fine fine job) so perhaps we could allow different hosts to build and contribute data for individual aspects. Maybe this is a goal to work towards, not focus on now, but I beleive that project id including a host are not correct (they ought be independent of the host) [Q: Are we comfortable with allowing remote hosts to connect to a center MySQL database, or do we need an intermediary representation and more secure protocol for such?] Do we need environment, i.e, kaffe or JDK 1.5 or whatever? Ought we have hosts/workspaces as mainly informational, with environment (what ought be the only differentiator for two builds of the same stuff, at exact time) as the key to builds? Do we need to allow build output to be optionally outside of the database, for those of us w/o terrabytes to spare? I like dependency within the database, but do we need more information (such as optional, etc.) on that? Also, one key piece of information in the current object model (which is used to document from) is cause. We didn't build this thing 'cos X failed to build. That, along with annotations (we build this, but w/o X 'cos it was an optional failed dependency), seem important. Personally I like all the information on this page being available. http://brutus.apache.org/gump/public/ant/ant/details.html Maybe (as a transition) we generate simple pages from the existing object model, but generate a results database (with history) and migrate more and more to it over time. Thanks, both, for putting this together. regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RT] Gump 3.0 - Database Model
This is cool. FWIW, here's some bits from my experience, implemeting something similar in a MySQL database. In my Build Results system, I have a schema that also includes a few additional things: - abritrary groupings of projects, which helps in organizaing various forms of the presentation of the data - the general notion of attributes associated with each: - build (instance) - project - group - the whole system And since my system is focused on creating interaction between people about given built baselines, I have the notion of a notes history associated with any given build, in a similar spirit as the comment history of a given bug in bugzilla. Like the notes table, I have separate tables for (references to) artifacts, and another for results, to support any arbitrary number of artifacts/results to a given build-instance. This could be hidden in your diagram inside the builds entity/table, but wasn't explicit. I've built a lot of generality into my schema, since I need to support many inputs into this database, from various (new and old) build systems. Thus things like the result table is kept very general within the database. One area that is not very well thought out (in my case) are how results and/or build instances depend on each other, a core requirement for Gump, as it seems. Hope this helps. Comments? wade Stefano Mazzocchi [EMAIL PROTECTED] wrote on 12/08/2004 06:32:34 PM: Since I received no pushback on my proposal, let's move on discussing the database model. I think the first step is to identify the entities that we want to model, their relationships and their respective cardinality. Here is what Leo and I came up with so far (attached as PDF). Comments/criticism/questions appreciated. -- Stefano.
Re: stinking *no longer* email still flooding lists!
Sorry, who was spammed and when/with what? [I recently had to unsubscribe
from the myriad of mailing lists I was on due to mental bandwidth reasons.]
Please send on a sample.
If a success message then we have a rogue branch running somewhere ('cos I
fixed HEAD and LIVE).
If a warning message, maybe that is a logic bug.
If a failure, I doubt you'd be complaining.
Info/insight please.
regards
Adam
- Original Message -
From: Stefano Mazzocchi [EMAIL PROTECTED]
To: Gump [EMAIL PROTECTED]
Sent: Thursday, December 09, 2004 8:11 AM
Subject: stinking *no longer* email still flooding lists!
I'm about ready to pull the plug on gump sending email until we figure
out how to stop spamming people!
--
Stefano.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
PyUnit (was Re: stinking *no longer* email still flooding lists!_
We need more unit tests, to weed out whatever is going on with state. Since we seem game to install Python packages now, mind if I look at moving us to this (and off our proprietary version?): http://pyunit.sourceforge.net/ regards Adam - Original Message - From: Stefano Mazzocchi [EMAIL PROTECTED] To: Gump [EMAIL PROTECTED] Sent: Thursday, December 09, 2004 8:11 AM Subject: stinking *no longer* email still flooding lists! I'm about ready to pull the plug on gump sending email until we figure out how to stop spamming people! -- Stefano. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PyUnit (was Re: stinking *no longer* email still flooding lists!_
Adam R. B. Jack wrote: We need more unit tests, to weed out whatever is going on with state. Since we seem game to install Python packages now, mind if I look at moving us to this (and off our proprietary version?): http://pyunit.sourceforge.net/ I actually started work on that. PyUnit has been in the distro since 2.1... http://www.python.org/doc/current/lib/module-unittest.html just do ./gump test and that uses a wrapper between the official PyUnit and our own. cheers! - LSD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: stinking *no longer* email still flooding lists!
Gump sent a success message for Jmeter-dev earlier today:
[...]
Received: from Unknown (HELO [127.0.0.1]) (209.237.227.198)
by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 09 Dec 2004 02:39:08 -0800
Date: Thu, 09 Dec 2004 02:35:39 PST
From: Gump-build [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [EMAIL PROTECTED]: Project jakarta-jmeter (in module
jakarta-jmeter) success
On Thu, 9 Dec 2004 11:57:12 -0700, Adam R. B. Jack [EMAIL PROTECTED] wrote:
Sorry, who was spammed and when/with what? [I recently had to unsubscribe
from the myriad of mailing lists I was on due to mental bandwidth reasons.]
Please send on a sample.
If a success message then we have a rogue branch running somewhere ('cos I
fixed HEAD and LIVE).
If a warning message, maybe that is a logic bug.
If a failure, I doubt you'd be complaining.
Info/insight please.
regards
Adam
- Original Message -
From: Stefano Mazzocchi [EMAIL PROTECTED]
To: Gump [EMAIL PROTECTED]
Sent: Thursday, December 09, 2004 8:11 AM
Subject: stinking *no longer* email still flooding lists!
I'm about ready to pull the plug on gump sending email until we figure
out how to stop spamming people!
--
Stefano.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
BATCH: Unable to send...
Dear Gumpmeisters, The following 1 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Project lenya (in module lenya) failed *** G U M P [EMAIL PROTECTED]: Project lenya (in module lenya) failed Failed with to: [EMAIL PROTECTED] from: [Gump] Failed to send notify e-mail: (450, 'FQDN required in the envelope sender', 'Gump') To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project lenya has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - lenya : Content Management System Full details are available at: http://brutus.apache.org/gump/public/lenya/lenya/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on cocoon exists, no need to add for property cocoon.src.dir. -INFO- Failed with reason build failed The following work was performed: http://brutus.apache.org/gump/public/lenya/lenya/gump_work/build_lenya_lenya.html Work Name: build_lenya_lenya (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs Command Line: java -Djava.awt.headless=true org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dcocoon.src.dir=/usr/local/gump/public/workspace/cocoon/build/cocoon-09122004 -Davalonapi.jar=/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-09122004.jar -Dlogkit.jar=/usr/local/gump/public/workspace/avalon-trunk/runtime/logkit/target/deliverables/jars/avalon-logkit-09122004.jar -Dversion=09122004 webapp [Working Directory: /usr/local/gump/public/workspace/lenya] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/lenya/tools/anttasks:/usr/local/gump/public/workspace/lenya/build/lenya-09122004/classes:/usr/local/gump/public/workspace/cocoon/build/cocoon-09122004/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-09122004/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-09122004/cocoon-deprecated.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-stylebook.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/logkit/target/deliverables/jars/avalon-logkit-09122004.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-09122004.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-09122004.jar - Buildfile: build.xml init: [echo] --- Apache Lenya 09122004 [1999-2004] [echo] Building with Apache Ant version 1.7alpha compiled on December 9 2004 using build file /home/gump/workspaces2/public/workspace/lenya/build.xml build-cocoon: [echo] Building Cocoon with our properties [copy] Copying 2 files to /usr/local/gump/public/workspace/cocoon/build/cocoon-09122004 BUILD FAILED /home/gump/workspaces2/public/workspace/lenya/src/targets/init-build.xml:88: The following error occurred while executing this line: java.io.FileNotFoundException: /usr/local/gump/public/workspace/cocoon/build/cocoon-09122004/build.xml (No such file or directory) Total time: 2 seconds - To subscribe to this information via syndicated feeds: - RSS: http://brutus.apache.org/gump/public/lenya/lenya/rss.xml - Atom: http://brutus.apache.org/gump/public/lenya/lenya/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 25000909122004, brutus:brutus-public:25000909122004 Gump E-mail Identifier (unique within run) #15. -- Apache Gump http://gump.apache.org/ [Instance: brutus] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: stinking *no longer* email still flooding lists!
Could I see the Gump footer (at bottom of the e-mail)? If I did correctly
comment out success e-mails (and I would like to believe that even I can do
that) then I need to determine why it might not be in some branch (likely
LIVE).
regards
Adam
- Original Message -
From: sebb [EMAIL PROTECTED]
To: Gump code and data [EMAIL PROTECTED]
Sent: Thursday, December 09, 2004 12:43 PM
Subject: Re: stinking *no longer* email still flooding lists!
Gump sent a success message for Jmeter-dev earlier today:
[...]
Received: from Unknown (HELO [127.0.0.1]) (209.237.227.198)
by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 09 Dec 2004 02:39:08 -0800
Date: Thu, 09 Dec 2004 02:35:39 PST
From: Gump-build [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [EMAIL PROTECTED]: Project jakarta-jmeter (in module
jakarta-jmeter) success
On Thu, 9 Dec 2004 11:57:12 -0700, Adam R. B. Jack [EMAIL PROTECTED]
wrote:
Sorry, who was spammed and when/with what? [I recently had to
unsubscribe
from the myriad of mailing lists I was on due to mental bandwidth
reasons.]
Please send on a sample.
If a success message then we have a rogue branch running somewhere
('cos I
fixed HEAD and LIVE).
If a warning message, maybe that is a logic bug.
If a failure, I doubt you'd be complaining.
Info/insight please.
regards
Adam
- Original Message -
From: Stefano Mazzocchi [EMAIL PROTECTED]
To: Gump [EMAIL PROTECTED]
Sent: Thursday, December 09, 2004 8:11 AM
Subject: stinking *no longer* email still flooding lists!
I'm about ready to pull the plug on gump sending email until we figure
out how to stop spamming people!
--
Stefano.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: stinking *no longer* email still flooding lists!
Hmm, ok -- the merge of trunk into live doesn't seem to be working: I followed the standard procedure (that Leo first helped me out with): http://wiki.apache.org/gump/GumpBranches ... minotaur svn info Path: . URL: https://svn.apache.org/repos/asf/gump/trunk Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 Revision: 111433 Node Kind: directory Schedule: normal Last Changed Author: ajack Last Changed Rev: 110051 Last Changed Date: 2004-12-06 15:34:27 -0800 (Mon, 06 Dec 2004) Properties Last Updated: 2004-12-09 13:24:11 -0800 (Thu, 09 Dec 2004) minotaur cd ../gump-live/ minotaur svn info Path: . URL: https://svn.apache.org/repos/asf/gump/live Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 Revision: 111433 Node Kind: directory Schedule: normal Last Changed Author: ajack Last Changed Rev: 110068 Last Changed Date: 2004-12-06 19:32:01 -0800 (Mon, 06 Dec 2004) Properties Last Updated: 2004-12-09 13:24:23 -0800 (Thu, 09 Dec 2004) minotaur svn merge -r 110068:110051 https://svn.apache.org/repos/asf/gump/trunk/ but I see no changes, and when I attempt a commit -- it simply returns (with nothing to do). Could SVN have been upgraded on minotaur (since a few months ago) and we need a new process or something? Anybody more SVN savvy than I able to figure this out? Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: stinking *no longer* email still flooding lists!
Is this what you mean?
== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 2409122004, brutus:brutus-public:2409122004
Gump E-mail Identifier (unique within run) #52.
S.
On Thu, 9 Dec 2004 14:22:24 -0700, Adam R. B. Jack [EMAIL PROTECTED] wrote:
Could I see the Gump footer (at bottom of the e-mail)? If I did correctly
comment out success e-mails (and I would like to believe that even I can do
that) then I need to determine why it might not be in some branch (likely
LIVE).
regards
Adam
- Original Message -
From: sebb [EMAIL PROTECTED]
To: Gump code and data [EMAIL PROTECTED]
Sent: Thursday, December 09, 2004 12:43 PM
Subject: Re: stinking *no longer* email still flooding lists!
Gump sent a success message for Jmeter-dev earlier today:
[...]
Received: from Unknown (HELO [127.0.0.1]) (209.237.227.198)
by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 09 Dec 2004 02:39:08 -0800
Date: Thu, 09 Dec 2004 02:35:39 PST
From: Gump-build [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [EMAIL PROTECTED]: Project jakarta-jmeter (in module
jakarta-jmeter) success
On Thu, 9 Dec 2004 11:57:12 -0700, Adam R. B. Jack [EMAIL PROTECTED]
wrote:
Sorry, who was spammed and when/with what? [I recently had to
unsubscribe
from the myriad of mailing lists I was on due to mental bandwidth
reasons.]
Please send on a sample.
If a success message then we have a rogue branch running somewhere
('cos I
fixed HEAD and LIVE).
If a warning message, maybe that is a logic bug.
If a failure, I doubt you'd be complaining.
Info/insight please.
regards
Adam
- Original Message -
From: Stefano Mazzocchi [EMAIL PROTECTED]
To: Gump [EMAIL PROTECTED]
Sent: Thursday, December 09, 2004 8:11 AM
Subject: stinking *no longer* email still flooding lists!
I'm about ready to pull the plug on gump sending email until we figure
out how to stop spamming people!
--
Stefano.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
directory and gump
Hi, I've regenerated the eve gump descriptor using a development version of the Maven Gump plugin. I'll do the others now. I reread the documentation and did the following: - stopped mapping ids (the ability is there for the project to do that in its descriptor) - removed work and mkdir (these seem irrelevant for Maven) - added junitreport - fixed svn - added multiproject support Hopefully that's it... The only thing I am now unsure about: I set module name to the artifactId, not the groupId. The reason for this is I believe (though don't see anything supporting or contradicting it in the doco) that gump may expect that name to be unique in the workspace, and groupId will not be. There is still the risk that there will be namespace issues later, but we can cross that bridge when we come to it. So, when/how will I know if this is correct? Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
