Re: [RT] a strategy for better gump action/reaction analysis
Stefano Mazzocchi wrote: gump action/reaction analysis could be otherwise named blames or nags but I like to think that if I break a build down 3 layers of dependencies, I'm not really screwing up, but merely I need to be advised or the 'reaction' of my 'action'. I have already stated that finding the exact action (commit) that created a particular reaction (broken build) is, in general, very computationally intensive, but this is so only if we have to regenerate the state of the build without any sort of caching. Our jar archive is an history of all the build-produced artifacts. Now, I wonder, is this really what we want? If left alone, this archive will slowly saturate all existing disk space. And pretty fast. Do we really need to save *all* the states? I think we just need one per project: the last successful one, tagged with the day of the checkout (or the SVN revision number, whichever you want) Gump should remove the previous ones, save space and make things more certain. +1 - o - So, assuming that gump was working like that, how would a better (but still simple) algorithm work like? Say we have project B that depends on project A. Both projects compiled yesterday. We have artifacts from both in the archive. Now, B doesn't build while A builds. Whose fault is that? There is not enough information in a single build to prove that, so we have to build again, but changing the constrains. If A builds but B doesn't, there are two possibilies: 1) B broke itself 2) A broke B Since we know that B-yesterda built against A-yesterday, than the result of the B-today against A-yesterday will tell us if it's 1) or 2) Ok, with two projects is easy, what about three? C - B - A worked yesterday, but today C is broken and B and A work. Who broke the build? First of all, is it safe to assume that since A is shielded by B and both B and A work, A has no influence on C? If so, we just apply the same algorithm for [C - B]. thoughts? One step at a time, Lets just getting gump using the last built jar, and see what kind of patterns emerge. R, Nick smime.p7s Description: S/MIME Cryptographic Signature
Re: Spam hijacking Gump content...
Not sure what we can do about that. Especially if they are forging the envelope headers to be someone on the list. *shrug* How does Gump feel about digital signatures of its messages? ;-) -- justin That is a cool Idea, Several security concerns about the process running gump. Also then the GUMP users would have to subscribe to the list. However unless the list rejects unsigned emails, it will hardly fix prevent the problem. R, Nick smime.p7s Description: S/MIME Cryptographic Signature
Re: forrestbot on brutus
Dave Brondsema wrote: On Thu, 29 Jul 2004, Nick Chalko wrote: Would we be able to run tomcat behind httpd with SSL? Would we be able to access ASF system login info (PAM or /etc/passwd /etc/groups)? This would be so any committer can use their system login to log in to the webapp. +1 Remember we need to treat apps on brutus as untrusted and treat the results as such. Can you explain how this would relate to forrestbot? If I remember correctly forrestbot will do a cvs checkout of a docs and run forrest against it and publish the results. Does forrest bot run against any non apache cvs's ? If it does then we have to careful some could inserts malicious code in the remote cvs. Does this relate to forrestbot. smime.p7s Description: S/MIME Cryptographic Signature
Re: [VOTE] Give Adam Jack root access to brutus
Scott Sanders wrote: Doing this on general@ instead of pmc@, because of my own email issues. PMC members only vote, please. I know Adam is not a member, but I asked infrastructure, and they don't have a problem with it because it is already considered an insecure box. I would like to propose that Adam is given root privileges on brutus so that he can 'scratch his itches' WRT gump infrastructure. I am +1. Adam has done more than enough to not be held back by us :) +1 (and some one recommend Adam as a Member all ready) smime.p7s Description: S/MIME Cryptographic Signature
Re: forrestbot on brutus
+1 Remember we need to treat apps on brutus as untrusted and treat the results as such. Dave Brondsema wrote: Greetings gump-ers, from the other half of your namesake. I sent the following to infrastructure and they suggested running it on brutus. I wouldn't have any problem with that. We at Forrest would like to get an ASF-wide forrestbot installation set up. Forrestbot is now a set of ant buildfiles. There is also a web interface which is pure-java (no scripts like before) webapp that execute the ant buildfiles. The webapp is for on-demand build deploy. Cron jobs would be set up seperately if projects wanted scheduled builds and/or deploys. We don't have any strong feelings about where in URL-space the webapp should be. Anything like bot.forrest.apache.org or forrest.apache.org/forrestbot or forrestbot.apache.org would be fine. We'll leave that decision up to you. The requirements and installation procedure are on the Web Interface page: http://forrest.apache.org/docs/forrestbot-web-interface.html http://forrest.apache.org/docs/forrestbot.html You can see a demo of the webapp (build/deploy disabled) here: brondsema.gotdns.com:8080/forrestbot-webapp with user/pwd: forrest-dev/forrest-dev smime.p7s Description: S/MIME Cryptographic Signature
Re: Here's a wild idea
Adam R. B. Jack wrote:
The easiest thing is that for every project it spits out another page
with included only the icon, so that projects can simply include that
with Apache include in the pages they want.
Our we could maintain an icon at a known place,
{root}/module/project/state.png
Where we'd clearly want to uses the gump c-name to proxy pass, and not
brutus in {root}.
That said, maybe there is more fun to have w/ a less easy solutions. :)
Maybe Stefano's blog entry gives both cautions and ideas. Perhaps we could
dynamically create an image w/ state and things like a date (or something):
http://www.betaversion.org/~stefano/linotype/news/66/
FOG number and with appropriate icons would be cool.
0:-) FOG 1.0
:-) FOG .99 - .8
:-\FOG .2 - .79
:-[ FOG 0 - .19
etc
BTW: I've wonder if a 'Community Gumped' icon like the 'built with forrest'
one would be good. We could have folks link that to 'their' gump page, so
folks can double check. This would be less interactive, but also less
network intensive.
BTW: Didn't we say that after we went TLP we'd look at some sort of
marketing/logos/icons/catch phrases like this? Have some form of competition
asking for ideas?
regards,
Adam
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
smime.p7s
Description: S/MIME Cryptographic Signature
Re: [Fwd: [jira] Commented: (INFRA-95) Please create a python@apache.org mailing list]
Unless there is objection I will reopen the request as the Gump PMC Sam Ruby wrote: Why doesn't the gump PMC sponsor this mailing list? - Sam Ruby Original Message Subject: [jira] Commented: (INFRA-95) Please create a [EMAIL PROTECTED] mailing list Date: Thu, 22 Jul 2004 11:02:17 -0700 (PDT) From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] The following comment has been added to this issue: Author: Adam Jack Created: Thu, 22 Jul 2004 11:02 AM Body: This request is suspended (and can be closed/deleted) since (per http://www.apache.org/dev/list-setup.html) it is an invalid request; since no PMC made it. - View this comment: http://issues.apache.org/jira/browse/INFRA-95?page=comments#action_36825 - View the issue: http://issues.apache.org/jira/browse/INFRA-95 Here is an overview of the issue: - Key: INFRA-95 Summary: Please create a [EMAIL PROTECTED] mailing list Type: Task Status: Unassigned Priority: Major Project: Infrastructure Components: Mailing Lists Assignee: Reporter: Adam Jack Created: Wed, 21 Jul 2004 8:25 AM Updated: Thu, 22 Jul 2004 11:02 AM Description: Based upon this thread, I'd like to request a [EMAIL PROTECTED] mailing list. http://issues.apache.org/eyebrowse/[EMAIL PROTECTED]by=threadfrom=822734to=822734first=1count=13 This intention for this list is for general Python discussion amongst Pythonically inclined (or simply Python using) ASF folk. This list is not part of a project, nor does it have (to date) a tighter focus than things related to Python. I am willing to be moderator (and I'll look for another volunteer down the road). I don't know where (if anywhere) this list ought be 'advertized', nor if I can do that myself (I doubt I have much Karma @ ASF, I only commit to Gump and Depot). Thanks in advance for any pointers. Please let me know (via comments on this issue) if this request is premature/misguided, and/or if I can/should do anything more prior to making this request. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] smime.p7s Description: S/MIME Cryptographic Signature
Re: [RT] Was python a good idea?
Nicola Ken Barozzi wrote: Stefano Mazzocchi wrote: I have started to use python myself because I loved the much faster try/fail cycle of a scripting language and python looked a lot friendlier than other scripting languages. But in my experience, it doesn't scale in terms of complexity as much as java does. This is my impression also :-( Java: it's truly cross-platform and the Gump PMC members all know it quite well; easy to install * cons: dunno I think the main problem we will face in a Java Gump is dependencies. We will have to COMPLETELY resit depending on anything except JDK 1.4 R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RT] Was python a good idea?
Stefano Mazzocchi wrote: I think the main problem we will face in a Java Gump is dependencies. We will have to COMPLETELY resit depending on anything except JDK 1.4 Very true, but doable, IMO since we get XML/XSLT/DOM support in there. I might help more if it was in Java, but I don't see the need with out also changing to more of a pipeline architecture, or tackle using last good jar or something. Otherwise we are just spinning our wheels. R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
need a gump ID to prevent mismatched timestamps on jars.
Time stamp causes miss matched jars. I think we should set a gump-run-id property for build files to use in naming files. Adam Jack wrote: Project depot-update has an issue affecting its community integration. This issue affects 4 projects. Project State : 'Failed', Reason 'Missing Build Outputs' The following annotations were provided: -INFO- Sole jar [depot-update-gump-20040528.jar] identifier set to project name -INFO- Dependency on ant exists, no need to add for property ant.home. -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/depot/update/dist/depot-update-gump-20040528.jar -ERROR- See Directory Listing Work for Missing Outputs snip/ package-src: [jar] Building jar: /usr/local/gump/public/workspace/depot/update/build/depot-update/depot-update-0.1-dev-20040529.jar package: dist-jar: [copy] Copying 1 file to /usr/local/gump/public/workspace/depot/update/dist gump: [move] Moving 1 files to /usr/local/gump/public/workspace/depot/update/dist BUILD SUCCESSFUL Total time: 6 seconds - To subscribe to this information via syndicated feeds: RSS: http://brutus.apache.org:8080/gump/depot/depot-update/rss.xml Atom: http://brutus.apache.org:8080/gump/depot/depot-update/atom.xml -- Produced by Gump 2.0.3-alpha-0002. [Run (20040528 21:00:12, brutus:brutus-public:20040528 21:00:12)] http://brutus.apache.org:8080/gump/index.html http://brutus.apache.org:8080/gump/options.html -- Apache Gump http://gump.apache.org/ [Instance: brutus] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
blog this was: [GUMP@brutus]: logging-log4j/logging-log4j failed
We need to blog this on peas and carrots after the long vacation.
Ceki Gülcü wrote:
Problem solved. It appears that the org.xml.sax classes included in
the JDK differ from those of the original.
Dancing around the discrepancy is not too difficult once you know that
it exists. Thanks to gump for pointing out the difference.
How inconsiderate on the part of Sun to modify an existing API and
bundle the modified version with the JDK.
At 10:22 AM 5/27/2004, Ceki Gülcü wrote:
Hello all,
It appears that log4j is failing to compile on brutus. It compiles
fine on my side using JDK 1.4, 1.3 or 1.2. The problem appears to be
linked to the signature of the resolveEntity() method in
org.xml.sax.helpers.DefaultHandler. Contrary to what is declared by
the resolveEntity method in EntityResolver interface, the
resolveEntity method in the DefaultHandler is not declared as throwing
an IOException. (It masks the IOException.)
Here is the code from the org.apache.joran.Interpreter class which
fails to compile on Brutus.
// Joran builds as part of log4j.
package org.apache.joran;
public class Interpreter extends DefaultHandler {
/**
* If a specific entityResolver is set for this Interpreter
instance, then
* we use it to resolve entities. Otherwise, we use the default
implementation
* offered by the super class.
*/
public InputSource resolveEntity(String publicId, String systemId)
throws SAXException {
if(entityResolver == null) {
return super.resolveEntity(publicId, systemId);
} else {
try {
return entityResolver.resolveEntity(publicId, systemId);
} catch(IOException ioe) {
// fall back to the default implementation
return super.resolveEntity(publicId, systemId);
}
}
}
}
Which version of the org.xml.sax package is used on brutus? I am a bit
at a loss here.
Thanks in advance for shedding some light on to the matter.
At 10:38 PM 5/26/2004, [EMAIL PROTECTED] wrote:
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 folk at [EMAIL PROTECTED]
Project logging-log4j has an issue affecting its community integration.
This issue affects 213 projects.
Project State : 'Failed', Reason 'Build Failed'
The following are affected:
- ant-embed-optional : Java based build tool
- avalon : Avalon's main repository.
[snip]
Full details are available at:
http://brutus.apache.org:8080/gump/logging-log4j/logging-log4j/index.html
That said, some snippets follow:
The following annotations were provided:
-INFO- Failed with reason build failed
-INFO- Enable debug output, due to build failure.
The following work was performed:
http://brutus.apache.org:8080/gump/logging-log4j/logging-log4j/gump_work/build_logging-log4j_logging-log4j.html
Work Name: build_logging-log4j_logging-log4j (Type: Build)
State: Failed
Elapsed: 0 hours, 0 minutes, 4 seconds
Command Line: java -Djava.awt.headless=true
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar
org.apache.tools.ant.Main
-Dgump.merge=/usr/local/gump/public/gump/work/merge.xml
-Dbuild.sysclasspath=only -Dversion=20040526 jar
[Working Directory: /usr/local/gump/public/workspace/logging-log4j]
CLASSPATH :
/usr/local/j2sdk1.4.2_04/lib/tools.jar:/usr/local/gump/public/workspace/logging-log4j/dist/classes:/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-xalan2.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/jakarta-servletapi-4/lib/servlet.jar:/usr/local/gump/packages/jms1.0.2/lib/jms.jar:/usr/local/gump/packages/jmx-1_2-ri/lib/jmxri.jar:/usr/local/gump/packages/jmx-1_2-ri/lib/jmxtools.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/packages/javamail-1.3/mail.jar--
---
Buildfile: build.xml
init:
jndiCheck:
build.core:
[mkdir] Created dir:
/usr/local/gump/public/workspace/logging-log4j/dist/classes
[javac] Compiling 220 source files to
/usr/local/gump/public/workspace/logging-log4j/dist/classes
[javac]
/usr/local/gump/public/workspace/logging-log4j/src/java/org/apache/joran/Interpreter.java:301:
unreported exception java.io.IOException; must be caught or declared
to be thrown
[javac] return super.resolveEntity(publicId, systemId);
[javac] ^
[javac]
Peas and Carrots on Brutus
I have set up blojsom on brutus to run Peas and Carrots. http://brutus.apache.org:8080/blojsom/blog/ I also have a cron job to update /home/gump/blog with anoncvs. If it looks ok and infra has no objections I will let brutus take over peas and carrots. R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Blog and More ... link
You can use the more/ tag to tell blojom where to break at. I think we should have the license AFTER the more. Adam R. B. Jack wrote: I was just noticing this also. When Nick and I were previewing this last night it looked good. I think there was a PREVIEW work (before title), a PREV here link/link, and an hr/. It looked fine then. Interestingly http://www.planetapache.org displays it fine. I've just tried adding an hr/ to see if it affects things positively before Nick gets online... regards, Adam - Original Message - From: Stefan Bodewig [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, May 25, 2004 6:41 AM Subject: Blog and More ... link Hi, if you look at http://gump.chalko.com/gb/blog/Issues/?permalink=GumpStorm.txt, you'll see pretty much nothing at all because the More... link has been inserted somewhere in the middle of a comment (the license). blojsom doesn't seem to deal with comments well at all - it certainly shouldn't place the link somewhere inside and if you look at the main Peas and Carrots page you will see the license as clear text. I almost feel inclined to remove the license completely to work around this - or is there a better solution? More comment silliness can be seen here http://gump.chalko.com/gb/blog/Issues/?permalink=Cactus-CommonsHttpclient.t xt where the license becomes part of the rdf:description part for the trackback auto-discovery stuff, but the -- isn't escaped correctly leading to more problems. Mozilla displays the closing comment marker as clear text for example. Stefan - 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: [GUMP@brutus]: depot/depot-update prerequisite failed
Adam Jack wrote: \ The following annotations were provided: -INFO- Sole jar [depot-update-gump-20040524.jar] identifier set to project name -INFO- Dependency on ant exists, no need to add for property ant.home. -INFO- Prerequisite failed with reason build failed Please add which prereq failed. To subscribe to this information via syndicated feeds: RSS: http://brutus.apache.org:8080/gump/depot/depot-update/rss.xml Atom: http://brutus.apache.org:8080/gump/depot/depot-update/atom.xml -- Produced by Gump 2.0.3-alpha-0002. [Run (20040524 15:00:12, brutus:brutus-public:20040524 15:00:12)] http://brutus.apache.org:8080/gump/index.html http://brutus.apache.org:8080/gump/options.html -- Apache Gump http://gump.apache.org/ [Instance: brutus] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Installing tomcat 5 on brutus
I am attempting to install tomcat 5 on brutus for Adam to use with a forrest webapp for gump. Wish me luck, this is my first time on debian. R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Installing tomcat 5 on brutus
http://brutus.apache.org:8080/gump/index.html is up Adam, start pushing xdocs, and lets see what happens. Of course to get this to work I had to put stuff in tomcat/common/endorsed R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem running Apache Gump...
Ooops, sorry I did not know my test would mail the list. [EMAIL PROTECTED] wrote: There is a problem with the run at : brutus:python/gump/test/resources/full1/brutus.xml The log ought be at: /gumpy_log.txt The last (up to) 50 lines of the log are : MAVEN_HOME - [/usr/local/gump/maven-1.0-rc2] PATH - [/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/usr/local/j2sdk1.4.2_04/bin:/usr/local/gump/forrest/bin:/usr/local/gump/maven-1.0-rc2/bin:/usr/local/j2sdk1.4.2_04/bin:/usr/local/gump/forrest/bin:/usr/local/gump/maven-1.0-rc2/bin] TERM - [xterm] SHELL - [/bin/bash] SHLVL - [2] LOCAL_ENV - [local-env-py.sh] GUMP - [/usr/local/gump/test/gump] JAVA_HOME - [/usr/local/j2sdk1.4.2_04] HOME - [/home/gump] HOST_LOCAL_ENV - [local-env-py-brutus.sh] SSH_AUTH_SOCK - [/tmp/ssh-IHIAY31112/agent.31112] CLASSPATH - [/usr/local/j2sdk1.4.2_04/lib/tools.jar] _ - [/usr/bin/python] SSH_CONNECTION - [66.60.148.34 61041 209.237.227.198 22] SSH_TTY - [/dev/pts/1] GUMP_HOST - [brutus] PWD - [/usr/local/gump/test/gump] MAIL - [/var/mail/gump] GUMP_WORKSPACE - [python/gump/test/resources/full1/brutus] GUMP_WS - [/usr/local/gump/test/workspace] - GUMP base directory : /usr/local/gump/test/workspace - GUMP base path : /usr/local/gump/test/workspace - GUMP mail server: mail.apache.org - GUMP mail port : 25 - GUMP mail from : [EMAIL PROTECTED] - GUMP mail to: [EMAIL PROTECTED] - GUMP PYTHONPATH : /usr/local/gump/test/gump/python Execute : cvs -q update -dP out.txt 21 ? brutus.xml ? local-env-py-brutus.sh ? out.txt ? python/gump/test/resources/full1/brutus.xml Executing with CWD: [python] Execute : python gump/integrate.py -w ../python/gump/test/resources/full1/brutus.xml --xdocs out.txt 21 INFO:gump:Output xdocs (do not run forrest). Gump ~ Apache Python Gump (2.0.2-alpha-0004), a multi-project builder. ~ Copyright (C) 2003/2004 Apache Software Foundation. All rights reserved. See the Apache Software License 1.1 for more details. http://www.apache.org/ No project specified, please supply a comma separated list of project expressions or 'all'. Project wildcards are accepted, e.g. jakarta-*. Process Exit Code : 1 -- Gumpy Version: 2.0.2-alpha-0002 - 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]
live forrest webapp for Gump
http://brutus.apache.org:8080/gump/index.html Adam on [EMAIL PROTECTED]:/usr/local/gump/test/gump$ I changed the log dir setting to logdir=/home/gump/tomcat/webapps/gump but I had trouble starting it for --xdoc work. Give it a try when you get a chance. R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven/Gump Artefact/Jar Identifiers
Adam R. B. Jack wrote: Any input on this folks? Choices: jar id=commons-logging or: jar id=all artefactId=commons-logging Do we change our id's to be full artefact ids, or add separate? I think we bite the bullet and change our id's to be artefact ids (changing metadata as we need). Any thoughts? I think changing the ID is better than adding a new - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cron on brutus
Cron will usually mail results. So [EMAIL PROTECTED]:~$ cat .forward [EMAIL PROTECTED] [EMAIL PROTECTED]:~$ echo testing .forward |mail -stest gump 2004-05-06 12:43:34 Exim configuration error in line 8 of /var/lib/exim4/config.autogenerated: malformed macro definition Can't send mail: sendmail process failed with error code 1 [EMAIL PROTECTED]:~$ Any ideas what is wrong Adam R. B. Jack wrote: [EMAIL PROTECTED]:~$ crontab -l 30 3,9,12,15,21 * * * cd /usr/local/gump/public/gump; /bin/bash gumpy.sh /home/gump/CRON_DID_THIS I keep trying to set values to catch the clock (i.e. I set 30 12 at 12:25) but I can't see a /home/gump/CRON_DID_THIS. I started this 'cos I don't see any fresh Gump run since I made the edit. Do I have a typo, or mistake? Am I missing something? Thanks in advance, regards Adam -- Experience the Unwired Enterprise: http://www.sybase.com/unwiredenterprise Try Sybase: http://www.try.sybase.com - 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: Gump output
Stefan Bodewig wrote: On Thu, 29 Apr 2004, Adam R. B. Jack [EMAIL PROTECTED] wrote: If there is consensus against this, or if you feel strongly enough, I can easily take it out. No strong feelings, I simply liked the long lines better. How about wrapped on the tail, and unwrapped on the details Also consider using either the unix standard \ as the sumbol for the wrap or an icon of a carriage return, instead of the ... R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: gump/project ant.xml
Thanks, This will really lighten the load on my nightly gump. [EMAIL PROTECTED] wrote: bodewig 2004/04/28 00:50:11 Modified:project ant.xml Log: Reduce dependencies for ant-testutil Revision ChangesPath 1.16 +6 -3 gump/project/ant.xml Index: ant.xml === RCS file: /home/cvs/gump/project/ant.xml,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- ant.xml 26 Mar 2004 13:09:37 - 1.15 +++ ant.xml 28 Apr 2004 07:50:11 - 1.16 @@ -118,8 +118,10 @@ project name=ant-testutil ant target=test-jar/ -depend project=dist-ant inherit=all/ -option project=jakarta-tomcat-4.0 ids=jasper-compiler jasper-runtime/ +depend project=ant/ +depend project=junit/ +depend project=xml-xerces/ +depend project=xml-apis/ home nested=build/lib/ jar name=ant-testutil.jar id=ant-testutil/ @@ -135,7 +137,8 @@ property name=ant.home reference=home project=ant/ /ant -depend project=ant-testutil inherit=all/ +depend project=dist-ant inherit=all/ +option project=jakarta-tomcat-4.0 ids=jasper-compiler jasper-runtime/ option project=xml-commons-which/ option project=rhino/ option project=beanshell/ - 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: [RT] Improving on gump
Stefano Mazzocchi wrote: Stefan Bodewig wrote: sorry for the delay, I'm so behind my email it hurts! Crete was wonderful though ;-) It concerns me that people are very silent about this. Did I go to far? I love the idea, But I would implement it with out the emails first, Then add the emails one at a time. I am unsure of our abailbity to assign blame, that may be implied in some of the emails. R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Blog about BSD
It made it in the Board Report :-) I will post it for you later today. Stefan Bodewig wrote: On Tue, 20 Apr 2004, Nick Chalko [EMAIL PROTECTED] wrote: Can some one who knows the details, blog about this on Peas and Carrots. I've been the one who's written that. It looked to small to blog about it (and I still think it is). If we managed to get the IPv6 problem resolved on hermes that would really be cool and then I'd blog about it. Unfortunately I haven't found the time to follow-up on it yet. The issue that Gump found was that ant-contrib-cpptasks-test relied on the fact that any executable called link that could be found on the PATH had to be Microsoft's DevStudio Linker. Linux or SunOS usually don't have a link command while FreeBSD seems to have a form of ln using that name. Stefan - 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]
Peas and Carrots was: Gump status
Michael Davey wrote: Hi, The status page http://gump.apache.org/status.html is looking out of date. Perhaps the page could be replaced with a link to peas and carrots? Perhaps we should just move peas and carrots to Brutus and format it to look like a tab of the gump website. What is the boards opinion of running a blog on apache hardware ? R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Blog about BSD
The board reports http://wiki.apache.org/gump/Drafts_2fBoardReports_2f20040421 says Gump ran on FreeBSD (probably for the first time ever) and quickly uncovered a platform specific problem in one of the projects we build. Can some one who knows the details, blog about this on Peas and Carrots. R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@lsd]: depot/depot-version-antlet failed
Adam Jack wrote:
To whom it may engage...
snip/
Caused by: /data3/gump/ant/dist/tools/antlet/junit-0.1/xbuild.xml:24:
***
* A required jar was downloaded to /data3/gump/ant/dist/lib
* Please restart the build procedure.
***
*
* junit-3.8.1.jar was downloaded to /data3/gump/ant/dist/lib
*
***
Sorry about this.
The junit.antlet from antworks was a little over aggressive and forced
the download the junit jar.
I have fixed that antlet to only download the jar if the
junit.framework.TestCase is not found.
To download it to ${user.home}/.ant/lib not ${ant.home}/lib
And finally to only download and fail for a restart when junit is
actually called.
Can someone please delete
/data3/gump/ant/dist/lib/junit-3.8.1.jar
for me.
R,
Nick
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@lsd]: depot/depot-version-antlet failed
Adam R. B. Jack wrote: Sorry about this. The junit.antlet from antworks was a little over aggressive and forced the download the junit jar. [..] Can someone please delete /data3/gump/ant/dist/lib/junit-3.8.1.jar Won't Gump simply do it tonight when it synchronizes the ant working directory with ant CVS? Am I missing something? The dist dir is not part of CVS, so unless it cleans the dir first it will be left there - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
blog Re: [status] me and gump
Stephen McConnell wrote: Adam R. B. Jack wrote: 4) The 'root cause/resolution' for outage X/Y (between too parties) was Z. Log it/Blog it... ++1 If this was available I would definitely use it to post details about what is going on relative to the projects I'm associated with. Furthermore - it would provide an extra hint that there is someone somewhere dealing with a problem as opposed to waiting n days for a change in status - which is something I would find really valuable in terms of projects I'm dependent on. Gump has a blog called Peas and Carrots at http://gump.chalko.com/gb/blog/ Any one can add post by committing a file to CVS. at gump/blog/ Copy the file http://cvs.apache.org/viewcvs.cgi/gump/blog/Template.txt?view=markup and edit as needed. R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FOG 2.0 Proposal
Adam R. B. Jack wrote: Ok, so FOG as successes/(failures+prereqs) hasn't been a huge hit w/ folks, but what about: successes/(successes+failures+prereqs). This is really (if my math memory is ok) 'odds of a successful build, based off history' -- I think. This is far more valuable as a FOG Factor, because it is something bounded (0 to 1) and something we can do math with. I think 'likelihood of success' is good to know, but also if you combine it with 'likelihood of dependent success' (a multiplication of all direct dependencies) one gets a comparison of how precariously something sits on it's stack, and how much it contributes to success or failure. +1 I feel there is good information in there. We ought know (mathematically) that Forrest or Maven don't have a snowballs chance in heck of building, and it isn't their doing. We ought know what odds we are facing at a certain depth. It will be nice to have number to show this, so we consider alternatives to our current first fail pattern. R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Graph Gump?
Interesting that Gump was seen as a host, not a builder. We may need to think about how to word some of the pages. R, Nick Adam R. B. Jack wrote: Rowan wrote: I was recently alerted that you were hosting a commons-graph project. I would like to be part of this project if it is still happening, and if not possibly ressurrect it. I have been developing my own library for use with our project at www.cytoscape.org, but I would really like to see a bigger Open Source Java Graphing community. Please let me know if you have any more information, or whom I should contact. 1) Gump doesn't 'host' projects, it builds them. What you 'saw on Gump' was likely this output from a build. http://brutus.apache.org/gump/public/jakarta-commons-sandbox/commons-graph.html 2) From the looks of this you need to go looking in Jakarta, in the commons sub-project. http://jakarta.apache.org/commons/ (Note: SandBox means an experimental area, hence it is new to all of us here.) regards, Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Downloading Maven to brutus
curl ? Adam R. B. Jack wrote: Ok, I give. I'm used to using 'lynx' on Linux for a text based http, but that doesn't appear to be available on brutus. Does anybody know an alternative? I need to download this: http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-1.0-rc2.tar.gz or copy it between apache machines (probably smarter if I could figure out where it sits.) Can somebody help? regards Adam -- Experience the Unwired Enterprise: http://www.sybase.com/unwiredenterprise Try Sybase: http://www.try.sybase.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
CVS failed for jdom was: Speed of brutus
Note this cvs error http://brutus.apache.org/gump/public/jdom/gump_work/update_jdom.html can't create temporary directory /tmp/cvs-serv17931 No space left on device Sam Ruby wrote: I see from http://brutus.apache.org/gump/public/ Elapsed Time : 1 hour 56 mins 20 secs Putting it mildly, this doesn't look half bad. I presume that this includes the time of cvs/svn checkouts? Are the logs of the cvs/svn checkouts captured? This sometimes is helpful when trying to track down why a build that worked yesterday failed today. Note that this is only with one CPU and less than one gig of RAM. Looking at the build times, it looks to me like gump 2.0 tries to do parallel builds whenever possible? And finally, a nit: I see useful information like the name of the java command (java) and the Operating System (posix), but I don't see the values of System.getProperties which contains values such as: java.vm.version=1.4.2_04-b05 java.vm.vendor=Sun Microsystems Inc. os.arch=i386 os.name=Linux Are these available someplace? - Sam Ruby - 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: Gump Thrashing/Spinning...
Adam R. B. Jack wrote: BTW: I'm eager to see some graphics. If SVG can be written (in XML, viua Python) can Forrest convert these to images (using Batik or somethough?) I'll happily continue with Forrest if that is a good way to get images rendered. Yes Just put foo.svg and then access it as foo.png For example http://antworks.sourceforge.net/importer/images/project-logo.png Comes from ?xml version=1.0 encoding=Windows-1252? svg xmlns=http://www.w3.org/2000/svg; xmlns:xlink=http://www.w3.org/1999/xlink; viewBox=0 0 340 60 height=60 width=340 titleantworks-importer logo/title defslinearGradient y2=1 x2=0 y1=0 x1=0 id=gradientstop offset=0 style=stop-color:white/ stop offset=1 style=stop-color:lightgreen//linearGradient filter filterUnits=objectBoundingBox id=shadowFilter feGaussianBlur result=blur stdDeviation=2 2 in=SourceAlpha/ feOffset result=offsetBlur dy=4 dx=4 in=blur/ feComposite operator=over in2=offsetBlur in=SourceGraphic//filter/defs g fill=url(#gradient) filter=url(#shadowFilter) text style=font-size:32pt; font-family:Verdana ; text-anchor: middle y=50% x=45%Antworks Importer/text text style=font-size:10pt; font-family:Arial ; text-anchor: middle y=80% x=55%autdownload and import ant build.xml/text/g /svg Is generated by the forrest.antlet http://antworks.sourceforge.net/antlets/forrest/xbuild-doc.html from a module.xml R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@lsd]: jelly-tags/commons-jelly-tags-xmlunit failed
Wow Total time: 251 minutes 30 seconds Morgan Delagrange wrote: 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 [EMAIL PROTECTED] Project commons-jelly-tags-xmlunit has an issue affecting its community integration. The current state is 'Failed', for reason 'Build Timed Out' Full details are available at: http://lsd.student.utwente.nl/gump/jelly-tags/commons-jelly-tags-xmlunit.html, however some snippets follow: - - - - - -- -- G U M P Gump provided these annotations: - Info - Sole jar [/data3/gump/jelly-tags/xmlunit/target/commons-jelly-tags-xmlunit-20040327.jar] identifier set to project name - Error - Failed with reason build timed out - Info - Enable debug output, due to build failure. - - - - - -- -- G U M P Gump performed this work: Work Name: build_jelly-tags_commons-jelly-tags-xmlunit (Type: Build) State: Failed Elapsed: 1 hours, 4 minutes, 24 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/xml-apis.jar:/data3/gump/xml-xalan/java/build/xalan-unbundled.jar:/data3/gump/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/data3/gump/gump-install/work/merge.xml -Dbuild.sysclasspath=only -Dfinal.name=commons-jelly-tags-xmlunit-20040327 jar [Working Directory: /data3/gump/jelly-tags/xmlunit] - [mkdir] Created dir: /data3/gump/jelly-tags/xmlunit/target/classes [javac] Compiling 5 source files to /data3/gump/jelly-tags/xmlunit/target/classes [javac] /data3/gump/jelly-tags/xmlunit/src/java/org/apache/commons/jelly/tags/xmlunit/AssertDocumentsEqualTag.java:79: snip/ jar: [jar] Building jar: /data3/gump/jelly-tags/xmlunit/target/commons-jelly-tags-xmlunit-20040327.jar BUILD SUCCESSFUL Total time: 251 minutes 30 seconds - To subscribe to this information via syndicated feeds: RSS: http://lsd.student.utwente.nl/gump/jelly-tags/commons-jelly-tags-xmlunit.rss | Atom: http://lsd.student.utwente.nl/gump/jelly-tags/commons-jelly-tags-xmlunit.atom -- Gump http://gump.apache.org/ [lsd] - 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]
[RT] Let each project run using the last successfull jar from each dependency
Here is an idea to let gump build 100% every time. Keep the jars from the last success full build of each project. Then a project fails it will not stop the rest of the tree from building. Of course it becomse a little more complicated to know what jars were used for what. But I think we could keep track of that. Hmm almost like a gump repostory. R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: gump/blog/SuccessStories jrefactory.txt
Formating looks funny Take a look at http://gump.chalko.com/gb/blog/SuccessStories?preview=truesmm=ypermalink=jrefactory.txt And then release when it looks the way you want. [EMAIL PROTECTED] wrote: nickchalko2004/03/26 09:02:55 Modified:blog/SuccessStories jrefactory.txt Log: Changed to preview until the format is right. PR: Obtained from: Submitted by: Reviewed by: CVS: -- CVS: PR: CVS: If this change addresses a PR in the problem report tracking CVS: database, then enter the PR number(s) here. CVS: Obtained from: CVS: If this change has been taken from another system, such as NCSA, CVS: then name the system in this line, otherwise delete it. CVS: Submitted by: CVS: If this code has been contributed to Apache by someone else; i.e., CVS: they sent us a patch or a new module, then include their name/email CVS: address here. If this is your work then delete this line. CVS: Reviewed by: CVS: If we are doing pre-commit code reviews and someone else has CVS: reviewed your changes, include their name(s) here. CVS: If you have not had it reviewed then delete this line. Revision ChangesPath 1.2 +23 -4 gump/blog/SuccessStories/jrefactory.txt Index: jrefactory.txt === RCS file: /home/cvs/gump/blog/SuccessStories/jrefactory.txt,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- jrefactory.txt 26 Mar 2004 16:37:40 - 1.1 +++ jrefactory.txt 26 Mar 2004 17:02:55 - 1.2 @@ -1,13 +1,32 @@ -JRefactory adapt their code to changes in jaxen/saxpath +PREVIEW JRefactory adapt their code to changes in jaxen/saxpath -h1 +Preview at +http://gump.chalko.com/gb/blog/SuccessStories?preview=truesmm=ypermalink=jrefactory.txt +hr/ +!-- + Copyright 2004 The Apache Software Foundation + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- + +h3 issue of line ending with PrettyPrinter task -/h1 +/h3 I had found a problem with the PrettyPrinter task supplied by JRefactory. Without any clear announcement, the JRefactory team had changed their PrettyPrinter task to delegate processing of line endings to the ant fixcrlf task - which is good. - +more/ As a consequence, the acceptable values for the lineending setting of PrettyPrinter changed to become the one's of ant's fixcrlf task. - 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: cvs commit: gump/blog/SuccessStories jrefactory.txt
No problems, I did a little more formating, Whanged the I's to Antoine got the funny e to display ;-) And published. R, Nick Antoine Lévy-Lambert wrote: Nick, I am not familiar with writing blogs. You can further edit what I wrote. I hope that it will be OK at some stage. And now I am going to be offline, the week-end is beginning, and my kids would like to play on my PCs. Cheers, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RT] Gump Architecture
Leo Simons wrote: snip/ As for the buzzwords...let's create an action-based, data-centric, graph-based, versioning-enabled, highly componentized, extensible, continous integration system. I have no idea how to do any of that in python, but it sounds like fun to find out.. I had thought of using a event / black board system to support a distributed gump. Using something like javaspaces. A controller adds projects to a queue With information like * project name * cvs info including timestamp to use * List of dependencies * ant file / target The controller then walks through the project queue to find request that have all dependencies resolved and moves them to the a buildable queue Builders then get projects from the queue, and post the results which are ant output and jar files. When the controller has no more buildable projects it then posts the rest as dependency failures. This is a radically change but much more scalable. R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gump Thrashing/Spinning...
Stefano Mazzocchi wrote: Adam Jack wrote: Two possible solutions here: 1) use forrest as a dynamic application 2) have HTML generate by python I would go for 1) since it would keep us the ability to do dynamic stuff like metadata manipulation. I volunteer to setup 1) +1 for dynamic forrest. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fog factor
Stefano Mazzocchi wrote: We should design Gump keeping in mind that it should be silly to infer any judgement of quality out of the data. Our goal is not to measure, it's to help out the development process. Some people argue you can't improve what you can't measure. The counter point is whatever you measure you will improve, so make sure you measure the right thing. R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deprecating Traditional Gump
Stefano Mazzocchi wrote: Now that we have gump running on an apache machine Yeah http://moof.apache.org:8080/gump/ that will soon proxypassed from http://gump.apache.org/results/ I propose a few actions: 1) state loud and clear that the direction is Gumpy and retire traditional gump, this will help creating itches to scratch +1 2) refactor our CVS module: gump-traditional gump gump-data gump-1.0 gump-2.0 meta-data 3) stop calling it gumpy but rather start doing version numbering, so that would be Gump 2.0, when Gump 1.0 was traditional +1 4) add a cron job so that [EMAIL PROTECTED] becomes the official gump run. +1 thoughts? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: BATCH: All dressed up, with nowhere to go...
Change the wording to The following projects had failures but I don't know who to notify. I looked at the code, to modify it but it was unclear which line was for unwanted and which was for unsent. Adam R. B. Jack wrote: These are just the ones that don't have a nag entry, so don't have anywhere to be sent -- hence they return to the Gumpmeisters. I believe Nicola has plans for javasrc. regards Adam - Original Message - From: Stefano Mazzocchi [EMAIL PROTECTED] To: Gump code and data [EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 9:09 AM Subject: Re: BATCH: All dressed up, with nowhere to go... [EMAIL PROTECTED] wrote: Dear Gumpmeisters, The following 6 nags should have been sent G U M P [EMAIL PROTECTED]: webwork/webwork failed [EMAIL PROTECTED]: jakarta-tapestry/ognl failed [EMAIL PROTECTED]: javasrc/javasrc failed [EMAIL PROTECTED]: jetty/jetty failed [EMAIL PROTECTED]: xml-xerces/xml-xerces1 failed [EMAIL PROTECTED]: eyebrowse/eyebrowse failed is this all? you gotta be kidding! and what about the stuff at http://lsd.student.utwente.nl/gump/project_todos.html Ah, another thing, javasrc is failing, not used by anybody and hosted on sourceforge. Why are we building it? -- 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: [Cactus] Gump build failure: Culprit found!
I am preparing to blog this at http://gump.chalko.com/gb/blog/Issues/?smm=ypermalink=Cactus-CommonsHttpclient.txtpreview=true Please take moment and read to make sure I am staying friendly to both projects. I don't see this failure right now, can some one point me to the build failure. R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RT] Source difference report between 2 gump build states
Vincent Massol wrote: Hi, I have posted this idea under the thread [Cactus] Gump build failure: Culprit found! but I'm reposting it here as I'm not sure everyone will read the cactus stuff and I think this is an interesting idea... :-) Idea: It would be nice if Gump would be able to do a source diff of a project dependencies, and this between a successful run and a failed one. That would be s nice! A report page showing all the differences. There can't be that much in 1 day, right? Having this should save countless hours of debugging trying to figure out what is wrong. Wow great Idea. We have the necessary info from the timestamp on the CVS Looks like start time of cvs for a gump run should be store in the history data. Perhaps we should even be more explicit. We coulld record the official start time of the entier gump run and use that as the timestamp for ALL cvs updates. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Cactus] Gump build failure: Culprit found!
Updates made Vincent Massol wrote: -Original Message- From: Nick Chalko [mailto:[EMAIL PROTECTED] Sent: 15 March 2004 22:24 To: Gump code and data Subject: Re: [Cactus] Gump build failure: Culprit found! I am preparing to blog this at http://gump.chalko.com/gb/blog/Issues/?smm=ypermalink=Cactus- CommonsHttpclient.txtpreview=true Please take moment and read to make sure I am staying friendly to both projects. 2/ httpclient HEAD (i.e. v3.x) is not going to be backward compatible with v2.x and thus several APIs will be broken. The question has been asked on Cactus dev mailing list as to whether we stay on the 2.x branch or follow 3.x. Do you have a link to the actual email thread. I don't see it in the archive? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: gump/blog/Issues Struts-Velocity.txt
Stefano Mazzocchi wrote: Nick Chalko wrote: Is it premature to talk about this? http://gump.chalko.com/gb/blog/Issues/?smm=ypermalink=Struts-Velocity.txtpreview=true I like to keep the visibility up. but is the risk of stepping on toes to large? Reading it again I see that the people side of it came out harsh. I will make sure to use softer words in the future. I think that it's fine if you remove the compiler error and keep it focused on the social aspect of things. [that is Stuts and Velocity have to work together to solve the issue] I thought the compile error would be good for google and others facing the same issues. Given that I stepped on toes it is very important that we remeber to blog about the success. R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [head-up + vote] Gump should identify itself!!
Stefan Bodewig wrote: People, I propose that Gump should identify itself as Apache Gump rather than with the name of the person that onw the project. Fine with me, but Gump needs to use an address that is subscribed to the -dev list (or a benevolent moderator). We can use the pattern Gump @ Host [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Depot svn is failing on covalent.
http://gump.covalent.net/log/cvs_depot.html Any Ideas? R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Monthly clean of cvs dir.
Adam R. B. Jack wrote: I think we should to a month clean of the cvs dirs. a rm -rf . This will help us catch errors that outdated cvs dir would otherwise miss. The only negative I foresee with this, is that currently Gumpy uses the output of the CVS|SVN updates (in quiet mode) to determine if there have been any updates. A monthly clean would (as implemented today) throw this off: http://lsd.student.utwente.nl/gump/gump_stats/module_updated.html Now, since we are on the topic -- is there a better way to ascertain what updates occurred? I suspect we could check file dates/time stamps, but are there CVS|SVN ways? use cvs -n up to test for updates, then do delete the dirs and do a update. regards, Adam - 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: cvs commit: gump/blog/Issues Struts-Velocity.txt
Is it premature to talk about this? http://gump.chalko.com/gb/blog/Issues/?smm=ypermalink=Struts-Velocity.txtpreview=true I like to keep the visibility up. but is the risk of stepping on toes to large? R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Website
Lets finish the cleanup of the blog entry an release that also see http://gump.chalko.com/gb/blog/News/?permalink=TLP.txtpreview=truesmm=y Stefan Bodewig wrote: On Tue, 09 Mar 2004, Stefan Bodewig [EMAIL PROTECTED] wrote: With this, I think that we have all necessary content together to make gump.apache.org our official home page, done. Updated the site, changed links on Jakarta and www.apache.org and added a redirect on Jakarta. I've not removed the gump directory from the Jakarta site (yet), if you want to pick up anything from there, hurry up ;-) Stefan - 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]
TLP blog announcemt
Is http://gump.chalko.com/gb/blog/News/?permalink=TLP.txtpreview=truesmm=y ready for release. R, Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Website
Adam R. B. Jack wrote: I would like to see us considerd new content, news, perhaps reference to Peas-n-Carrots, Eventually I would like to see Peas-n-Carrots be a tab of the gump site. Like I did with http://nick.chalko.com - 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: Wanna join Gump : Development
krishnamoorthy wrote: Hi, I am interested to join in this development team.I checked the outstanding TODOS list and I am interested to invole in this team.Let me know if I could do something.Btw I do't know Python.I am from J2EE/Java background. Great to have you. First step get gumpy to run on your local machine. after that ( and that may take some time). Jump in and make improvements. and send them in as a patch. regds Kicha __ Do you Yahoo!? Get better spam protection with Yahoo! Mail. http://antispam.yahoo.com/tools - 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: All dressed up, with nowhere to go...
[EMAIL PROTECTED] wrote: [EMAIL PROTECTED]: webwork/webwork failed To whom it may engage... I don't quit get the Subject line here. shouldn't it at least say webwork is all dressed up, with nowhere to go... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unable to send...
Why are we Unable to send... [EMAIL PROTECTED] wrote: [EMAIL PROTECTED]: logging-log4j/log4j-tests 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 [EMAIL PROTECTED] Project log4j-tests has an issue affecting it's community integration, and has been outstanding for 16 runs. The current state is 'Failed', for reason 'Build Failed' Full details are available at: http://lsd.student.utwente.nl/gump/logging-log4j/log4j-tests.html, however some snippets follow: - - - - - -- -- G U M P Gump provided these annotations: - Info - Made directory [/data3/gump/logging-log4j/tests/classes] - Error - Failed with reason build failed - - - - - -- -- G U M P Gump performed this work: Work Name: build_logging-log4j_log4j-tests (Type: Build) State: Failed Elapsed: 0 hours, 0 minutes, 9 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 -Dgump.merge=/data3/gump/gump-install/work/merge.xml -Dbuild.sysclasspath=only regression [Working Directory: /data3/gump/logging-log4j/tests] - build.xml: javamailCheck: javamail: build.javamail: jmsCheck: jms: jndiCheck: jndi: [echo] JNDI is present. build.jms: jmxCheck: jmx: build.jmx: avalonFrameworkCheck: avalonFramework: build.avalonFramework: build: prepare: [mkdir] Created dir: /data3/gump/logging-log4j/tests/output build: [javac] Compiling 61 source files to /data3/gump/logging-log4j/tests/classes [javac] /data3/gump/logging-log4j/tests/src/java/org/apache/log4j/chainsaw/receivers/ReceiversHelperTest.java:31: cannot resolve symbol [javac] symbol : variable ReceiversHelper [javac] location: class org.apache.log4j.chainsaw.receivers.ReceiversHelperTest [javac] List list = ReceiversHelper.getInstance().getKnownReceiverClasses(); [javac] ^ [javac] 1 error BUILD FAILED /data3/gump/logging-log4j/tests/build.xml:80: Compile failed; see the compiler error output for details. Total time: 8 seconds - To subscribe to this information via syndicated feeds: RSS: http://lsd.student.utwente.nl/gump/logging-log4j/log4j-tests.rss | Atom: http://lsd.student.utwente.nl/gump/logging-log4j/log4j-tests.atom -- Gump http://gump.apache.org/ [lsd] - 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]
