Problem running Apache Gump...
There is a problem with the run at : http://brutus.apache.org/gump/public The log ought be at: http://brutus.apache.org/gump/public/gump_log_31102004_02.txt The last (up to) 50 lines of the log are : INFO:gump:Build Project: #[(514, 704)] : jakarta-tapestry : [state:Prerequisite Failed] INFO:gump: -- Perform Artifact Repository Search for : jakarta-tapestry INFO:gump:Failed to find artifact for id jakarta-tapestry (Gump Repo has [u'jcharts'] in jakarta-tapestry) ERROR:gump: -- Extracted (fallback) artifacts from Repository : jakarta-tapestry INFO:gump:Build Project: #[(515, 704)] : jakarta-velocity-tools : [state:Prerequisite Failed] INFO:gump: -- Perform Artifact Repository Search for : jakarta-velocity-tools INFO:gump:Utilize jakarta-velocity-tools-gump-28102004.jar from Gump artifact repository for id: jakarta-velocity-tools INFO:gump:Build Project: #[(516, 704)] : metro-reflector-blocks-standard : [state:Unset] INFO:gump:Run Ant on Project: #[(516, 704)] : metro-reflector-blocks-standard INFO:gump:Build Project: #[(517, 704)] : ws-juddi : [state:Unset] INFO:gump:Run Ant on Project: #[(517, 704)] : ws-juddi INFO:gump:Published /usr/local/gump/public/workspace/ws-juddi/build/juddi-31102004.jar to repository as ws-juddi-gump-31102004.jar at /usr/local/gump/public/jars/ws-juddi/jars/ws-juddi-gump-31102004.jar INFO:gump:Build Project: #[(518, 704)] : ws-wsil : [state:Unset] INFO:gump:Run Ant on Project: #[(518, 704)] : ws-wsil INFO:gump:Build Project: #[(519, 704)] : xml-axis-wsil : [state:Unset] INFO:gump:Build Project: #[(520, 704)] : dist-ant : [state:Unset] INFO:gump:Run Ant on Project: #[(520, 704)] : dist-ant Traceback (most recent call last): File bin/integrate.py, line 109, in ? irun() File bin/integrate.py, line 86, in irun result = getRunner(run).perform() File /home/gump/workspaces2/public/gump/python/gump/core/runner/runner.py, line 213, in perform return self.performRun() File /home/gump/workspaces2/public/gump/python/gump/core/runner/demand.py, line 199, in performRun self.performBuild(project) File /home/gump/workspaces2/public/gump/python/gump/core/runner/demand.py, line 132, in performBuild self.run.generateEvent(project) File /home/gump/workspaces2/public/gump/python/gump/core/run/gumprun.py, line 198, in generateEvent self._dispatchEvent(EntityRunEvent(self, entity)) File /home/gump/workspaces2/public/gump/python/gump/core/run/gumprun.py, line 181, in _dispatchEvent actor._processEvent(event) File /home/gump/workspaces2/public/gump/python/gump/core/run/actor.py, line 90, in _processEvent self.processEvent(event) File /home/gump/workspaces2/public/gump/python/gump/core/run/actor.py, line 111, in processEvent self._processProject(entity) File /home/gump/workspaces2/public/gump/python/gump/core/run/actor.py, line 156, in _processProject self.processProject(project) File /home/gump/workspaces2/public/gump/python/gump/actor/mysql/databaser.py, line 98, in processProject if project.hasTimes(): File /home/gump/workspaces2/public/gump/python/gump/util/work.py, line 239, in hasTimes if self.getStart() and self.getEnd(): return True File /home/gump/workspaces2/public/gump/python/gump/util/timing.py, line 287, in __nonzero__ return self.getElapsedSecs() 0 File /home/gump/workspaces2/public/gump/python/gump/util/timing.py, line 315, in getElapsedSecs return deltaToSecs(self.endTimeStamp.getTimestamp() - self.getTimestamp()) File /home/gump/workspaces2/public/gump/python/gump/util/timing.py, line 102, in deltaToSecs raise RuntimeError, Can not cope with backwards deltas RuntimeError: Can not cope with backwards deltas Process Exit Code : 1 -- Gump Version: 2.0.2-alpha-0003 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [proposal] removing non-ASF leaves from the workspace
I've got no problem with removing Barcode4J from Gump. It is a nice-to-have but I can live without it. Go ahead. On 30.10.2004 19:55:21 Stefano Mazzocchi wrote: there are a few projects that gump builds that are not ASF projects and are not used by any ASF project. I think the ASF already has enough things to build for ourselves and gump is not a public service. I personally think that it is abusive for comitters to use their access to add projects that are not required. Examples of such projects are Barcode4j, Antworks, Smartfrog, but I'm sure I can found more (and, in fact, I'll write some code to outline those and automate the checks). I propose that we remove those projects from the gump.xml profile that is ran on brutus (we can keep the descriptors there, that doesn't hurt) but I would like to remove all those leaves projects from using cpu/disk space. WTDY? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [proposal] removing non-ASF leaves from the workspace
there are a few projects that gump builds that are not ASF projects and are not used by any ASF project. I think the ASF already has enough things to build for ourselves and gump is not a public service. I hear you, but since Gump was a social experiment not an ASF build tool, some of this was reach out. Don't forget that some non-ASF projects that Gump built became ASF projects, e.g. ws-juddi. I personally think that it is abusive for comitters to use their access to add projects that are not required. I don't know as much (partly since I added a few of them ;-). Other folks had the ability to -1 any. We used to run once a day, and as such it wasn't such a big deal. Examples of such projects are Barcode4j, Antworks, Smartfrog, but I'm sure I can found more (and, in fact, I'll write some code to outline those and automate the checks). I propose that we remove those projects from the gump.xml profile that is ran on brutus (we can keep the descriptors there, that doesn't hurt) but I would like to remove all those leaves projects from using cpu/disk space. WTDY? We have grown a lot larger in recent months, and are using a lot more CPU/disk. Further, we are trying to do more than one Gump workspace (JDK1.5, Kaffe, etc.) As such, maybe we do have to trim down. If it helps with that that, then go for it. For Gump to scale (as Niclas mentioned) we do need to federate somehow, but that is a separate topic this seems a practical step until then. Folks who really want to be included could petition us for re-inclusion. regards, Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem running Apache Gump...
Yikes, this is a new one on me. Ahh ... clocks changed back an hour in the middle of a run, perhaps. Grins a little embarrassed, shrugs, oh well... regards Adam - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, October 31, 2004 9:02 AM Subject: Problem running Apache Gump... There is a problem with the run at : http://brutus.apache.org/gump/public The log ought be at: http://brutus.apache.org/gump/public/gump_log_31102004_02.txt The last (up to) 50 lines of the log are : INFO:gump:Build Project: #[(514, 704)] : jakarta-tapestry : [state:Prerequisite Failed] INFO:gump: -- Perform Artifact Repository Search for : jakarta-tapestry INFO:gump:Failed to find artifact for id jakarta-tapestry (Gump Repo has [u'jcharts'] in jakarta-tapestry) ERROR:gump: -- Extracted (fallback) artifacts from Repository : jakarta-tapestry INFO:gump:Build Project: #[(515, 704)] : jakarta-velocity-tools : [state:Prerequisite Failed] INFO:gump: -- Perform Artifact Repository Search for : jakarta-velocity-tools INFO:gump:Utilize jakarta-velocity-tools-gump-28102004.jar from Gump artifact repository for id: jakarta-velocity-tools INFO:gump:Build Project: #[(516, 704)] : metro-reflector-blocks-standard : [state:Unset] INFO:gump:Run Ant on Project: #[(516, 704)] : metro-reflector-blocks-standard INFO:gump:Build Project: #[(517, 704)] : ws-juddi : [state:Unset] INFO:gump:Run Ant on Project: #[(517, 704)] : ws-juddi INFO:gump:Published /usr/local/gump/public/workspace/ws-juddi/build/juddi-31102004.jar to repository as ws-juddi-gump-31102004.jar at /usr/local/gump/public/jars/ws-juddi/jars/ws-juddi-gump-31102004.jar INFO:gump:Build Project: #[(518, 704)] : ws-wsil : [state:Unset] INFO:gump:Run Ant on Project: #[(518, 704)] : ws-wsil INFO:gump:Build Project: #[(519, 704)] : xml-axis-wsil : [state:Unset] INFO:gump:Build Project: #[(520, 704)] : dist-ant : [state:Unset] INFO:gump:Run Ant on Project: #[(520, 704)] : dist-ant Traceback (most recent call last): File bin/integrate.py, line 109, in ? irun() File bin/integrate.py, line 86, in irun result = getRunner(run).perform() File /home/gump/workspaces2/public/gump/python/gump/core/runner/runner.py, line 213, in perform return self.performRun() File /home/gump/workspaces2/public/gump/python/gump/core/runner/demand.py, line 199, in performRun self.performBuild(project) File /home/gump/workspaces2/public/gump/python/gump/core/runner/demand.py, line 132, in performBuild self.run.generateEvent(project) File /home/gump/workspaces2/public/gump/python/gump/core/run/gumprun.py, line 198, in generateEvent self._dispatchEvent(EntityRunEvent(self, entity)) File /home/gump/workspaces2/public/gump/python/gump/core/run/gumprun.py, line 181, in _dispatchEvent actor._processEvent(event) File /home/gump/workspaces2/public/gump/python/gump/core/run/actor.py, line 90, in _processEvent self.processEvent(event) File /home/gump/workspaces2/public/gump/python/gump/core/run/actor.py, line 111, in processEvent self._processProject(entity) File /home/gump/workspaces2/public/gump/python/gump/core/run/actor.py, line 156, in _processProject self.processProject(project) File /home/gump/workspaces2/public/gump/python/gump/actor/mysql/databaser.py, line 98, in processProject if project.hasTimes(): File /home/gump/workspaces2/public/gump/python/gump/util/work.py, line 239, in hasTimes if self.getStart() and self.getEnd(): return True File /home/gump/workspaces2/public/gump/python/gump/util/timing.py, line 287, in __nonzero__ return self.getElapsedSecs() 0 File /home/gump/workspaces2/public/gump/python/gump/util/timing.py, line 315, in getElapsedSecs return deltaToSecs(self.endTimeStamp.getTimestamp() - self.getTimestamp()) File /home/gump/workspaces2/public/gump/python/gump/util/timing.py, line 102, in deltaToSecs raise RuntimeError, Can not cope with backwards deltas RuntimeError: Can not cope with backwards deltas Process Exit Code : 1 -- Gump Version: 2.0.2-alpha-0003 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem running Apache Gump...
On Sunday 31 October 2004 21:30, Adam R. B. Jack wrote: Yikes, this is a new one on me. Ahh ... clocks changed back an hour in the middle of a run, perhaps. Grins a little embarrassed, shrugs, oh well... Simple solution for this, which I wonder why not every single host in the world use; UTC. Except for Americans it would make life a lot easier, since who have a clue about what PST and PDT is, and when it is either... ;o) Cheers Niclas -- +--//---+ / http://www.bali.ac/ / http://niclas.hedhman.org / +--//---+ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Kaffe instance and ant-bootstrap
Stefan Bodewig bodewig at apache.org writes: On Wed, 27 Oct 2004, Niclas Hedhman niclas at hedhman.org wrote: I have looked at the Kaffe instance and its inability to create the Ant bootstrap. The first level of problem is that the Kaffe compiler doesn't imply any source files that are not specified, and that results in the immense number of Cannot find class. I think the only viable solution is to drop kopi and use jikes as a compiler. The very same problem is likely to come up in javac tasks later on as well. Yes. There already is an issue in Jira for this. Ant's bootstrap script can use jikes easily by setting the JAVAC environment variable. Ah, cool, I didn't know that. Since which version of ant is that the case? I don't know if we should proceed by convincing Ant to introduce this to their codebase, or we should maintain a separate bootstrap script. I'd prefer to really not use kopi at all. I've been told that even the Kaffe people prefer to use Jikes. Yes. the main reason is that kjc is not greedy wrt to resolving missing classes, whereas most other compilers are, so people naturally write build.xml files that don't work with kjc, which needs to be fed all classes on the command line. Any approach like yours will need to be maintained when classes get added to Ant. Sorry for the late reply, I've been busy with some other issues, unfortunately. I'll look into making the bootstrap work with jikes kaffe in debian by setting the JAVAC env var. I've had to solve a similart problem for bootstrapping ant with kaffe jikes in kaffe-extras module of kaffe's CVS. There I've patched ant's bootstrap scripts for that [1] but of course setting env vars is more elegant ;) cheers, dalibor topic [1] http://www.kaffe.org/cgi-bin/viewcvs.cgi/kaffe-extras/patches/ ant-kaffe-1.1.3.diff?annotate=1.2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [proposal] removing non-ASF leaves from the workspace
Adam R. B. Jack wrote: there are a few projects that gump builds that are not ASF projects and are not used by any ASF project. I think the ASF already has enough things to build for ourselves and gump is not a public service. I hear you, but since Gump was a social experiment not an ASF build tool, some of this was reach out. Don't forget that some non-ASF projects that Gump built became ASF projects, e.g. ws-juddi. I'm about to propose that we change that 'social experiment' tagline and we turn this into a more solid thing for the ASF. I personally think that it is abusive for comitters to use their access to add projects that are not required. I don't know as much (partly since I added a few of them ;-). Other folks had the ability to -1 any. We used to run once a day, and as such it wasn't such a big deal. Right, we also used to run at 60%, things are changing. Examples of such projects are Barcode4j, Antworks, Smartfrog, but I'm sure I can found more (and, in fact, I'll write some code to outline those and automate the checks). I propose that we remove those projects from the gump.xml profile that is ran on brutus (we can keep the descriptors there, that doesn't hurt) but I would like to remove all those leaves projects from using cpu/disk space. WTDY? We have grown a lot larger in recent months, and are using a lot more CPU/disk. Further, we are trying to do more than one Gump workspace (JDK1.5, Kaffe, etc.) As such, maybe we do have to trim down. If it helps with that that, then go for it. For Gump to scale (as Niclas mentioned) we do need to federate somehow, but that is a separate topic this seems a practical step until then. Folks who really want to be included could petition us for re-inclusion. I find particularely silly that we have a projects that: 1) are not from the ASF 2) no ASF project depends on 3) and they constantly don't build and nobody seems to care I find the combination of the above enough to remove a project from our builds. -- Stefano. smime.p7s Description: S/MIME Cryptographic Signature
Re: [proposal] removing non-ASF leaves from the workspace
Stefano Mazzocchi wrote: WTDY? The downside of this idea is that ASF projects will lose warnings about incompatible changes they make that break non-ASF projects. IOW, info about downstream breakages can be interesting even if it is not a breakage in an ASF project. I know the I always regarded Gump as a giant test of Ant. Ant probably gets enough coverage just from ASF project builds to not be overly concerned, but other projects may be more affected. Just me 2c Conor - 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]: Project lenya (in module lenya) failed *** G U M P [EMAIL PROTECTED]: Project lenya (in module lenya) failed Failed with to: [EMAIL PROTECTED] from: [Gump] Failed to send notify e-mail: (450, 'FQDN required in the envelope sender', 'Gump') 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 lenya has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - lenya : Content Management System Full details are available at: http://brutus.apache.org/gump/public/lenya/lenya/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://brutus.apache.org/gump/public/lenya/lenya/gump_work/build_lenya_lenya.html Work Name: build_lenya_lenya (Type: Build) Work ended in a state of : Failed Elapsed: 1 sec Command Line: java -Djava.awt.headless=true org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Davalonapi.jar=/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-31102004.jar -Dlogkit.jar=/usr/local/gump/public/workspace/avalon-trunk/runtime/logkit/target/deliverables/jars/avalon-logkit-31102004.jar -Dversion=31102004 gump-core [Working Directory: /usr/local/gump/public/workspace/lenya] CLASSPATH : /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/lenya/build/lenya-31102004/classes:/usr/local/gump/public/workspace/cocoon/build/cocoon-31102004/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-31102004/cocoon-deprecated.jar:/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/avalon-trunk/runtime/logkit/target/deliverables/jars/avalon-logkit-31102004.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-31102004.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-31102004.jar - Buildfile: build.xml BUILD FAILED Target `gump-core' does not exist in this project. Total time: 0 seconds - To subscribe to this information via syndicated feeds: - RSS: http://brutus.apache.org/gump/public/lenya/lenya/rss.xml - Atom: http://brutus.apache.org/gump/public/lenya/lenya/atom.xml == Gump Tracking Only === Produced by Gump version 2.1.0-alpha-0003. Gump Run 17001531102004, brutus:brutus-public:17001531102004 Gump E-mail Identifier (unique within run) #8. -- Apache Gump http://gump.apache.org/ [Instance: brutus] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [proposal] removing non-ASF leaves from the workspace
Conor MacNeill wrote: Stefano Mazzocchi wrote: WTDY? The downside of this idea is that ASF projects will lose warnings about incompatible changes they make that break non-ASF projects. I said: remove non-ASF project that ASF projects don't depend upon. -- Stefano. smime.p7s Description: S/MIME Cryptographic Signature
