Re: gump3 - error
Justin Merz wrote: I can't seem to trace error back. Any suggestions? Ignore the test failures for now. I broke some of them yesterday. cheers, LSD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gump3 Presentation -- choice of technology
Leo Simons wrote: Thomas wrote: More I have taken a look at the dynaGump but can't get it to woork the application is missing a Catalogmanager.properties. I've copied one from the samples of the cocoon source but don't know if I need configure it in anny special way. That has got to be the most common error or rather warning cocoon spits out. It should be able to work without that file. What do you see when visiting http://localhost:8080/? Ignore the CatalogManager.properties message. It is for adding your own catalog to look up extra DTDs for xml source documents, to save network trips and get a local copy. You can have an optional CatalogManager.properties in your project which can be empty and thus keep the thing quiet. What version of Cocoon is this? -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dynagumper is alive!
so I figured we'd need to get Thomas some more data. Rather than invent it by hand, I figured I'd fix up the dynagumper plugin to work properly. See Cool, that is what I've been trying to do with Gump3 on VmGump: Oh, and you're now greeted with 100s of lines of error messages if you don't have a db connection or a messed up database :-). Like this? ;-) http://vmgump.apache.org/gump/gump3/run.log Adam, perhaps you could take a pass through the code and point your finger at stuff that's messed up or which doesn't make sense? Also, one todo that'd be nice to have when building dynagump is to actually have long logs stored in the DB. I know you've spent a lot of time on the builder plugins. For some reason no build_log properties are being set. Could you try and get that running? Sure. In return, could you look into the problem above seeking to understand why these failures cause Gump to fall off IRC, not exit? Are certain plugins not getting called when another fails? I'm never quite sure how Gump3 copes with errors. BTW: Can we fix the schema, or do we need to re-instantiate it? regards, Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN migration of metadata
I'm halfway torn between throwing history away and simply importing CVS HEAD manually and doing a trunk-only conversion. Well, not really true, I'd probably prefer keeping the history, but could live without it. What's your preference? +1 for keep the history. The second question is, where should our metadata end up in SVN? Probably in http://svn.apache.org/repos/asf/gump/metadata/trunk - I envision metadata branches for Gump3 later, so I'd be against a flat structure like site currently has. +1 in theory, 'cos looking at our SVN tree we do seem to use /gump/X/trunk when we have a sub-project X, but see below. Since today folks (1) checkout Gump from SVN and (2) checkout metadata from CVS into ./metadata, I don't see a hardship of having two places. That said, will SVN allow us to do this w/o pain? Can we have an empty /repos/asf/gump/trunk/metadata become a local working directory, and then checkout /repos/asf/gump/metadata/trunk into it? I suspect not. I think we got away with it because we were using two separate SCMs. Something will have to give, I'm just not sure what, i.e. (1) no empty ./metadata w/ a FILLME.txt (2) ../metadata not ./metadata (3) not separate SVN trees. Thoughts? regards, Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 11 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Module jakarta-commons-sandbox success, but with warnings. [EMAIL PROTECTED]: Module lenya success, but with warnings. [EMAIL PROTECTED]: Project nant (in module nant) failed [EMAIL PROTECTED]: Project txt2html-task (in module jakarta-servletapi-5) success, but with warnings. [EMAIL PROTECTED]: Project httpunit (in module httpunit) failed [EMAIL PROTECTED]: Project derby-split-2 (in module db-derby) failed [EMAIL PROTECTED]: Project jtidy-cvs (in module jtidy) failed [EMAIL PROTECTED]: Project myfaces (in module myfaces) failed [EMAIL PROTECTED]: Project xml-security-tests (in module xml-security) failed [EMAIL PROTECTED]: Project commons-feedparser (in module jakarta-commons) failed [EMAIL PROTECTED]: Project groovy (in module groovy) failed *** G U M P [EMAIL PROTECTED]: Module jakarta-commons-sandbox success, but with warnings. To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Module jakarta-commons-sandbox contains errors. The current state of this module is 'Success'. Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -ERROR- *** Failed to update from source control. Stale contents *** The following work was performed: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/gump_work/update_jakarta-commons-sandbox.html Work Name: update_jakarta-commons-sandbox (Type: Update) Work ended in a state of : Failed Elapsed: 44 secs Command Line: svn --quiet update --non-interactive jakarta-commons-sandbox [Working Directory: /usr/local/gump/public/workspace/cvs] - svn: REPORT request failed on '/repos/asf/!svn/vcc/default' svn: Cannot replace a directory from within - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/rss.xml - Atom: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 25010006072005, vmgump.apache.org:vmgump-public:25010006072005 Gump E-mail Identifier (unique within run) #1. *** G U M P [EMAIL PROTECTED]: Module lenya success, but with warnings. To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Module lenya contains errors. The current state of this module is 'Success'. Full details are available at: http://vmgump.apache.org/gump/public/lenya/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -ERROR- *** Failed to update from source control. Stale contents *** The following work was performed: http://vmgump.apache.org/gump/public/lenya/gump_work/update_lenya.html Work Name: update_lenya (Type: Update) Work ended in a state of : Failed Elapsed: 3 mins 28 secs Command Line: svn --quiet update --non-interactive lenya [Working Directory: /usr/local/gump/public/workspace/cvs] - svn: PROPFIND request failed on '/svn/kupu/branch/kupu-1.2' svn: PROPFIND of '/svn/kupu/branch/kupu-1.2': could not connect to server (http://codespeak.net) - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/lenya/rss.xml - Atom: http://vmgump.apache.org/gump/public/lenya/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 25010006072005, vmgump.apache.org:vmgump-public:25010006072005 Gump E-mail Identifier (unique within run) #2. *** G U M P [EMAIL PROTECTED]: Project nant (in module nant) 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 the folk at [EMAIL PROTECTED] Project nant has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 94 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - nant : NAnt is a
BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 11 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Module jakarta-commons-sandbox success, but with warnings. [EMAIL PROTECTED]: Module lenya success, but with warnings. [EMAIL PROTECTED]: Project nant (in module nant) failed [EMAIL PROTECTED]: Project txt2html-task (in module jakarta-servletapi-5) success, but with warnings. [EMAIL PROTECTED]: Project httpunit (in module httpunit) failed [EMAIL PROTECTED]: Project derby-split-2 (in module db-derby) failed [EMAIL PROTECTED]: Project jtidy-cvs (in module jtidy) failed [EMAIL PROTECTED]: Project myfaces (in module myfaces) failed [EMAIL PROTECTED]: Project xml-security-tests (in module xml-security) failed [EMAIL PROTECTED]: Project commons-feedparser (in module jakarta-commons) failed [EMAIL PROTECTED]: Project groovy (in module groovy) failed *** G U M P [EMAIL PROTECTED]: Module jakarta-commons-sandbox success, but with warnings. To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Module jakarta-commons-sandbox contains errors. The current state of this module is 'Success'. Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -ERROR- *** Failed to update from source control. Stale contents *** The following work was performed: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/gump_work/update_jakarta-commons-sandbox.html Work Name: update_jakarta-commons-sandbox (Type: Update) Work ended in a state of : Failed Elapsed: 44 secs Command Line: svn --quiet update --non-interactive jakarta-commons-sandbox [Working Directory: /usr/local/gump/public/workspace/cvs] - svn: REPORT request failed on '/repos/asf/!svn/vcc/default' svn: Cannot replace a directory from within - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/rss.xml - Atom: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 25010006072005, vmgump.apache.org:vmgump-public:25010006072005 Gump E-mail Identifier (unique within run) #1. *** G U M P [EMAIL PROTECTED]: Module lenya success, but with warnings. To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Module lenya contains errors. The current state of this module is 'Success'. Full details are available at: http://vmgump.apache.org/gump/public/lenya/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -ERROR- *** Failed to update from source control. Stale contents *** The following work was performed: http://vmgump.apache.org/gump/public/lenya/gump_work/update_lenya.html Work Name: update_lenya (Type: Update) Work ended in a state of : Failed Elapsed: 3 mins 28 secs Command Line: svn --quiet update --non-interactive lenya [Working Directory: /usr/local/gump/public/workspace/cvs] - svn: PROPFIND request failed on '/svn/kupu/branch/kupu-1.2' svn: PROPFIND of '/svn/kupu/branch/kupu-1.2': could not connect to server (http://codespeak.net) - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/lenya/rss.xml - Atom: http://vmgump.apache.org/gump/public/lenya/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 25010006072005, vmgump.apache.org:vmgump-public:25010006072005 Gump E-mail Identifier (unique within run) #2. *** G U M P [EMAIL PROTECTED]: Project nant (in module nant) 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 the folk at [EMAIL PROTECTED] Project nant has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 94 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - nant : NAnt is a
Re: SVN migration of metadata
On Wed, 6 Jul 2005, Adam R. B. Jack [EMAIL PROTECTED] wrote: Since today folks (1) checkout Gump from SVN and (2) checkout metadata from CVS into ./metadata, I don't see a hardship of having two places. That said, will SVN allow us to do this w/o pain? We can add an svn:external to gump/trunk that checks out metadata into the correct place. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dynagumper is alive!
On 06-07-2005 13:51, Adam R. B. Jack [EMAIL PROTECTED] wrote: Oh, and you're now greeted with 100s of lines of error messages if you don't have a db connection or a messed up database :-). Like this? ;-) http://vmgump.apache.org/gump/gump3/run.log Fancy! BTW: Can we fix the schema, or do we need to re-instantiate it? The latter. I'll try and take care of it tonight. Adam, perhaps you could take a pass through the code and point your finger at stuff that's messed up or which doesn't make sense? Also, one todo that'd be nice to have when building dynagump is to actually have long logs stored in the DB. I know you've spent a lot of time on the builder plugins. For some reason no build_log properties are being set. Could you try and get that running? Sure. In return, could you look into the problem above seeking to understand why these failures cause Gump to fall off IRC, not exit? Huh? Ehm, will do. Are certain plugins not getting called when another fails? I'm never quite sure how Gump3 copes with errors. Its supposed to be pretty simple: all exceptions that occur inside a plugin bubble up to the algorithm that's being run. The idea is that you configure the ErrorHandler used with the Algorithm. Using the OptimisticLoggingErrorHandler swallows the exceptions that plugins raise, whereas the LoggingErrorHandler re-raises all of them. Maybe the post-processing plugins are configured with the LoggingErrorHandler or something. I'll check. Cheers, LSD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN migration of metadata
Adam R. B. Jack wrote: I'm halfway torn between throwing history away and simply importing CVS HEAD manually and doing a trunk-only conversion. Well, not really true, I'd probably prefer keeping the history, but could live without it. What's your preference? +1 for keep the history. The second question is, where should our metadata end up in SVN? Probably in http://svn.apache.org/repos/asf/gump/metadata/trunk - I envision metadata branches for Gump3 later, so I'd be against a flat structure like site currently has. +1 in theory, 'cos looking at our SVN tree we do seem to use /gump/X/trunk when we have a sub-project X, but see below. Since today folks (1) checkout Gump from SVN and (2) checkout metadata from CVS into ./metadata, I don't see a hardship of having two places. That said, will SVN allow us to do this w/o pain? of course, svn:external is your friend :-) Can we have an empty /repos/asf/gump/trunk/metadata become a local working directory, and then checkout /repos/asf/gump/metadata/trunk into it? I suspect not. I think we got away with it because we were using two separate SCMs. Something will have to give, I'm just not sure what, i.e. (1) no empty ./metadata w/ a FILLME.txt (2) ../metadata not ./metadata (3) not separate SVN trees. Thoughts? regards, Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stefano. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r209496 - in /gump/branches/Gump3/pygump/python/gump/test: testDynagumper.py testModel.py
Scott laughs to self as this is exactly where he led Justin in private email to get the test case working :) Justin, you can undo your change and just svn update the new code :) Scott On Jul 6, 2005, at 11:39 AM, [EMAIL PROTECTED] wrote: def test_visit_module(self): -#TODO class m: - def __init__(self, n, d, u): + def __init__(self, n, d, u, r): self.name = n self.description = d self.url = u +self.repository = r + +class r: + def __init__(self, workspace, name): +self.workspace = workspace +self.name= name -mi = m(blah, blah blah, http://example.com;) +class w: + def __init__(self, name): +self.name= name + +wi = w(blah) +ri = r(wi, blah) +mi = m(blah, blah blah, http://example.com;, ri) dynagumper = Dynagumper(self.db,self.log) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r209496 - in /gump/branches/Gump3/pygump/python/gump/test: testDynagumper.py testModel.py
Scott Sanders wrote: Scott laughs to self as this is exactly where he led Justin in private email to get the test case working :) Justin, you can undo your change and just svn update the new code :) Scott On Jul 6, 2005, at 11:39 AM, [EMAIL PROTECTED] wrote: def test_visit_module(self): - #TODO class m: - def __init__(self, n, d, u): + def __init__(self, n, d, u, r): self.name = n self.description = d self.url = u + self.repository = r + + class r: + def __init__(self, workspace, name): + self.workspace = workspace + self.name = name - mi = m(blah, blah blah, http://example.com;) + class w: + def __init__(self, name): + self.name = name + + wi = w(blah) + ri = r(wi, blah) + mi = m(blah, blah blah, http://example.com;, ri) dynagumper = Dynagumper(self.db,self.log) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I just got the lastest commit and test is running fine now. I am movin on -Thanks Justin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
