Re: What to do with vmgump2?
On 2011-06-08, Stefan Bodewig wrote: On 2011-06-03, Stefan Bodewig wrote: The machine has been sitting unmaintained for a while now and I think we should decide what to do with it. From the top of my head I see two options: * give it back to infra * run Gump on OpenJDK 7 once it is released but maybe anybody else around has another idea. Unless anybody yells I'll start the process of handing it back to infra next week. Done Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
What to do with vmgump2?
Hi all, a few month ago I asked for a second Ubuntu VMWare image for Gump to run on top of Harmony rather than Oracle's or OpenJDK's stack. It took some time until the machine was ready and the people interested in Harmony land have lost time for/interest in the experiment by then. The machine has been sitting unmaintained for a while now and I think we should decide what to do with it. From the top of my head I see two options: * give it back to infra * run Gump on OpenJDK 7 once it is released but maybe anybody else around has another idea. Please note that we'd need to maintain the machine if we don't give it back and my time for anything Apache has been limited as of lately (which makes me prefer the give it back option myself). Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: vmgump2
On 2010-09-23, Leo Simons wrote: I had some fun trying to dig through the codebase to try and remember what's what...hoo boy, this certainly isn't how I'd write python code today :) The Gump code base is a collection of first Python project of a Java programmer pieces from three or four people. Nevertheless I think it may be safe to disable # Add Historical Database storer -- ??? no such thing... if self.run.getOptions().isOfficial() and \ self.run.getWorkspace().hasDatabaseInformation() and \ self.run.getOptions().isHistorical(): try: import gump.actor.history.historical self.run.registerActor( gump.actor.history.historical.Historical(self.run)) except Exception, details: self.log.warning( 'Unable to register Historical Database Actor : %s ' % details, exc_info=1) # Add Dynagump database populator if self.run.getWorkspace().hasDatabaseInformation(): # create the database helper dbInfo = self.run.getWorkspace().getDatabaseInformation() from gump.util.mysql import Database database = Database(dbInfo) # now create the Dynagumper using that database import gump.actor.mysql.dynagumper self.run.registerActor( gump.actor.mysql.dynagumper.Dynagumper(self.run,database)) in https://svn.apache.org/repos/asf/gump/trunk/python/gump/core/runner/runner.py Agreed. that may help get rid of some confusing warnings? We used to get funny error messages when isHistorical returned true on the FreeBSD machine since there have been two isHistorical methods in the same class and it depended on the platform which of the two methods was called[1]. This is why I like compilers to catch my errors and have made a habit out of running pylint on python code before I check it in. Dynagumper is a an actor that doesn't do anything so it doesn't hurt too much either. Stefan [1] http://svn.apache.org/viewvc/gump/trunk/python/gump/core/run/options.py?r1=988801r2=988804 - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: vmgump2
Hey guys, On 8/9/10 5:17 AM, Stefan Bodewig wrote: On 2010-08-08, Stefan Bodewig wrote: vmgump2 sends nag emails to me right now, but if the current run works like I expect it to, I'll enable nagging there and turn off nagging on vmgump. Done now. Starting midnight GMT vmgump2 will take over as the official machine. Just checking in after ignoring my e-mail for some 2 months (*). Sorry I missed all the fun! Awesome work, though! Are you guys all up and running again now or is there anything more that needs attention? For example did you figure out the wonders of mysql to the degree you wanted to? Let me know. cheers, Leo (*) I can totally recommend it ;) - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: vmgump2
On 2010-09-20, Leo Simons wrote: Just checking in after ignoring my e-mail for some 2 months (*). Sounds great. Are you guys all up and running again now or is there anything more that needs attention? Gump is happily running on the new VM as well as on a new FreeBSD zone by now. For example did you figure out the wonders of mysql to the degree you wanted to? More than I wanted to, I'd say. If you happen to recall the specifics around the historical databaser or the dynagump actors it would be nice if you could referesh my memory - but both work as well as they did before (i.e. not at all). Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
vmgump2
Hi, we've gotten a new virtual machine running Ubuntu 10.4 that is going to replace the current vmgump main machine. It is currently building at the results are at http://vmgump2.apache.org/gump/public/. The current run is expected to fix a few problems of the last run where I tried to use Maven 1.1 instead of 1.0.2 for Maven 1.x builds - it just didn't work out. Right now it uses OpenJDK6 (64bit) instead of the Sun JVM vmgump used. There are a few build errors that I think stem from this (IMHO at least Batik and dist-xerces) - we could either keep with OpenJDK and see whether the projects are able to adapt or install the Oracle JVM for Linux, I'm not sure what the best option will be. vmgump2 sends nag emails to me right now, but if the current run works like I expect it to, I'll enable nagging there and turn off nagging on vmgump. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
