From this thread:
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]by=threadfrom=667384
.. here are my thoughts, (for what they are worth).
Stefano has convinced me that pure numbers are not the most erudite form of
communication, are equivocable (folks will hate the algorythms) and
I've been wondering why the LSD 'log' at :
http://lsd.student.utwente.nl/gump/gumpy.html
has been so terse unhelpful, and the forrest pages stale.
On LSD we still use gumpy.sh (because gumpy.py isn't ready for prime time)
and one difference between those two is that gumpy.sh write to
Gump didn't run last night on LSD. I can't really figure out why
right now.
I think it has been caused by the circular dependency between two
jicarilla projects (that I've just removed by commenting out jicarilla
in the Gump descriptor).[1]
Unlike Jenny, GUMPY doesn't detect the cycle
I currently don't understand why Gump on LSD thinks Cocoon would
depend on avalon-fortress-container, but the Gump instance on
covalent.net tries to build it[1].
I wonder if the removal of the 'full dependencies' and 'full dependees'
tables (on 'working projects') is a good thing or not. It
Gump is a social experiment, and this part of the experiment has shown
to be a negative and annoying factor. I feel that my own recent
experiences with jicarilla are an excellent example: even with an active
and experienced member of the core gump group trying to actively
maintain gump
if I would like to replace the use of ls and cat in gumpy with pure
python code (like sync), do you have
any suggestions ?
Do we already have testcases for the use of ls and cat in the tools.py ?
Huh? I think this has already been done (see FileHolder in files.py), I just
left the old code
Question for a gump newbi.
As the fog clears - you would anticipate a fog factor approaching zero.
Maybe it should, a boundary value is more comparable.
In the context of gump - is zero fog a good thing? Summary - I don't
understand the fog factor index - can anyone explain it or point
Maybe it should, a boundary value is more comparable.
Sorry, I meant to type bounded value as in 0-1.
On this course they showed 30 of us fives line of text, and asked us to
count the number of Fs. Many folks found 3, and some found as many as 7. As
time went on more and more folks found the 7,
If that's is a correct (reasonable) assumption - is this something I
should post to JIRA?
Please do add all comments you have on FOG to JIRA at:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=GUMP-21
regards
Adam
Adam, I think we should get rid of FoG entirely until we have a better
solution. It is causing more harm than good.
What is harm and what is refining discussion? If we remove it, what
incentive do folks have to contribute improvements?
I'll do whatever the group determines, but first teach me
how do you feel about setting up [EMAIL PROTECTED] for all change
notifications?
+0
regards
Adam
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Yeah, it seems not. I don't know if this is related, but I had woes trying
to run/test Gump on my VM server Gump-box yesterday also. Basically the
poor
box swapped itself to death, in part 'cos forrest grew so large. The xdocs
were written, but the forrest site wasn't generated. I wonder if
Who's Gump in whose account? Sam's? Is anybody aware of the outputs, let
alone using them?
I don't think folks have had access to the outputs (that they've known
about) in forever.
http://gump.apache.org/#Where+is+Gump%3F
regards
Adam
- Original Message -
From: Noel J. Bergman
OK, it looks like there may be a new ASF hosted machine or two running
gump in the next 24 or so hours. Which gump should be run on it?
Which? As in traditioanl verse Python? I think concensus has been Python for
a while.
We have a README in /usr/local/gump on moof, ought I post it here for
We have a README in /usr/local/gump on moof, ought I post it here for
folks?
I can't get there this mo, and my eyebrowse search isn't bringing up when
I
posted it before. It has the steps involved.
A google search found me this:
http://www.mail-archive.com/[EMAIL
We should probably use a template engine. I'm sure there's a python
equivalent for something like velocity (or smarty).
First, I like the dynamic 'tree of nodes' based approach to writing
HTML/XML, rather than template -- in the main because of pleasant
experiences with the Perl modules for
1) use forrest as a dynamic application
First, what do you mean by this, please? For those of us who don't know,
could somebody elaborate?
Second, I think it is forrest that is where we are getting stuck right now.
Now sure why, but it is locking up. So, if we want forest, we have to figure
First, I like the dynamic 'tree of nodes' based approach to writing
HTML/XML, rather than template
I like merging the concepts. Once you've built the tree, flatten the
part of it that will make up the page, and feed that to the template
engine. Even if you don't use a template engine,
Davey [EMAIL PROTECTED]
To: Gump code and data [EMAIL PROTECTED]
Sent: Thursday, March 25, 2004 4:01 PM
Subject: Re: Gump Thrashing/Spinning...
Adam Jack wrote:
[snip]
I think it is forrest that is where we are getting stuck right now.
Now sure why, but it is locking up. So, if we want
Now Gump generates it's xdocs using an object tree structure. Watching
the
python memory grow from 20M (after loading all XML) to 136M (during
generating these pages) it has some sort of leak (actual or effective)
ouch! Maybe it would pay off to use pipelining (you know, SAX, stuff)
Interesting. LSD took 7 hours to run, which is 3 hours longer than usual.
Gump.try was swamped by a tonne of Java processes (that looked like ant
forking ant) and I had to kill it. I suspect you are right this is looping
on itself.
Stefan, if this due to Python Gump using the hard coded 'clone
This page shows the entities (modules or projects) that have any 'warning'
or 'error' annotations on them. We really want to work this down to a blank
page, by reducing the verbosity or level of annotations. For example, saying
'build failed' at a warning level could me made informational (the
I hand moved the large XML files from
content/xdocs/.../gump_[work|file|/*.xml to content/... -- and then ran
forrest.
I think I inserted the fix earlier to make this automatic from now on.
regards,
Adam
-
To unsubscribe,
BuildFileTest is used by some Depot builds to test it's Ant tasks.
BuildFileTest is within the jar produced by project ant-testutil. This
project has ant-dist as a dependency, and this is a heavy dependency for
users of the single BuildFileTest class.
Nick and I are trying (partly as an exercise
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 gump-test has an issue affecting its community integration.
Project State :
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]
Module apache-gump-test contains errors.
Module State : 'Success'
Full details are
All,
As part of the migration towards SVN (at least in parcel with CVS), I asked
infrastructure to create a shared commits mailing list. They have done so:
http://issues.apache.org/jira/browse/INFRA-92
Now apparently mails going to [EMAIL PROTECTED] (from CVS commits) now go
to [EMAIL
Stefano,
To load a Workspace one ought use the WorkspaceLoader to load it (ws here is
a path/filename):
# get parsed workspace definition
from gump.core.loader.loader import WorkspaceLoader
workspace=WorkspaceLoader().load(ws)
To get a GumpRun (wrapper around a workspace), do:
Build from repository is a beautiful thing. Even though Beaver broke with
a technicality (the LICENSE file was missing) Gump was able (and willing) to
take the latest successful build of it from the repository. As such, even
though we state Beaver is the root cause (despite not being a direct
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 gump-test has an issue affecting its community integration.
Project State : '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 gump-test has an issue affecting its community integration, and has been
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 gump-test has an issue affecting its community integration, and has been
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 gump-test has an issue affecting its community integration, and has been
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 gump-test has an issue affecting its community integration, and has been
I just noticed a sync (where Gump copies from one directory tree to another)
failure occuring in XOM due to unicode decode issues. I always struggle to
get my ehad around the magic that is unicode (to/from 'real world') and I'd
appreciate any thoughts.insights here. The file name
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 gump-test has an issue affecting its community integration, and has been
I took a look at the ws-jaxme configuration, and its Ant scripts. As far as
I followed it, I was wrong about this being a simple work or depend
problem. I wonder if it is a clean environment problem.
Looking at the build output:
Please subscribe to the new mailing list:
http://gump.apache.org/mail.html#Commits+List
Since we migrated to both SVN and CVS this was created (a week or so ago),
but folks subscribed to [EMAIL PROTECTED] were *NOT* automatically subscribed to
[EMAIL PROTECTED] Please do so manually -- or
To whom it may satisfy...
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 gump-test *no longer* has an issue.
Project State : 'Success', Reason ''
Full
I think there is a new reason for ant-contrib disappearing, and I suspect it
is related to the spam that SF.net seem to be putting at the top of their
viewcvs. When I curl this URL from brutus I get HTML not XML
Looking at:
http://brutus.apache.org/gump/public/excalibur/excalibur-logger/gump_work/build_excalibur_excalibur-logger.html
I see Maven thinks these are unsatisfied:
The build cannot continue because of the following unsatisfied
dependencies:
avalon-framework-4.1.5.jar
As I get back into this I'd like to run the Gump unit tests. Can somebody
help me with:
F:\data\Python\gump-svn\pythonpython gump/test/pyunit.py
Traceback (most recent call last):
File gump/test/pyunit.py, line 25, in ?
from gump import log
File
Ok, I'm hooked. Much as there seems like masses of work to do (see BTW at
bottom) I like the opportunity to redo things afresh, and specially replace
the Gump2 working prototype with a more Pythonic approach. [When I was
writing Gump2 I didn't know the front from the back of Python, and it shows.
All,
I've created: /.../gump/staging (for shared CVS|SVN staging)
I've updated /.../gump/[test|kaffe|jdk15]/gump/metadata/brutus.xml to point
to above.
I've delete:/.../gump/[test|kaffe|jdk15]/workspace/cvs.
Since these three runs use the trunk of SVN, the change I added last week
(to [on
I've been pretty flaky these last months; not able to commit the time/effort
I'd enjoy committing. Basically, of the three days a week I can work (the
others I grow with my daughter) I've been working for a start-up that
consumes me. It is fun to build something from scratch, but I need to let
Folks,
Any ideas what this is about? I believe it started when I trimmed the
bloated classpaths, meaning it used to work when something else added
something. Is it requiring Xerces2 (I see it depends upon xerces)? Could
somebody give a quick xerces depends 101, e.g. when to ask for it on
Here are some random thoughts/questions, on things I'd like to see explored
with Gump3. I'd appreciate insights on if they are good requirements (for
now) and/or how we might design them in:
1) External PlugIns
I'd really like to hear design/implementation ideas about
discovery/life-cycle of
Why are CvsUpdater, SvnUpdater pre-process plug-ins, not 'process' visitors?
Clearly (as of now) it make little difference, I'm just trying to
understand.
I'm not sure I'm comfortable with the three pre-process/process/post-process
walks. Is this a Gump2 hold over that we want in Gump3? I'm not
[Not that I'll have time over the next few days, but maybe within the next
week, but ...] I'd like to work towards getting some things built w/ Gump3,
by working on two plug-ins, (or one with two modes). The first will lay out
the plan, constructing classpaths and such, and recording these
I'd try to fix it, but I only have an hour free want to work on something
else.
regards
Adam
==
FAIL: test_do_script (testPluginBuilder.BuilderTestCase)
--
I'm working on a new Gump instance on Brutus. Clearly, it is a Gump3
instance.
As such, I've added a line like this to cron:
$ /bin/bash gump run --databasename=gump3
I'd like to get it up and running, and (at least) running the gump test
command line. Using the current implementation of
I learn a program's behaviour from watching it's logs. I want to see the
Gump3 logs, but am getting a headache trying to figure out how:
1) Why is there a long pause before logs start spewing when one
does --debug? Is some file buffered? How can I get spew as you go
behaviour so I can 'watch' it?
I meant to send this yesterday, but somehow failed to pres send...
What is the thinking behind this being an array? Do we want to support
multiple dependencies from one project to another?
BTW: Per [1] I've change DependencyInfo.specific_output_id to ids (plural).
Now an array.
regards
Adam
So, with the addition of tools.jar to the classpath Ant (from bootstrap-ant)
can now build dist-ant under Gump3. We are starting to see Gump3 interact w/
it's customer base. :-) I think the next important steps are to define a
good working set (maybe a test profile) of projects to build. Since
Folks,
I am starting to think that Gump3 needs to integrate with JIRA, in
preference to building some functionality itself. Basically, Gump3 ought
leverage JIRA's notification ability (e-mail and RSS), and it's tracking
process (commenting, tracking, status, history). Basically Gump outages
I've enabled public on vmgump [1] to (1) do an official build each day and
(2) deliver notifications via e-mail when it does. With Brutus gone, it
seems time. That said, seems we have some package work to do. [2] [3]
regards
Adam
[1] http://vmgump.apache.org/gump/public/
[2]
I am frustrated trying to debug vmgump, and e-mail notifications. I just
don't know if they are getting through, or not. Heck, for the longest time I
didn't know if they were being sent, and I'm still not sure. Rather than me
subscribe to a gazzillion mailing lists I keep wondering if Gump ought
It doesn't look like vmgump has disk space for more than one Gump. When I
asked #asfinfra about it they said ask leo, I believe that the intent was
to have separate VMs, but I'm not sure. So, here I am (in line after Dim's
question yesterday :-).
Thinking about this, what are the pros/cons? Why
We have (to my knowledge) three ideas posted, the first thanks to Scott.
I've been contacted (twice, in the few days since I posted it) for
gump-presentation.
http://wiki.apache.org/general/SummerOfCode2005#gump-and-maven
http://wiki.apache.org/general/SummerOfCode2005#gump-and-doap
Folks
Are we seeing some duplicate moderated in e-mails (perhaps due to two
moderators moderating at different times?) I know this ought not occur, but
I wonder if (say) some spam storm is causing things not to be normal. Just
curious what others are seeing/thinking on this...
regards,
Adam
Folks,
Somebody (not me) seems to have most/all of a test Gump install on our
solaris zone. Thanks!!!
I simply (after some poking around) had to re-create /var/run/apache2 and
start the HTTPD, and we get these pages.
I've just kicked off a test run.
I've been tinkering with an IRC plug-in for Gump3 that allows it to interact
with an IRC channel.
Given how long our runs are, it seems reasonable that we'd like to interact
with them in real-time. Theoretically Gump3 could (one day) become a
long-lived IRC bot that took requests/instructions
It seems that the kind folks at infrastructure@ are about ready to do this,
the test run looks clean. It occurs to be that we've considered the human
impact of this moving (waiting until most ASFers are comfortable with SVN)
but not the automated Gump impact. We need to migrate our, and other,
Folks
Can I get details/pointers from anybody on how the Kaffe run was installed
last time (on Brutus?) If so, I'll attempt to get it redone. Thanks in
advance.
regards
Adam
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
With the help of some kind folk on irc#kaffe we have the start of :
http://gump.zones.apache.org/gump/kaffe/buildLog.html
There was a certain amount of juggling about to get Kaffe to compile on this
Solaris, and a few tests fail. That said, we are using CVS HEAD of Kaffe, so
can
What issue did this fix? I don't get it. Is kaffe misbehaving?
Yes, it was/is deadlocking it's GC thread (folks believe.) Either way it was
hanging and fixes were going into CVS HEAD. What this allows is to build
Kaffe at the start of the run (and search for cores at the end) and hence
not
Wow, I guess it ought not be a surprise that I hardly follow a word of
this. I've missed a lot in a couple of years. :-)
Hmm, and I still need to figure out how to send from @apache.org again.
regards
Adam
On Mar 12, 2009, at 11:16 PM, Stefan Bodewig wrote:
Hi all,
these are the mid-term
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
On 12 Jun 2013, at 01:31, Stefan Bodewig bode...@apache.org wrote:
On 2013-06-11, Adam R. B. Jack wrote:
As for your letter, I like it. Perhaps add a paragraph as to why Gump
does it's builds?
OK.
NOTE: I'd try to find appropriate dev/general lists for each project and
do with a single
Very reasonable.
Adam
Sent from my iPad
On Jul 21, 2013, at 12:20 AM, Stefan Bodewig bode...@apache.org wrote:
Hi
after about a month we have three projects still interested in Gump
(Tomcat, POI, XMLGraphics), two saying they don't care too much (Xerces,
Xalan), one asking to get
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project gump-test has an issue affecting its community integration.
This issue
1 - 100 of 132 matches
Mail list logo
