Re: Moving Gump metadata from CVS to SVN
On Fri, 8 Jul 2005, Adam Jack [EMAIL PROTECTED] wrote: Ought we simple disable CVS metadata updates by default, Yes. enabling SVN by default. With svn:external I believe we automatically pick up the ability to have one SVN update get both code and metadata, so disabling CVS update ought be all we need for us, right? I think we need to remove the metadata directory in the already active workspaces or svn will be unhappy (it will want to create those directories itself). Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SoC update - gump3 and maven
On Mon, 11 Jul 2005, Stefano Mazzocchi [EMAIL PROTECTED] wrote: How about granting our GSoC friends commit access so that they can show us what they are doing? Related, if not completely on-topic. Justin's CLA has not yet been recorded. Until we get there, Justin could provide patches - we will see his code and at the same time get a feeling for how well/bad the send patch get a committer to commit it approach is going to work. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Kaffe gump run
Hi, I am one of the developers of the Kaffe.org VM. I would like to know if there is any chance to get back an automatic gump run on vmgump.apache.org. That was pretty useful to test GNU Classpath Kaffe in interaction with the rest of the other java projects and to detect bugs. Thanks a lot for your job ! Best regards, Guilhem Lavaux. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-test (in module jakarta-commons-sandbox) 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 commons-test has an issue affecting its community integration. This issue affects 5 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Pre-Build Failed'. For reference only, the following projects are affected by this: - apache-ldapber-provider : Apache Directory Project - apacheds-core : Apache Directory Server - apacheds-main : Apache Directory Server - asn1-ber : Apache ASN.1 Tools - commons-test : Commons Test Package Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-test-11072005.jar] identifier set to project name -INFO- Failed with reason pre-build failed -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-test/rss.xml - Atom: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-test/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3611072005, vmgump.apache.org:vmgump-public:3611072005 Gump E-mail Identifier (unique within run) #13. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]: Project commons-test (in module jakarta-commons-sandbox) 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 commons-test has an issue affecting its community integration. This issue affects 5 projects, and has been outstanding for 11 runs. The current state of this project is 'Failed', with reason 'Pre-Build Failed'. For reference only, the following projects are affected by this: - apache-ldapber-provider : Apache Directory Project - apacheds-core : Apache Directory Server - apacheds-main : Apache Directory Server - asn1-ber : Apache ASN.1 Tools - commons-test : Commons Test Package Full details are available at: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [commons-test-11072005.jar] identifier set to project name -INFO- Failed with reason pre-build failed -INFO- Failed to extract fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-test/rss.xml - Atom: http://vmgump.apache.org/gump/public/jakarta-commons-sandbox/commons-test/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3611072005, vmgump.apache.org:vmgump-public:3611072005 Gump E-mail Identifier (unique within run) #13. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Kaffe gump run
Guilhem Lavaux wrote: Hi, Hi Guilhem! I am one of the developers of the Kaffe.org VM. I would like to know if there is any chance to get back an automatic gump run on vmgump.apache.org. Not really :/. That machine is low on disk space so we can't run any more profiles there. We do have a Mac OS X box on which we'll be running gump as well as a Solaris zone. My intention has always been to get a kaffe run set up on one of these, but I've been kind-of busy with other stuff lately :-) That was pretty useful to test GNU Classpath Kaffe in interaction with the rest of the other java projects and to detect bugs. Thanks a lot for your job ! :-). You're welcome! We'll let you know when we have things working, but if I'm the one setting it up that'll be a while yet... cheers, Leo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Kaffe gump run
On Mon, 11 Jul 2005, Guilhem Lavaux [EMAIL PROTECTED] wrote: I would like to know if there is any chance to get back an automatic gump run on vmgump.apache.org. There is not that much left to add to what Leo said. If you had the choice of Solaris or MacOS X, which one would you prefer as a testbed? Stefan - 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]: Project nant (in module nant) failed [EMAIL PROTECTED]: Project cppunit-make (in module cppunit) 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: 41 secs Command Line: svn --quiet update --non-interactive jakarta-commons-sandbox [Working Directory: /usr/local/gump/public/workspace/cvs] - svn: URL 'https://svn.apache.org/repos/asf/jakarta/commons/sandbox/sql/trunk' doesn't exist - 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 3611072005, vmgump.apache.org:vmgump-public:3611072005 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 114 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 3611072005, vmgump.apache.org:vmgump-public:3611072005 Gump E-mail Identifier (unique within run) #2.
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]: Project nant (in module nant) failed [EMAIL PROTECTED]: Project cppunit-make (in module cppunit) 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: 41 secs Command Line: svn --quiet update --non-interactive jakarta-commons-sandbox [Working Directory: /usr/local/gump/public/workspace/cvs] - svn: URL 'https://svn.apache.org/repos/asf/jakarta/commons/sandbox/sql/trunk' doesn't exist - 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 3611072005, vmgump.apache.org:vmgump-public:3611072005 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 114 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 3611072005, vmgump.apache.org:vmgump-public:3611072005 Gump E-mail Identifier (unique within run) #2.
Re: Kaffe gump run
Hi, If Mac OS X means Powerpc, I would prefer Solaris. Mac OS X supports is still uncertain with the JIT (though we are working on it). Solaris/sparc/x86 should work at 99%. The remaining percent being due to some unimplemented feature like Network card interface detection. Thanks ! Guilhem Lavaux. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Kaffe gump run
On Mon, 11 Jul 2005, Guilhem Lavaux [EMAIL PROTECTED] wrote: If Mac OS X means Powerpc, It does. I would prefer Solaris. Solaris x86 is the only option here. Cheers Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Runtime.exec Ant Gump3 (was: Re: svn commit: r210128 - in /gump/branches/Gump3)
So, ehm,
I've had to learn a lot about process management in the last two days,
most importantly that java is *really* bad at doing it properly. If you
open
pygump/python/gump/plugins/java/builder.py
and edit the AntBuilderPlugin to have no_cleanup=False instead of
no_cleanup=True, then do a gump run using the vmgump.xml profile, the
run will usually stall trying to invoke java_cup.
The reason for this seems to be that java sometimes deadlocks when
forked from java. I built a trivial testcase (basically rewrote the
Execute.java from ant to manually run my demo program and wrote a simple
python wrapper to fire that up) and the problem does not occur there, so
I suspect (after stepping through both python and java debuggers for a
whole lot) that something like multi-threading or garbage collection is
in some way significant.
To be clear, this isn't a bug in gump or a bug in ant, but a bug in the
JDK in interaction with a very specific environment. It'll be
interesting to see if, for instance, the same mess doesn't occur when
using Kaffe. I suspect that using any JVM for which Ant's Execute takes
a different approach (ie not using Runtime.exec) makes the problem go
away.
We'll have to see if this becomes a problem or not (eg zombie
processes). I'll try hard to, if we run into issues, produce big and
scary stack traces. My hunch is that we'd have to implement a work
around in Ant...I doubt sun is going to fix their jdk...
cheers,
Leo
[EMAIL PROTECTED] wrote:
* disable process group management for running ant. See inside
gump.plugins.java.builder.AntPlugin for some details. This was a *huge*
pain to figure out. What triggered this is the invocation of java_cup
from the xalan build.xml file, which has a java fork=true.
...
project name=xalan
-module name=xml/
+module name=xml-xalan/
!-- commands --
ant basedir=java target=unbundledjar
@@ -252,6 +263,8 @@
/project
...
+def _do_run_command(self, command, args, workdir, shell=False,
no_cleanup=False):
+# see gump.plugins.java.builder.AntPlugin for information on the
+# no_cleanup flag
+
...
-cmd =
Popen(myargs,shell=False,cwd=workdir,stdout=outputfile,stderr=STDOUT,env=command.env)
+cmd =
Popen(myargs,shell=False,cwd=workdir,stdout=outputfile,stderr=STDOUT,env=command.env,
no_cleanup=no_cleanup)
...
-command.build_log = outputfile.read()
+# we need to avoid Unicode errors when people put in 'fancy
characters'
+# into build outputs
+command.build_log = unicode(outputfile.read(), 'iso-8859-1')
+import tempfile
...
-def _get_new_process_group():
-Get us an unused (or so we hope) process group.
-pid = os.fork()
-gid = pid # that *should* be correct. However, let's actually
- # create something in that group.
-if pid == 0:
-# Child
-
-# ensure a process group is created
-os.setpgrp()
-
-# sleep for ten days to keep the process group around
-# for a while
-import time
-time.sleep(10*24*60*60)
-os._exit(0)
-else:
-# Parent
-
-# wait for child a little so it can set its group
-import time
-time.sleep(1)
-
-# get the gid for the child
-gid = os.getpgid(pid)
-
-return gid
-
-# This is the group we chuck our children in. We don't just want to
-# use our own group since we don't want to kill ourselves prematurely!
-_our_process_group = _get_new_process_group()
+temp_dir = tempfile.mkdtemp(gump_util_executor)
+process_list_filename = os.path.join(temp_dir, processlist.pids)
+def savepgid(filename):
+Function called from Popen child process to create new process
groups.
+os.setpgrp()
+f = None
+try:
+grp = os.getpgrp()
+f = open(filename,'a+')
+f.write(%d % grp)
+f.write('\n')
+finally:
+if f:
+try: f.close()
+except: pass
+
class Popen(subprocess.Popen):
This is a thin wrapper around subprocess.Popen which handles
process group management. The gump.util.executor.clean_up_processes()
@@ -106,35 +109,67 @@
stdin=None, stdout=None, stderr=None,
preexec_fn=None, close_fds=False, shell=False,
cwd=None, env=None, universal_newlines=False,
- startupinfo=None, creationflags=0):
-Create a new Popen instance that delegates to the
-subprocess Popen.
-if not preexec_fn:
-# setpgid to the gump process group inside
[jira] Created: (GUMP-146) Need to run each build against a fresh CVS/SVN tree
Need to run each build against a fresh CVS/SVN tree - Key: GUMP-146 URL: http://issues.apache.org/jira/browse/GUMP-146 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-5 Reporter: Leo Simons Fix For: Gump3-alpha-5 Gump2 has synchronisation functionality where we do a cvs/svn checkout of a project, then copy over that dir into the work area for the actual build. This ensures the build outputs of the last run don't influence the current one. Gump3 needs that functionality as well, probably best implemented by modifying the CvsUpdater and SvnUpdater plugins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (GUMP-146) Need to run each build against a fresh CVS/SVN tree
[ http://issues.apache.org/jira/browse/GUMP-146?page=all ] Leo Simons reassigned GUMP-146: --- Assign To: Adam Jack Need to run each build against a fresh CVS/SVN tree - Key: GUMP-146 URL: http://issues.apache.org/jira/browse/GUMP-146 Project: Gump Type: New Feature Components: Python-based Gump Versions: Gump3-alpha-5 Reporter: Leo Simons Assignee: Adam Jack Fix For: Gump3-alpha-5 Gump2 has synchronisation functionality where we do a cvs/svn checkout of a project, then copy over that dir into the work area for the actual build. This ensures the build outputs of the last run don't influence the current one. Gump3 needs that functionality as well, probably best implemented by modifying the CvsUpdater and SvnUpdater plugins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gump3 is slowly becoming useful
Yay! :-) This is awesome! Having some 'live' data is exactly what we need to make this move forward fast. Thank you. You have *no* idea how hard that was (well, actually, I guess at least adam does :-)). Actually, I suspect we all have an idea about how much it takes, and all you've put in. Along those lines ... I feel we all appreciate how ASF you've handled this project. You really have set the example for how to work openly, with a full archive of history. I feel I've learned a lot from your approach and your efforts here, and I know we'll all look back with gratitude at how you've kicked off this effort. I'm proud to be associated with Gump/Gump3, and I know this is great for the Gump Community. Thank you. regards, Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Runtime.exec Ant Gump3
Stefan Bodewig wrote: On Mon, 11 Jul 2005, Leo Simons [EMAIL PROTECTED] wrote: I suspect that using any JVM for which Ant's Execute takes a different approach (ie not using Runtime.exec) makes the problem go away. Hmm, have you run your tests with the equivalent of exec's vmlauncher=false? I.e. force Execute to use the ShellLauncher even if it is on JDK 1.2? I have now. It doesn't help. But it does give a new bit of info -- the /bin/sh process created by the ShellLauncher stalls as well, before ever firing up a new java process. I.e. we never get beyond return Runtime.getRuntime().exec(cmd, env); on line 736 of Execute.java. My hunch is that we'd have to implement a work around in Ant... I can probably get away with yet another magic property if I know how to cure the problem ;-) It'd be nice to know :-) I've verified that the same problem occurs when running the xalan build through gump on vmgump, so if you want to have a go at figuring it out, that's all set to go :-) cheers, Leo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Runtime.exec Ant Gump3
On Mon, 11 Jul 2005, Leo Simons [EMAIL PROTECTED] wrote: Stefan Bodewig wrote: On Mon, 11 Jul 2005, Leo Simons [EMAIL PROTECTED] wrote: I suspect that using any JVM for which Ant's Execute takes a different approach (ie not using Runtime.exec) makes the problem go away. Hmm, have you run your tests with the equivalent of exec's vmlauncher=false? I.e. force Execute to use the ShellLauncher even if it is on JDK 1.2? I have now. It doesn't help. But it does give a new bit of info -- the /bin/sh process created by the ShellLauncher stalls as well, Likely some thread waiting for the process to read or the process waiting for Ant to write something. There have been some process deadlocks due to streams getting read too early or written too late. You are certainly using Ant's CVS HEAD, aren't you? I've verified that the same problem occurs when running the xalan build through gump on vmgump, so if you want to have a go at figuring it out, that's all set to go :-) I'll try to free up some time, thanks. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Runtime.exec Ant Gump3
Stefan Bodewig wrote: I have now. It doesn't help. But it does give a new bit of info -- the /bin/sh process created by the ShellLauncher stalls as well, Likely some thread waiting for the process to read or the process waiting for Ant to write something. There have been some process deadlocks due to streams getting read too early or written too late. Yeah its something I thought about. I've tried manually sending bits and bytes into some of the unix pipes that get created but without much understanding of all the custom pipe stuff its pretty much impossible to understand. You are certainly using Ant's CVS HEAD, aren't you? Yep. Have also tried using 1.6.2 with the same result. I've verified that the same problem occurs when running the xalan build through gump on vmgump, so if you want to have a go at figuring it out, that's all set to go :-) I'll try to free up some time, thanks. Kewl! LSD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[RT] Gump3 for bootstrapping your entire environment
Gang, ... 00:05:35 INFO Processing LocalRepository: DEFAULT_GUMP_LOCAL_REPOSITORY 00:05:35 INFO Processing LocalModule: gump3-packages 00:05:35 INFO Processing Project: jdk 00:05:35 INFO Processing Project: jaxp 00:05:35 INFO Processing CvsModule: xml-xalan 00:05:35 INFO Processing Project: java_cup 00:05:35 INFO Processing CvsRepository: ant 00:05:35 INFO Processing CvsModule: ant 00:05:35 INFO Processing Project: bootstrap-ant 00:05:35 DEBUG Perform Script:bootstrap,args=,shell=,basedir= on Project: bootstrap-ant 00:05:35 DEBUG Perform Script:bootstrap,args=,shell=,basedir= on Project: bootstrap-ant 00:05:35 INFO Executing command: '/usr/bin/env sh /home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/ant/ant/bootstrap.sh' in directory '/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/ant/ant' 00:06:09 INFO Processing CvsModule: xml-commons 00:06:09 INFO Processing Project: xml-apis 00:06:09 DEBUG Perform Ant:target=jar,buildfile=,basedir=java/external on Project: xml-apis 00:06:09 DEBUG Perform Ant:target=jar,buildfile=,basedir=java/external on Project: xml-apis 00:06:09 DEBUG Perform Ant:target=jar,buildfile=,basedir=java/external on Project: xml-apis 00:06:09 DEBUG CLASSPATH is '/usr/lib/j2se/1.5/lib/tools.jar:/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/DEFAULT_GUMP_LOCAL_REPOSITORY/gump3-packages/jdk/lib/tools.jar:/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/ant/ant/bootstrap/lib/ant.jar:/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/ant/ant/bootstrap/lib/ant-launcher.jar' 00:06:09 DEBUG PATH is '/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/DEFAULT_GUMP_LOCAL_REPOSITORY/gump3-packages/jdk/bin:/usr/lib/j2se/1.4/bin:/home/lsimons/bin:/home/lsimons/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/usr/bin/X11::/home/lsimons/svn/gump/branches/Gump3/' 00:06:09 INFO Executing command: 'java -Xbootclasspath/p:/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/DEFAULT_GUMP_LOCAL_REPOSITORY/gump3-packages/jaxp-1_3-20050622-gump-20050710/jaxp-api.jar:/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/DEFAULT_GUMP_LOCAL_REPOSITORY/gump3-packages/jaxp-1_3-20050622-gump-20050710/dom.jar:/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/DEFAULT_GUMP_LOCAL_REPOSITORY/gump3-packages/jaxp-1_3-20050622-gump-20050710/sax.jar:/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/DEFAULT_GUMP_LOCAL_REPOSITORY/gump3-packages/jaxp-1_3-20050622-gump-20050710/xercesImpl.jar:/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/DEFAULT_GUMP_LOCAL_REPOSITORY/gump3-packages/jaxp-1_3-20050622-gump-20050710/xalan.jar org.apache.tools.ant.Main jar' in directory '/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/xml/xml-commons/java/external' ... Freely translated, it took me about 20 minutes to make it possible to have gump compile binaries it can then use (by modifying the PATH in which subprocesses execute) for building other stuff. Theoretically, this shows that we could have gump compile a GCC to compile a linux environment to chroot in to compile a python to run gump. Practically, It's going to take a while to figure out how to do all that (and we don't want to be bootstrapping GCC, trust me), but this is encouraging. Another cool thin to think about is that if we get gump to build all its prerequisites installation could be made much easier :) cheers, LSD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RT] Gump3 for bootstrapping your entire environment
Leo Simons wrote: Gang, ... 00:05:35 INFO Processing LocalRepository: DEFAULT_GUMP_LOCAL_REPOSITORY 00:05:35 INFO Processing LocalModule: gump3-packages 00:05:35 INFO Processing Project: jdk 00:05:35 INFO Processing Project: jaxp 00:05:35 INFO Processing CvsModule: xml-xalan 00:05:35 INFO Processing Project: java_cup 00:05:35 INFO Processing CvsRepository: ant 00:05:35 INFO Processing CvsModule: ant 00:05:35 INFO Processing Project: bootstrap-ant 00:05:35 DEBUG Perform Script:bootstrap,args=,shell=,basedir= on Project: bootstrap-ant 00:05:35 DEBUG Perform Script:bootstrap,args=,shell=,basedir= on Project: bootstrap-ant 00:05:35 INFO Executing command: '/usr/bin/env sh /home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/ant/ant/bootstrap.sh' in directory '/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/ant/ant' 00:06:09 INFO Processing CvsModule: xml-commons 00:06:09 INFO Processing Project: xml-apis 00:06:09 DEBUG Perform Ant:target=jar,buildfile=,basedir=java/external on Project: xml-apis 00:06:09 DEBUG Perform Ant:target=jar,buildfile=,basedir=java/external on Project: xml-apis 00:06:09 DEBUG Perform Ant:target=jar,buildfile=,basedir=java/external on Project: xml-apis 00:06:09 DEBUG CLASSPATH is '/usr/lib/j2se/1.5/lib/tools.jar:/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/DEFAULT_GUMP_LOCAL_REPOSITORY/gump3-packages/jdk/lib/tools.jar:/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/ant/ant/bootstrap/lib/ant.jar:/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/ant/ant/bootstrap/lib/ant-launcher.jar' 00:06:09 DEBUG PATH is '/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/DEFAULT_GUMP_LOCAL_REPOSITORY/gump3-packages/jdk/bin:/usr/lib/j2se/1.4/bin:/home/lsimons/bin:/home/lsimons/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/usr/bin/X11::/home/lsimons/svn/gump/branches/Gump3/' 00:06:09 INFO Executing command: 'java -Xbootclasspath/p:/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/DEFAULT_GUMP_LOCAL_REPOSITORY/gump3-packages/jaxp-1_3-20050622-gump-20050710/jaxp-api.jar:/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/DEFAULT_GUMP_LOCAL_REPOSITORY/gump3-packages/jaxp-1_3-20050622-gump-20050710/dom.jar:/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/DEFAULT_GUMP_LOCAL_REPOSITORY/gump3-packages/jaxp-1_3-20050622-gump-20050710/sax.jar:/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/DEFAULT_GUMP_LOCAL_REPOSITORY/gump3-packages/jaxp-1_3-20050622-gump-20050710/xercesImpl.jar:/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/DEFAULT_GUMP_LOCAL_REPOSITORY/gump3-packages/jaxp-1_3-20050622-gump-20050710/xalan.jar org.apache.tools.ant.Main jar' in directory '/home/lsimons/svn/gump/branches/Gump3/pygump/work/gump3-test/xml/xml-commons/java/external' ... Freely translated, it took me about 20 minutes to make it possible to have gump compile binaries it can then use (by modifying the PATH in which subprocesses execute) for building other stuff. Theoretically, this shows that we could have gump compile a GCC to compile a linux environment to chroot in to compile a python to run gump. Practically, It's going to take a while to figure out how to do all that (and we don't want to be bootstrapping GCC, trust me), but this is encouraging. Another cool thin to think about is that if we get gump to build all its prerequisites installation could be made much easier :) Boy, this is so cool is starting to hurt :-) (... not to be able to participate!) I wonder how long a 'gump world' of debian would take to run (and whether or not you can reach a 100% ;-) Now, the biggest question of all: does gump3 implement fallback? -- Stefano. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
