BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 7 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Module castor success, but with warnings. [EMAIL PROTECTED]: Project nant (in module nant) failed [EMAIL PROTECTED]: Module jaxen success, but with warnings. [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 jaxen (in module jaxen) failed *** G U M P [EMAIL PROTECTED]: Module castor success, but with warnings. To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Module castor contains errors. The current state of this module is 'Success'. Full details are available at: http://vmgump.apache.org/gump/public/castor/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -ERROR- *** Failed to update from source control. Stale contents *** The following work was performed: http://vmgump.apache.org/gump/public/castor/gump_work/update_castor.html Work Name: update_castor (Type: Update) Work ended in a state of : Failed Elapsed: 11 secs Command Line: cvs -q -z3 -d :pserver:[EMAIL PROTECTED]:/scm/castor update -P -d -A [Working Directory: /usr/local/gump/public/workspace/cvs/castor] - cvs server: failed to create lock directory for `/scm/castor/castor/lib/tests' (/home/projects/castor/haus.d/lock/cvs/castor/lib/tests/#cvs.lock): Permission denied cvs server: failed to obtain dir lock in repository `/scm/castor/castor/lib/tests' cvs [server aborted]: read lock failed - giving up - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/castor/rss.xml - Atom: http://vmgump.apache.org/gump/public/castor/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2323062005, vmgump.apache.org:vmgump-public:2323062005 Gump E-mail Identifier (unique within run) #1. *** 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 46 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 free .NET build tool. In theory it is kind of like... Full details are available at: http://vmgump.apache.org/gump/public/nant/nant/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/nant/nant/gump_work/build_nant_nant.html Work Name: build_nant_nant (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs Command Line: make [Working Directory: /usr/local/gump/public/workspace/nant] - mkdir -p bootstrap cp -R lib/ bootstrap/lib # Mono loads log4net before privatebinpath is set-up, so we need this in the same directory # as NAnt.exe cp lib/log4net.dll bootstrap cp src/NAnt.Console/App.config bootstrap/NAnt.exe.config mcs -target:exe -define:MONO -out:bootstrap/NAnt.exe -r:bootstrap/log4net.dll \ -recurse:src/NAnt.Console/*.cs src/CommonAssemblyInfo.cs Compilation succeeded resgen src/NAnt.Core/Resources/Strings.resx bootstrap/NAnt.Core.Resources.Strings.resources make: resgen: Command not found make: *** [bootstrap/NAnt.Core.dll] Error 127 - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/nant/nant/rss.xml - Atom: http://vmgump.apache.org/gump/public/nant/nant/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2323062005, vmgump.apache.org:vmgump-public:2323062005 Gump E-mail Identifier (unique within run) #2. *** G U M P [EMAIL PROTECTED]: Module jaxen success, but with warnings. To whom it may engage... This is an automated request, but not an unsolicited one. For more
BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 7 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Module castor success, but with warnings. [EMAIL PROTECTED]: Project nant (in module nant) failed [EMAIL PROTECTED]: Module jaxen success, but with warnings. [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 jaxen (in module jaxen) failed *** G U M P [EMAIL PROTECTED]: Module castor success, but with warnings. To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Module castor contains errors. The current state of this module is 'Success'. Full details are available at: http://vmgump.apache.org/gump/public/castor/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -ERROR- *** Failed to update from source control. Stale contents *** The following work was performed: http://vmgump.apache.org/gump/public/castor/gump_work/update_castor.html Work Name: update_castor (Type: Update) Work ended in a state of : Failed Elapsed: 11 secs Command Line: cvs -q -z3 -d :pserver:[EMAIL PROTECTED]:/scm/castor update -P -d -A [Working Directory: /usr/local/gump/public/workspace/cvs/castor] - cvs server: failed to create lock directory for `/scm/castor/castor/lib/tests' (/home/projects/castor/haus.d/lock/cvs/castor/lib/tests/#cvs.lock): Permission denied cvs server: failed to obtain dir lock in repository `/scm/castor/castor/lib/tests' cvs [server aborted]: read lock failed - giving up - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/castor/rss.xml - Atom: http://vmgump.apache.org/gump/public/castor/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2323062005, vmgump.apache.org:vmgump-public:2323062005 Gump E-mail Identifier (unique within run) #1. *** 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 46 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 free .NET build tool. In theory it is kind of like... Full details are available at: http://vmgump.apache.org/gump/public/nant/nant/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/nant/nant/gump_work/build_nant_nant.html Work Name: build_nant_nant (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs Command Line: make [Working Directory: /usr/local/gump/public/workspace/nant] - mkdir -p bootstrap cp -R lib/ bootstrap/lib # Mono loads log4net before privatebinpath is set-up, so we need this in the same directory # as NAnt.exe cp lib/log4net.dll bootstrap cp src/NAnt.Console/App.config bootstrap/NAnt.exe.config mcs -target:exe -define:MONO -out:bootstrap/NAnt.exe -r:bootstrap/log4net.dll \ -recurse:src/NAnt.Console/*.cs src/CommonAssemblyInfo.cs Compilation succeeded resgen src/NAnt.Core/Resources/Strings.resx bootstrap/NAnt.Core.Resources.Strings.resources make: resgen: Command not found make: *** [bootstrap/NAnt.Core.dll] Error 127 - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/nant/nant/rss.xml - Atom: http://vmgump.apache.org/gump/public/nant/nant/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2323062005, vmgump.apache.org:vmgump-public:2323062005 Gump E-mail Identifier (unique within run) #2. *** G U M P [EMAIL PROTECTED]: Module jaxen success, but with warnings. To whom it may engage... This is an automated request, but not an unsolicited one. For more
Re: BATCH: All dressed up, with nowhere to go...
Hi gang, Does anyone ever do anything with the content of these messages? I tend to use them as a gauge of gump ran and it sent e-mail, but as the actual content I would much rather have something like a list of failures/successes, i.e. a condensed version of log.html. Do you agree? Just planning for the future here... Cheers, LSD On 23-06-2005 12:57, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Dear Gumpmeisters, The following 7 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Module castor success, but with warnings. [EMAIL PROTECTED]: Project nant (in module nant) failed [EMAIL PROTECTED]: Module jaxen success, but with warnings. [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 jaxen (in module jaxen) failed *** G U M P [EMAIL PROTECTED]: Module castor success, but with warnings. To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Module castor contains errors. The current state of this module is 'Success'. Full details are available at: http://vmgump.apache.org/gump/public/castor/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -ERROR- *** Failed to update from source control. Stale contents *** The following work was performed: http://vmgump.apache.org/gump/public/castor/gump_work/update_castor.html Work Name: update_castor (Type: Update) Work ended in a state of : Failed Elapsed: 11 secs Command Line: cvs -q -z3 -d :pserver:[EMAIL PROTECTED]:/scm/castor update -P -d -A [Working Directory: /usr/local/gump/public/workspace/cvs/castor] - cvs server: failed to create lock directory for `/scm/castor/castor/lib/tests' (/home/projects/castor/haus.d/lock/cvs/castor/lib/tests/#cvs.lock): Permission denied cvs server: failed to obtain dir lock in repository `/scm/castor/castor/lib/tests' cvs [server aborted]: read lock failed - giving up - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/castor/rss.xml - Atom: http://vmgump.apache.org/gump/public/castor/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2323062005, vmgump.apache.org:vmgump-public:2323062005 Gump E-mail Identifier (unique within run) #1. *** 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 46 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 free .NET build tool. In theory it is kind of like... Full details are available at: http://vmgump.apache.org/gump/public/nant/nant/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/nant/nant/gump_work/build_nant_nant.html Work Name: build_nant_nant (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs Command Line: make [Working Directory: /usr/local/gump/public/workspace/nant] - mkdir -p bootstrap cp -R lib/ bootstrap/lib # Mono loads log4net before privatebinpath is set-up, so we need this in the same directory # as NAnt.exe cp lib/log4net.dll bootstrap cp src/NAnt.Console/App.config bootstrap/NAnt.exe.config mcs -target:exe -define:MONO -out:bootstrap/NAnt.exe -r:bootstrap/log4net.dll \ -recurse:src/NAnt.Console/*.cs src/CommonAssemblyInfo.cs Compilation succeeded resgen src/NAnt.Core/Resources/Strings.resx bootstrap/NAnt.Core.Resources.Strings.resources make: resgen: Command not found make: *** [bootstrap/NAnt.Core.dll] Error 127 - To subscribe to this information via syndicated feeds: - RSS:
Re: BATCH: All dressed up, with nowhere to go...
I also use it as you use it, a sanity check that it ran (and these days -- on vmgump -- didn't stall.) That said, I also often eyeball it for candidates that I can go bug. When Gump is stable, sending notifications as needed, it annoys me if ASF projects don't accept notification. I also go and (politely) as other projects if they'll accept notification. That, I could do that w/ or w/o this e-mail. The other one like this (i.e. failed to send, not nowhere to send) is more interesting, e.g. when the host (vmgump) isn't allowed to relay: http://issues.apache.org/jira/browse/INFRA-365 regards, Adam - Original Message - From: Leo Simons [EMAIL PROTECTED] To: Gump code and data general@gump.apache.org Sent: Thursday, June 23, 2005 1:26 PM Subject: Re: BATCH: All dressed up, with nowhere to go... Hi gang, Does anyone ever do anything with the content of these messages? I tend to use them as a gauge of gump ran and it sent e-mail, but as the actual content I would much rather have something like a list of failures/successes, i.e. a condensed version of log.html. Do you agree? Just planning for the future here... Cheers, LSD On 23-06-2005 12:57, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Dear Gumpmeisters, The following 7 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Module castor success, but with warnings. [EMAIL PROTECTED]: Project nant (in module nant) failed [EMAIL PROTECTED]: Module jaxen success, but with warnings. [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 jaxen (in module jaxen) failed *** G U M P [EMAIL PROTECTED]: Module castor success, but with warnings. To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Module castor contains errors. The current state of this module is 'Success'. Full details are available at: http://vmgump.apache.org/gump/public/castor/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -ERROR- *** Failed to update from source control. Stale contents *** The following work was performed: http://vmgump.apache.org/gump/public/castor/gump_work/update_castor.html Work Name: update_castor (Type: Update) Work ended in a state of : Failed Elapsed: 11 secs Command Line: cvs -q -z3 -d :pserver:[EMAIL PROTECTED]:/scm/castor update -P -d -A [Working Directory: /usr/local/gump/public/workspace/cvs/castor] - cvs server: failed to create lock directory for `/scm/castor/castor/lib/tests' (/home/projects/castor/haus.d/lock/cvs/castor/lib/tests/#cvs.lock): Permission denied cvs server: failed to obtain dir lock in repository `/scm/castor/castor/lib/tests' cvs [server aborted]: read lock failed - giving up - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/castor/rss.xml - Atom: http://vmgump.apache.org/gump/public/castor/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2323062005, vmgump.apache.org:vmgump-public:2323062005 Gump E-mail Identifier (unique within run) #1. *** 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 46 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 free .NET build tool. In theory it is kind of like... Full details are available at: http://vmgump.apache.org/gump/public/nant/nant/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/nant/nant/gump_work/build_nant_nant.html Work Name: build_nant_nant (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs
Apache Gump now uses pylid
Hi Aldo!
I found
http://www.nullcube.com/software/pylid.html
while looking for a usable code coverage tool and test runner. It's much
better than what we (Gump [1]) had (we used testrunner.py from Zope
which is a real ugly script which I made uglier to have it run our tests).
I changed it a little bit to support multiple basedir arguments since
we have several source trees to aggregate. Patch attached. Feel free to
reuse under the BSD license or the Apache License v2.0, or not, whatever.
We may be adding some more features or modding the code a little to work
in our environment. If you feel like it you could follow that progress at
http://svn.apache.org/repos/asf/gump/branches/Gump3/bin/pylid-0.3/
Also, it isn't generating the coverage stats properly just yet, but I'm
sure I'll figure that out.
If I do mod stuff I'll be happy to provide patches to integrate upstream
but I couldn't find any info on a version control repo so...
Thanks for a neat little bit of code!
cheers,
Leo Simons
[1] -- http://gump.apache.org/
Index: pylid.py
===
--- pylid.py(revision 201501)
+++ pylid.py(working copy)
@@ -30,6 +30,8 @@
import sys, parser, token, symbol, copy, getopt, unittest, os, fnmatch,
os.path, time, glob, trace
+UNIT_TEST_FILE_NAME_GLOB = 'test*.py' # 'test_*.py'
+
def isPathContained(outer, inner):
Does inner lie within outer?
@@ -246,14 +248,16 @@
class Tester:
-def __init__(self, baseDir, include, exclude):
+def __init__(self, baseDirs, include, exclude):
-Takes the project base directory. This directory is inserted into
+Takes the project base directories. These directories are inserted
into
our path so that unit tests can import files/modules from there.
# We want to be able to import from the current dir
self.cov = Coverage(include, exclude)
-sys.path.insert(0, baseDir)
+for baseDir in baseDirs:
+sys.path.insert(0, baseDir)
+
# We also insert the current directory, to make sure we can import
# source files in our test directory.
sys.path.insert(0, .)
@@ -277,7 +281,7 @@
if os.path.isfile(path):
self._addFile(path, coverage)
elif os.path.isdir(path):
-for filename in glob.glob(os.path.join(path, 'test_*.py')):
+for filename in glob.glob(os.path.join(path,
UNIT_TEST_FILE_NAME_GLOB)):
self._addFile(filename, coverage)
else:
# We now assume that it's a module
@@ -376,7 +380,7 @@
If a project is structured correctly, these options
will rarely be required.)
group.add_option(-b, --base,
action=store, type=string, dest=base,
default=.., metavar=DIR,
- help='Project base directory. (Default: ..)')
+ help='Project base directories, seperated by colons.
(Default: ..)')
group.add_option(-e, --exclude,
action=append, type=string, dest=exclude,
metavar=DIR,
help='Exclude path from coverage analysis. Can be passed
multiple times. (Default: .)')
@@ -401,15 +405,17 @@
if options.clear:
for filename in GlobDirectoryWalker(options.include, '*.pyc'):
os.remove(filename)
-for filename in GlobDirectoryWalker(options.base, '*.pyc'):
-os.remove(filename)
+for basedir in options.base.split(':'):
+for filename in GlobDirectoryWalker(basedir, '*.pyc'):
+os.remove(filename)
for filename in GlobDirectoryWalker(options.include, '*.pyo'):
os.remove(filename)
-for filename in GlobDirectoryWalker(options.base, '*.pyo'):
-os.remove(filename)
+for basedir in options.base.split(':'):
+for filename in GlobDirectoryWalker(basedir, '*.pyo'):
+os.remove(filename)
# Do the actual run
-t = Tester(options.base, options.include, options.exclude)
+t = Tester(options.base.split(':'), options.include, options.exclude)
dostats = options.stats or options.annotate
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Dependencies update for jakarta commons-logging
Hi,
The dependencies for jakarta commons-logging have changed, and Gump has
reported problems. I would appreciate some help making the necessary
adjustments to gump.
commons-logging now depends on both:
* logging-log4j 1.2.x as ${log4j12.jar}, and
* logging-log4j 1.3 (currently at alpha-6) as ${log4j13.jar}
The dependency on both is needed as commons-logging provides adapters
for both versions of log4j, and the versions are binary-incompatible.
Thanks,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dependencies update for jakarta commons-logging
On Fri, 2005-06-24 at 14:41 +1200, Simon Kitching wrote:
Hi,
The dependencies for jakarta commons-logging have changed, and Gump has
reported problems. I would appreciate some help making the necessary
adjustments to gump.
commons-logging now depends on both:
* logging-log4j 1.2.x as ${log4j12.jar}, and
* logging-log4j 1.3 (currently at alpha-6) as ${log4j13.jar}
The dependency on both is needed as commons-logging provides adapters
for both versions of log4j, and the versions are binary-incompatible.
By the way, the jars generated by the ant build.xml file also now have a
version number in them, eg commons-logging-1.1-dev.jar. I don't know
how this affects the projects that depend on commons-logging.
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
