Re: [VOTE] retire java gump
+1 I'd rather try to find the time to understand Gumpy in order to implement the things missing (javadoc for example). Playing catch-up with Gumpy isn't fun and nothing should stop Gumpy to go into ways that Java Gump won't follow fast enough. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PROPOSAL: SAX+xmlutils - xml.dom.minidom
Adam R. B. Jack wrote: I just can't seem to deal with the code that Sam originally wrote for parsing/merging XML. ... I can't fix the bugs that are there, I can't extend it without make more bugs, 'odd stuff' happens. This is a problem with all of us that would want to work on Gump. There are many developers that want to put their hands on it, and are stopped by a high entry barrier. Anything to lower this will benefit Gump immensly. We can always come back later to Sam's design at a later date, who knows :-) -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PROPOSAL: SAX+xmlutils - xml.dom.minidom
Adam, since you seem to be the only one actively working on it, just do what makes live easier for you IMHO. It may make life easier for other non-Python folks around here as well, once/if they find time to contribute. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RT] Gump service
Adam R. B. Jack wrote: [snip] Server component to look at the projects and work out which ones Gump needs to try to build next. To start off, the algorithm stays as it is now. In future we can look to detect if there have been CVS commits since last build and so on. Server component puts n work pieces into a pool. [snip] Service/Client component takes one project out of the pool, performs cvs update and attempts to build (again using the current algorithm). Puts the results into a second pool. I've been thinking about this, but for threads. I recently split Gump into pieces with some for of listener event/request pattern, so we could dispatch to unnamed parties. I reworked a 'runner' so we could have various types, my goal is one that take 'next available module or project' from a list, so we can have multiple concurrent threads working it. View component takes the results from the second pool and produces the web site. Alternatively, the second pool could be replaced with a filestore and the view generates the pages on the fly from the filestore. The view component is forrest with a little glue logic. I agree, something (lower priority?) could be building a WWW site at the same time that real biulds are going on. I keep thinking we could serialize the context (the build information) to a file, but I like having lots of information haven't found time to serialzie it all. The nice thing about this is that it opens up many more possibilities for the future. For instance, it would enable distributed gump at the client component. Yup, very nice. My personal goals are for cascading gumps, then multi-threaded (to make use of the two CPUs on Brutus), and one day, distributed. Thanks for the thoughts. Now, how do we make the incremental progress to get there? I'll respond as no one else has yet. I am very new to Python - I can play about with simple things like checking of executables but pretty much anything else is beyond me, so I am unlikely to be able to help with coding for this. That said... You said that you have recently split Gump up into pieces using an event/listener pattern. I infer that the listener works across the equivalent of my proposed server/client interface but you don't have an equivalent between client and view. The steps would seem to be: 1a. Find a way of describing a piece of work to the client (a 'type' as you put it - a project or module). For the moment, I think we can assume that server and client have a consistent view of the metadata, so just the module or project name should suffice for the moment. 1b. Rework the runner to work over some form of sockets. The client will request a piece of work, the server will describe the piece of work as per [1a] above and mark it as checked out to the client (simply remove the work piece from its list in the initial implementation). When the server runs out of work pieces, it starts again from the beginning. 2a. Find a way of describing the results of a build. We need to decide whether only the log files are to be supplied; log files and location of the build on the client (assuming it is public access); or log files plus the actual build. 2b. The client will contact the view and supply the results of the build as per [2a] above and the view will acknowledge receipt. 2c. Rework the view to understand how to process the results from the client. The actual sockets layer could be implemented using ftp, http, svn or our own protocol. Later we can add a feedback loop from view to server to let the server know that the client has supplied the results and make the mechanism more bulletproof by timing out a client if it doesn't supply the results in a timely manner (so the work piece can be supplied to a different client). We could also send the work out to multiple clients to ensure they agree upon the results. -- Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] retire java gump
Stefan Bodewig wrote: +1 I'd rather try to find the time to understand Gumpy in order to implement the things missing (javadoc for example). Playing catch-up with Gumpy isn't fun and nothing should stop Gumpy to go into ways that Java Gump won't follow fast enough. +1 -- Stefano. smime.p7s Description: S/MIME Cryptographic Signature
[Gump Wiki] Updated: FrontPage
Date: 2004-06-09T05:51:24 Editor: 65.230.28.226 Wiki: Gump Wiki Page: FrontPage URL: http://wiki.apache.org/gump/FrontPage Artefact - Artifact Change Log: -- @@ -35,7 +35,7 @@ '''HistoricalResultsDatabase''' - '''ArtefactsRepository''' + '''ArtifactRepository''' '''ImaginaryUsers''' Some imaginary user profiles for gump. For whom are we building this thing? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Gump Wiki] New: ArtifactRepository
Date: 2004-06-09T05:53:07 Editor: 65.230.28.226 Wiki: Gump Wiki Page: ArtifactRepository URL: http://wiki.apache.org/gump/ArtifactRepository no comment New Page: = Artifact Repository = /!\ '''WORK IN PROGRESS''' /!\ /!\ '''WORK IN PROGRESS''' /!\ /!\ '''WORK IN PROGRESS''' /!\ /!\ '''WORK IN PROGRESS''' /!\ Please don't waste your time reading this... *yet* I am saving this regularly (and working on it in background) 'cos when I went to go get HelpOnFormatting the brower window chosen was this one, and despite attempts to be back/reload, I lost my in-memory edits. /!\ '''WORK IN PROGRESS''' /!\ /!\ '''WORK IN PROGRESS''' /!\ /!\ '''WORK IN PROGRESS''' /!\ /!\ '''WORK IN PROGRESS''' /!\ == Overview == Gump generates and consumes artifacts. Providing access to the artefact repository that Gump produces has a number of benefits. Providing Gump with access to alternate artifact repositories (not just it's packaged projects area) has yet more. == Gump Artifact Repository == Gump currently generates artefacts and stores them in a hierarchical directory structure, ala ASF Repository Format (more Maven Repository Format w/o the .MD5s 'yet'). These artifacts can be made available online, and become available for cascading Gumps to download. == Gump Accessing Artifacts == Gump currently takes packages from it's local repository of installed packages. This is a manually maintained 'repository', with manual metadata changes made to poitn to these entries. === Metadata === Gump recognized CVS and SVN repositories (that contain source code/projects). Adding a third 'Artifact' repository is proposed: === Depot === [http://incubator.apache.org/depot Apache Depot] has one tool for downloading artifacts. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Gump Wiki] Updated: ArtefactsRepository
Nothing much, and as Leo said, that can be hard to change. In this case, only as hard as a few people finding/stating it gets in their way. Consistency is key for ASF processing artifacts automatically. Changed. :) regards, Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jira and Gump (Re: Fw: brutus)
pretty OT, no? :-D. Some yacka-di-yack below. Jeff Turner wrote: On Tue, Jun 08, 2004 at 08:59:17AM -0600, Adam R. B. Jack wrote: I can do it, esp if people can be disciplined about using jira (toomuchemail). I couldn't agree more. JIRA has to help us smooth out the inflow. delurk Can you elaborate on this? I'm rewriting JIRA's email templates at the moment, so am interested in that general area.. one of the key advantages is that with jira the email it sends you is always (well, one would hope anyway) laid out the same way. Just like with a gump nag e-mail, you know the structure is always the same. When gump sends an issue fixed e-mail (was that implemented?) you can mark the message read based on the subject. You can also filter and search e-mail that comes from a bot more easily. With some issues, I can fix them as I see the request come in or assigned to me, and forget about them (what's missing is of course being able to mark the changes from my e-mail program; for example a write gump success story button that appears when I'm reading e-mail about gump; chandler's interesting). With others, I can forget about them right away and be sure I can still find them when I log into my dashboard. I think lots and lots of research actually exists about information overload. Once you build up an e-mail backlog, your inbox keeps just piling up and up and up. With jira, you know you can just mark a message read without reading it, since its possible to find that information later on through the web. Gump, jira, etc, view 'em as tools for the overworked knowledge worker to deal with information flow. Anything which allows me to hit 'M' (mark as read) a split second earlier and forget about a message is progress! If you were to improve things along these linesfor example, jira ought to have the resolution in the subject line when an issue is resolved, since FIXED means I can forget about things immediately whilst WONTFIX might be a bigger problem. cheers, - LSD - 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]: ant-contrib/ant-contrib-test failed *** G U M P [EMAIL PROTECTED]: ant-contrib/ant-contrib-test failed 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 ant-contrib-test has an issue affecting its community integration. Project State : 'Failed', Reason 'Build Failed' Full details are available at: http://brutus.apache.org:8080/gump/ant-contrib/ant-contrib-test/index.html That said, some snippets follow: The following annotations were provided: -INFO- Made directory [/usr/local/gump/public/workspace/ant-contrib/test/classes] -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/ant-contrib/ant-contrib-test/gump_work/build_ant-contrib_ant-contrib-test.html Work Name: build_ant-contrib_ant-contrib-test (Type: Build) State: Failed Elapsed: 0 hours, 0 minutes, 26 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=20040609 test [Working Directory: /usr/local/gump/public/workspace/ant-contrib] CLASSPATH : /usr/local/j2sdk1.4.2_04/lib/tools.jar:/usr/local/gump/public/workspace/ant-contrib/test/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-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/ant/build/lib/ant-testutil.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-20040609.jar- [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 2.064 sec [junit] Testcase: test1(net.sf.antcontrib.process.LimitTest): Caused an ERROR [junit] java.lang.NullPointerException [junit] /usr/local/gump/public/workspace/ant-contrib/test/resources/logic/limittest.xml:16: java.lang.NullPointerException [junit] at net.sf.antcontrib.process.Limit.execute(Limit.java:313) [junit] at net.sf.antcontrib.BuildFileTestBase.expectLogNotContaining(BuildFileTestBase.java:60) [junit] at net.sf.antcontrib.process.LimitTest.test1(LimitTest.java:31) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] Caused by: java.lang.NullPointerException [junit] at net.sf.antcontrib.process.Limit.execute(Limit.java:290) [junit] ... 35 more [junit] --- Nested Exception --- [junit] java.lang.NullPointerException [junit] at net.sf.antcontrib.process.Limit.execute(Limit.java:290) [junit] at net.sf.antcontrib.BuildFileTestBase.expectLogNotContaining(BuildFileTestBase.java:60) [junit] at net.sf.antcontrib.process.LimitTest.test1(LimitTest.java:31) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] Test net.sf.antcontrib.process.LimitTest FAILED [junit] Testsuite: net.sf.antcontrib.property.MathTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.029 sec [junit] Testsuite: net.sf.antcontrib.property.PathToFileSetTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.094 sec [junit] Testsuite: net.sf.antcontrib.property.PropertyCopyTest [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.069 sec [junit] Testsuite: net.sf.antcontrib.property.PropertySelectorTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.063 sec [junit] Testsuite: net.sf.antcontrib.property.VariableTest [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 0.152 sec [junit] Testsuite
Re: BATCH: Unable to send...
On 09 Jun 04, [EMAIL PROTECTED] wrote: The following 1 notifys should have been sent *** G U M P [EMAIL PROTECTED]: ant-contrib/ant-contrib-test failed Any indication why brutus failed to send the mail? Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: BATCH: Unable to send...
On Wed, 9 Jun 2004, Adam R. B. Jack [EMAIL PROTECTED] wrote: We seeem to be getting sparodic timeouts to mail.apache.org Sure it is a timeout? The ant-contrib nags do not come from an apache.org sender so I suspected a no-relay rule kicking in. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: BATCH: Unable to send...
On Wed, 9 Jun 2004, Adam R. B. Jack [EMAIL PROTECTED] wrote: We seeem to be getting sparodic timeouts to mail.apache.org Sure it is a timeout? The ant-contrib nags do not come from an apache.org sender so I suspected a no-relay rule kicking in. It is oddly coincidental that we get the no-send notify, but not the original. That said, we do get: error: (110, 'Connection timed out') -- and maybe the first failure allows the second to work, for timing issues. I don't know. I hate to bug infr@ these days, but I guess we ought add a JIRA entry to investigate. regards, Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jira and Gump (Re: Fw: brutus)
I couldn't agree more. JIRA has to help us smooth out the inflow.
delurk
Can you elaborate on this? I'm rewriting JIRA's email templates at the
moment, so am interested in that general area..
I don't think I was meaning anything more perceptive than JIRA is a good
TODOs list, but I have felt swamped with Gump TODOs recently (we have too
many fun ideas I'd love to find time to do) and I've overstretched my
abilities, and felt overwhelmed. [At least, before I took some days off.
:) ] Basically, JIRA *ought* (if we use discipline) be the repository for
prioritised TODOs, and our 'intray' for tasks. I really ought not do
anything other than what it in JIRA. I need to get that discipline, and I
think the public sharing of tasks/to-dos would be in keeping w/ OSS
principles/benefits.
BTW: I'd kinda like to see 'nag e-mails' from JIRA. Like: this task has
been waiting a significant time, please either complete it, or assign it to
the pool, or somebody else. Along with that (and for what we'd like here)
we'd like a different group of potential worker per sub-component (in this
case managing the Gump hardware). It'd be nice to have nags to the group
about things sitting in a pool for them.
If we all would read our JIRA dashboard each day we'd not need this, but
that is like expecting folks to read their Gump WWW page each day. Not
feasible. I think in the distributed world of open source nobody has time to
read any WWW site ('cos there are always N). As such , nags e-mails or
RSS/Atom...
regards,
Adam
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: gump/python/gump/test/resources/full1 artifact_repository1.xml download1.xml profile.xml artefact_repository1.xml
ajack 2004/06/09 12:28:45
Modified:.Tag: CleanUp gumpy.py
python/gump/core Tag: CleanUp gumprun.py gumpinit.py
python/gump/model Tag: CleanUp module.py workspace.py
object.py property.py rawmodel.py repository.py
python/gump/utils Tag: CleanUp http.py work.py __init__.py
python/gump/test/resources/complete1 Tag: CleanUp
profile.xml download1.xml
python/gump/update Tag: CleanUp updater.py
python/gump/repository Tag: CleanUp artefact.py
python/gump/test/resources/full1 Tag: CleanUp download1.xml
profile.xml
Added: python/gump/utils Tag: CleanUp timing.py tasks.py
python/gump/test/resources/complete1 Tag: CleanUp
artifact_repository1.xml
python/gump/update Tag: CleanUp artifact.py
python/gump/loader Tag: CleanUp loader.py __init__.py
.cvsignore
python/gump/test/resources/full1 Tag: CleanUp
artifact_repository1.xml
Removed: python/gump/test/resources/complete1 Tag: CleanUp
artefact_repository1.xml
python/gump/update Tag: CleanUp artefact.py
python/gump/test/resources/full1 Tag: CleanUp
artefact_repository1.xml
Log:
Lightening commit...
1) Artefact - Artifact
2) SAX/xmlutils - DOM (start of)
3) Some work on tasks/timestamps
Revision ChangesPath
No revision
No revision
1.37.2.1 +4 -1 gump/gumpy.py
Index: gumpy.py
===
RCS file: /home/cvs/gump/gumpy.py,v
retrieving revision 1.37
retrieving revision 1.37.2.1
diff -u -r1.37 -r1.37.2.1
--- gumpy.py 27 May 2004 14:35:28 - 1.37
+++ gumpy.py 9 Jun 2004 19:28:44 - 1.37.2.1
@@ -359,6 +359,8 @@
log.write('- GUMP mail to: ' + mailto + '\n')
if logurl:
log.write('- GUMP log is @ : ' + logurl + '\n')
+if logdir:
+log.write('- GUMP log is @ : ' + logdir + '\n')
#
# Add Gump to Python Path...
@@ -447,7 +449,8 @@
catFile(publishedLog, logFile, logTitle)
publishedLog.close()
published=1
-except:
+except Exception, detauls:
+print 'Failed to publish log file. ', str(details)
published=0
else:
print 'Unable to publish log file.'
No revision
No revision
1.9.2.2 +2 -2 gump/python/gump/core/gumprun.py
Index: gumprun.py
===
RCS file: /home/cvs/gump/python/gump/core/gumprun.py,v
retrieving revision 1.9.2.1
retrieving revision 1.9.2.2
diff -u -r1.9.2.1 -r1.9.2.2
--- gumprun.py8 Jun 2004 21:36:37 - 1.9.2.1
+++ gumprun.py9 Jun 2004 19:28:44 - 1.9.2.2
@@ -616,8 +616,8 @@
#
# A repository interface...
#
-from gump.repository.artefact import ArtefactRepository
-self.outputsRepository=ArtefactRepository(workspace.jardir)
+from gump.repository.artifact import ArtifactRepository
+self.outputsRepository=ArtifactRepository(workspace.jardir)
# Generate a GUID (or close)
import md5
1.3.2.1 +3 -3 gump/python/gump/core/gumpinit.py
Index: gumpinit.py
===
RCS file: /home/cvs/gump/python/gump/core/gumpinit.py,v
retrieving revision 1.3
retrieving revision 1.3.2.1
diff -u -r1.3 -r1.3.2.1
--- gumpinit.py 21 May 2004 23:15:02 - 1.3
+++ gumpinit.py 9 Jun 2004 19:28:44 - 1.3.2.1
@@ -36,10 +36,10 @@
###
# Initialize
###
-def gumpinit():
+def gumpinit(level=None):
#set verbosity to show all messages of severity = default.logLevel
-log.setLevel(default.logLevel)
+log.setLevel(level or default.logLevel)
# Ensure dirs exists,
basicConfig()
No revision
No revision
1.45.2.2 +7 -7 gump/python/gump/model/module.py
Index: module.py
===
RCS file: /home/cvs/gump/python/gump/model/module.py,v
retrieving revision 1.45.2.1
retrieving revision 1.45.2.2
diff -u -r1.45.2.1 -r1.45.2.2
--- module.py 8 Jun 2004 21:36:35 -
Re: [Gump Wiki] Updated: ArtefactsRepository
Don't wast too much time on changing it, I just thought it was incorrect spelling, but now I heard it is correct spelling, I am happy with it:) Mvgr, Martin On Wed, 2004-06-09 at 14:54, Adam R. B. Jack wrote: Nothing much, and as Leo said, that can be hard to change. In this case, only as hard as a few people finding/stating it gets in their way. Consistency is key for ASF processing artifacts automatically. Changed. :) regards, Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Gump Wiki] Updated: SolarisConfig
Date: 2004-06-09T15:58:47
Editor: 217.42.133.87
Wiki: Gump Wiki
Page: SolarisConfig
URL: http://wiki.apache.org/gump/SolarisConfig
no comment
Change Log:
--
@@ -11,11 +11,11 @@
http://www.activestate.com/Products/ActivePython/
- Apache webserver from the SunFreeware disk or from http://apache.org/
+ Apache webserver from the SunFreeware disk, http://sunfreeware.com/ website or
from http://apache.org/
- CVS from the SunFreeware disk or from http://cvshome.org/
+ CVS from the SunFreeware disk, http://sunfreeware.com/ website or from
http://cvshome.org/ . You'll need version 1.11.6 or better - 1.11 (supplied with some
versions of Solaris) does not correctly recognise the port number as part of the
CVSROOT or -d option.
- subversion from the SunFreeware disk or from http://subversion.org/
+ subversion from the SunFreeware disk, http://sunfreeware.com/ website or from
http://subversion.org/
If your server does not have a graphics card, you will also need to install Xvfb
from the SunFreeware disk
@@ -43,6 +43,7 @@
* '''Note''': FORREST_HOME will be exported and added to the PATH in step 4
* Apache Maven:
+(version 1.0-rc1 or better - 1.0-beta-8 generates an error if --version is called
when no project file is present, causing Gump to think that Maven is not present)
* {{{cd /usr/local}}}
* Download [http://maven.apache.org/start/download.html Maven] to /tmp (select
.tar.gz format)
* {{{tar -xzf /tmp/maven-1.0-rc2.tar.gz}}}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
BATCH: Unable to send...
Dear Gumpmeisters, The following 5 notifys should have been sent *** G U M P [EMAIL PROTECTED]: checkstyle/checkstyle-test failed [EMAIL PROTECTED]: ant-contrib/ant-contrib-test success [EMAIL PROTECTED]: cocoon-2.1/cocoon-block-scratchpad failed [EMAIL PROTECTED]: incubator-geronimo/incubator-geronimo failed [EMAIL PROTECTED]: jaxen/jaxen-test failed *** G U M P [EMAIL PROTECTED]: checkstyle/checkstyle-test failed 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 checkstyle-test has an issue affecting its community integration, and has been outstanding for 5 runs. Project State : 'Failed', Reason 'Build Failed' Full details are available at: http://brutus.apache.org:8080/gump/checkstyle/checkstyle-test/index.html That said, some snippets follow: The following annotations were provided: -INFO- Enable verbose output, due to 4 previous error(s). -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/checkstyle/checkstyle-test/gump_work/build_checkstyle_checkstyle-test.html Work Name: build_checkstyle_checkstyle-test (Type: Build) State: Failed Elapsed: 0 hours, 2 minutes, 29 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 -verbose -Dgump.merge=/usr/local/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=20040609 gump.setup run.tests [Working Directory: /usr/local/gump/public/workspace/checkstyle] CLASSPATH : /usr/local/j2sdk1.4.2_04/lib/tools.jar:/usr/local/gump/public/workspace/checkstyle/target/checkstyle:/usr/local/gump/public/workspace/checkstyle/target/tests:/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/checkstyle/target/dist/checkstyle-20040609/checkstyle-20040609.jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local/gump/public/workspace/jakarta-regexp/build/jakarta-regexp-20040609.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-20040609.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-20040609.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jdom/build/jdom.jar:/usr/local/gump/public/workspace/jakarta-velocity/bin/velocity-20040609.jar:/usr/local/gump/public/workspace/avalon-logkit/target/avalon-logkit-20040609.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar- [junitreport] Parsing file: '/usr/local/gump/public/workspace/checkstyle/target/testreports/TEST-com.puppycrawl.tools.checkstyle.checks.naming.ParameterNameCheckTest.xml' [junitreport] Parsing file: '/usr/local/gump/public/workspace/checkstyle/target/testreports/TEST-com.puppycrawl.tools.checkstyle.checks.naming.StaticVariableNameCheckTest.xml' [junitreport] Parsing file: '/usr/local/gump/public/workspace/checkstyle/target/testreports/TEST-com.puppycrawl.tools.checkstyle.checks.naming.TypeNameCheckTest.xml' [junitreport] Parsing file: '/usr/local/gump/public/workspace/checkstyle/target/testreports/TEST-com.puppycrawl.tools.checkstyle.checks.sizes.AnonInnerLengthCheckTest.xml' [junitreport] Parsing file: '/usr/local/gump/public/workspace/checkstyle/target/testreports/TEST-com.puppycrawl.tools.checkstyle.checks.sizes.ExecutableStatementCountCheckTest.xml' [junitreport] Parsing file: '/usr/local/gump/public/workspace/checkstyle/target/testreports/TEST-com.puppycrawl.tools.checkstyle.checks.sizes.FileLengthCheckTest.xml' [junitreport] Parsing file: '/usr/local/gump/public/workspace/checkstyle/target/testreports/TEST-com.puppycrawl.tools.checkstyle.checks.sizes.LineLengthCheckTest.xml' [junitreport] Parsing file: '/usr
[Gump Wiki] Updated: GumpInfrastructure
Date: 2004-06-09T16:12:31 Editor: 80.176.146.62 Wiki: Gump Wiki Page: GumpInfrastructure URL: http://wiki.apache.org/gump/GumpInfrastructure no comment Change Log: -- @@ -8,7 +8,7 @@ == Gump on brutus.apache.org == -See http://brutus.apache.org/gump/public. See BrutusConfig +See http://brutus.apache.org:8080/gump/index.html. See BrutusConfig == Gump on moof.apache.org == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: BATCH: Unable to send...
[EMAIL PROTECTED] wrote: Dear Gumpmeisters, The following 5 notifys should have been sent *** G U M P [EMAIL PROTECTED]: checkstyle/checkstyle-test failed [EMAIL PROTECTED]: ant-contrib/ant-contrib-test success [EMAIL PROTECTED]: cocoon-2.1/cocoon-block-scratchpad failed [EMAIL PROTECTED]: incubator-geronimo/incubator-geronimo failed [EMAIL PROTECTED]: jaxen/jaxen-test failed *** G U M P [snip] Is it possible to include the email headers (at least to, from, date subject) in the Unable to send digest mails? This would make debugging of failures somewhat easier. Cheers, -- Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] retire java gump
- Original Message - From: Michael Davey [EMAIL PROTECTED] To: Gump code and data [EMAIL PROTECTED] Sent: Tuesday, June 08, 2004 5:07 PM Subject: Re: [VOTE] retire java gump Leo Simons wrote: Hi gang! And now for something completely different... Saw both Adam and Stefan suggest this recently. I concur. Let's retire (kill off sounds way to harsh for this faithful servant!) the java version of gump. The python one is now superior in most ways, and Adam keeps getting a headache keeping all the undocumented awkwardness in sync! +0. -0 (if that's allowed) But -1 if the proposal is to stop non-Python Gumps at present. I'd suggest tagging CVS and making it clear that java gump may deviate from documentation, etc but permit changes to the code. My main concern +1 As far as I can see, the Python Gumps are currently in the minority, so it makes sense to allow the Java Gumps to continue. The more, the merrier, as there's then more chance that the inevitable installation differences will help find subtle build problems. Also, none of the Python Gumps seem to make any generated jars available, even if they are redistributable. S. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: BATCH: Unable to send...
Is it possible to include the email headers (at least to, from, date
subject) in the Unable to send digest mails? This would make
debugging of failures somewhat easier.
The code base I have here pretty much does that, plus reason for failure.
Unfortunately I went on this DOM chase w/ the code in this branch, so can't
commit yet.
Mind you, for now, go look at the project details:
http://brutus.apache.org:8080/gump/checkstyle/checkstyle-test/index.html#Details
a.. Notify To: [EMAIL PROTECTED]
a.. Notify From: Conor MacNeill [EMAIL PROTECTED]
a.. Notification E-mail: Contents
http://brutus.apache.org:8080/gump/checkstyle/checkstyle-test/checkstyle-test_notify.html
---
-
BTW:
The script gumpy.py copies it's log to the log directory, unfortunately with
the webapp it ought be in a sub-directory called content. I moved it here,
for now:
http://brutus.apache.org:8080/gump/gumpy_log.txt
It'll stay only until next run completes.
Looking at it now, I do see evidence of Stefan's concern:
Apache Gump
http://gump.apache.org/ [Instance: brutus]
Traceback (most recent call last):
File /usr/local/gump/public/gump/python/gump/net/smtp.py, line 103, in
mail
failures = server.sendmail(sane_fromaddr, sane_toaddrs, data)
File /usr/lib/python2.3/smtplib.py, line 687, in sendmail
raise SMTPRecipientsRefused(senderrs)
SMTPRecipientsRefused: {'[EMAIL PROTECTED]': (550, 'Invalid
To: Address')}
ERROR:gump:Server :smtplib.SMTP instance at 0x41d7fd0c From :Conor
MacNeill [EMAIL PROTECTED] To :['[EMAIL PROTECTED]']
ERROR:gump:Failed with to: [EMAIL PROTECTED] from: [Conor
MacNeill [EMAIL PROTECTED]]
Traceback (most recent call last):
File /usr/local/gump/public/gump/python/gump/net/smtp.py, line 103, in
mail
failures = server.sendmail(sane_fromaddr, sane_toaddrs, data)
File /usr/lib/python2.3/smtplib.py, line 687, in sendmail
raise SMTPRecipientsRefused(senderrs)
SMTPRecipientsRefused: {'[EMAIL PROTECTED]':
(550, 'Invalid To: Address')}
ERROR:gump:Server :smtplib.SMTP instance at 0x41d7fd0c From :Stefan
Bodewig [EMAIL PROTECTED] To
:['[EMAIL PROTECTED]']
ERROR:gump:Failed with to: [EMAIL PROTECTED]
from: [Stefan Bodewig [EMAIL PROTECTED]
This is slightly different, they've not qualified it...
INFO:gump:Notify for project: spark
INFO:gump:Notify for project: cocoon-block-scratchpad
INFO:gump:Send Notify e-mail:
To: [EMAIL PROTECTED]
From: Gump
Subject: [EMAIL PROTECTED]: cocoon-2.1/cocoon-block-scratchpad failed
ERROR:gump:Failed to send e-mail: (450, 'FQDN required in the envelope
sender', 'Gump')
ERROR:gump:Date: 09 Jun 04 23:08:56
From: Gump
To: [EMAIL PROTECTED]
This looks like a typo, inco not incu...
ERROR:gump:Failed to send e-mail: {'[EMAIL PROTECTED]':
(550, 'relaying denied')}
ERROR:gump:Date: 09 Jun 04 23:09:00
From: Davanum Srinivas [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [EMAIL PROTECTED]: incubator-geronimo/incubator-geronimo failed
regards,
Adam
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
