- Pharo-dev - lists.pharo.org

[Pharo-project] Can you do this? Re: Automated VM build server
by Mariano Martinez Peck Dec. 19, 2010

Dec. 19, 2010

Hi Igor. I really appreciate your work on this field. I wonder if you or someone could provide (in a future) the following: I would like to be able to download a PharoVM OneClick (or put the name you want), which is a zip with the following: 1) All the platform code of a version XXX. 2) All the src folder with the code generated by ConfigurationOfVMMaker version YYY. 3) Inside the platform folder, for mac, there is always a xcode project. This project file, should be configured so that it takes the sources from the src folder. 4) An squeak/pharo image with VMMaker and plugins loaded. And this has to be loaded by ConfigurationOfVMMaker version YYY 5) The previous image can also have a workspace with the Do-it that was used to generate the src folder. And, this should be pointing to the path ../src And of course, version YYY should work with XXX. If you can provide this, not necessary automaticallly generated all the time, but every some time, this would be awesome. This will let people to: - just open xcode/make and compile a vm - just open the image, change VMMaker, generate sources and then compile a new vm I think this will REALLY increase the people using/developing/learning VM. cheers mariano On Fri, Dec 17, 2010 at 9:17 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > In our nearest plans is make an automated (Hudson based) build setup > for Cog and Squeak VMs. > > All files, which used for building an artifacts should be included in > source code repository. > So, most probably i will add the 'hudson-build' dir at same level as > 'platforms', where scripts and configs will be stored. > > Some changes which i going to do: > - all generated code will be removed from version controlled tree. > Instead of it i will add an information, which will be enough > to reproduce the generated code by taking 3 separate config file(s) > > a) image version (or its URL(s) for download) > b) script for loading VMMaker (of concrete version) + all addons like > FFI , FT2 etc etc into image > c) script for generating the source code using VMMaker image > .. > z) tell me if i miss anything here > > With removing generated source code from repo we now can make sure > that any changes in VMMaker (including code generation itself) > can be tested and can be reproduced by build server at any snapshot > version. > Also, we could test & see if VMMaker loads well and can generate code > using different base images. > So, we will instantly know if any changes in compiler, or other layers > of system is breaking VMMaker. > > Because having a years old image where VMMaker works 100%, but at same > time have 100% chances that it > couldn't be loaded (or even if loaded, but can't run correctly) in > latest image is not what i think good practice for > keeping your house clean. > > > So, by getting rid any intermediate artifacts from build chain we > will be able to make sure that: > - VMMaker loads w/o problems in latest/multiple image(s) > - VMMaker works well and can generate code > > That's means that for any newcomer, loading and building VM will be > much less tedious process, and for 99% > of cases it can be fully automated error free process. > > And let me remind our motto: we're not trying to produce perfect > system/setup from first lucky shot. > We slowly but steady crawling towards improved state of art. > > Any comments, ideas and suggestions are welcome. > > -- > Best regards, > Igor Stasenko AKA sig. > >

2 1

[Pharo-project] [Hudson] Changes
by Marcus Denker Dec. 19, 2010

Dec. 19, 2010

I did some more small incremental changes to the Hudson setup: - Names of the build artitfacts changend (both 1.1 and 1.2) Core: PharoCore-1.2.zip, PharoCore-1.2.changes / PharoCore-1.2.image Full: Pharo-1.2.zip, PharoOneClick1.2.zip and Pharo-1.2.changes / Pharo-1.2.changes.image - zip of image/changes does not contain the build script anymore - One-Click has now the version number in the .app directory name The direkt links (unchanging from now on) are: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/lastSuccessfu… https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/… https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/… -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

Re: [Pharo-project] Graph library in Smalltalk - Need for advices (St?phane Ducasse)
by Ralph Boland Dec. 19, 2010

Dec. 19, 2010

>> May this is a ridiculuous thought but may be it would be good to start an effort on >> build a library for Smalltalk. Reusing some part of mondrian could be good. >> >> It would be very slow and really a lot of work. Mondrian is nice for visualization, but a Graph library is a lot more than that. > But not starting means that we will never have anything. > If there are multiple people needed something this means that they can join forces. > For Moose, mondrian, glamour, petitParser, RB.... nothing came out from a day to the other one > this is just that some guys starred and continued to push. > Stef If there was a basic library for graphs then people who need specific graph algorithm implementations could contribute that implementation once they complete it for their application. By this means a more complete graph library would gradually evolve. All we need for now is a well designed framework for implementing graph algorithms in with implementations of some common algorithms. Regards, Ralph Boland -- Quantum Theory cannot save us from the tyranny of a deterministic universe but it does give God something to do

1 0

[Pharo-project] [update 1.2] #12282
by Marcus Denker Dec. 19, 2010

Dec. 19, 2010

12282 ----- Issue 3456: ENH SUnit ClassFactoryForTestCase Issue 3451: All the packages should have pharo as homw package folder Issue 3415: Failing tests for SUNit Issue 3443: Should remove Sophie Undo classes -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 1

[Pharo-project] Issue 3443 in pharo: Should remove Sophie Undo classes
by pharo＠googlecode.com Dec. 19, 2010

Dec. 19, 2010

Status: Accepted Owner: stephane.ducasse Labels: Milestone-1.2 New issue 3443 by stephane.ducasse: Should remove Sophie Undo classes http://code.google.com/p/pharo/issues/detail?id=3443 Now that we have the new implementation for the undo we should remove the sophie classes.

1 2

[Pharo-project] Issue 3415 in pharo: Failing tests for SUNit
by pharo＠googlecode.com Dec. 19, 2010

Dec. 19, 2010

Status: Accepted Owner: marcus.denker Labels: Milestone-1.2 New issue 3415 by marcus.denker: Failing tests for SUNit http://code.google.com/p/pharo/issues/detail?id=3415 >>> SUnit.Tests.SUnitTest.testExpectedFailure 0.0 50 >>> SUnit.Tests.SUnitTest.testExpectedFailureDetection 0.0 50 >>> SUnit.Tests.SUnitTest.testExpectedFailurePass 0.0 50 These are testsing the expected failures defined by pragmas that we removed because of performance. Tests should be fixed to use oldstyle expected failure definition

1 2

[Pharo-project] preamble in ChangeSet and ChangeRecord
by Max Leske Dec. 19, 2010

Dec. 19, 2010

Hi folks What exactly is the purpose of the preamble in ChangeSet and ChangeRecord? I believe they are not the same for both objects but I haven't been able to figure out what the content of a preamble might actually be. My guess would be that it contains either a comment or a doIt that can check prerequisites. Maybe you could give me an example of how the respective preambles would be used. Thanks, Max

2 2

[Pharo-project] Issue 3451 in pharo: All the packages should have pharo as homw package folder
by pharo＠googlecode.com Dec. 19, 2010

Dec. 19, 2010

Status: Fixed Owner: stephane.ducasse Labels: Milestone-1.2 New issue 3451 by stephane.ducasse: All the packages should have pharo as homw package folder http://code.google.com/p/pharo/issues/detail?id=3451 Else we will have problem to merge. ScriptLoader new cleanRepositories

1 1

[Pharo-project] Issue 3456 in pharo: ENH SUnit ClassFactoryForTestCase
by pharo＠googlecode.com Dec. 19, 2010

Dec. 19, 2010

Status: New Owner: ---- New issue 3456 by bouraqadi: ENH SUnit ClassFactoryForTestCase http://code.google.com/p/pharo/issues/detail?id=3456 The default superclass is put in a dedicated method so it can be redefined in subclasses

1 4

[Pharo-project] [Progress Report] Zinc HTTP Components
by Sven Van Caekenberghe Dec. 19, 2010

Dec. 19, 2010

I am pleased to report another milestone was reached in the Zn project. The default implementation for an HTTP Server is now a multi-threaded (forking) keep-alive implementation called ZnMultiThreadedServer. It passes my initial concurrent load tests. ZnServer is now a facade. This means that all features (test server, static file server, monticello server, seaside adaptor, as well as all unit tests) are now using the new code. In addition, several useful features were added to the servers, including logging and lastRequest/lastResponse debugging hooks. Extra handlers were added to ZnDefaultServerDelegate (favicon, benchmark, random) which double as examples. Next up will be some benchmarking and optimalization. As always, users/testers are most welcome. For more details: http://www.squeaksource.com/ZincHTTPComponents.html http://homepage.mac.com/svc/Zinc-HTTP-Components/index.html http://homepage.mac.com/svc/Zinc-HTTP-Components/getting-started.html Sven

4 16