- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Jenkins] Matrix build for tests and vm

by StÃ©phane Ducasse

really exciting. Software engineering in action with imagination :) Stef On Apr 4, 2012, at 9:22 AM, Marcus Denker wrote: > Hi, > > Christophe changed the Jenkins setup related to testing in a very nice way: > > -> first the current pharo 1.4 is updated to the latest. (as it used to be) > -> new: then we have a Matrix job for running tests on all plattforms. > This is one project, but it spawns test runs on all plattforms (Linux and Mac for now). > https://ci.lille.inria.fr/pharo/view/Build%20pipeline/job/Pharo%201.4%20Tes… > > -> Only if this build is green, it triggers all depending builds. > > see > > https://ci.lille.inria.fr/pharo/view/Build%20pipeline/ > > > The matrix is used already for other things > -> build of Cog: > https://ci.lille.inria.fr/pharo/job/Cog-VM/ > win, linux, mac > -> Testing Cog > https://ci.lille.inria.fr/pharo/job/Cog-VM%20tests/ > (not yet windows) > > This allows us to radically simplify the Jenkins setup and trigger actions > when *all* plattforms are in a good state. > > This will allow us, for example, to automatically update the VM that is used > for running builds and tests or that is packaged in the one-click. > > TODO > -> fix 1.4 so that passing a script to the image works on Windows > -> configure to run tests on windows > -> One-Click build for 1.4 and 1.3 > -> ..... > > So we are getting somewhere! I am sure that 1.5 will be the first Pharo where we > build *the artefact of release* completely automatically and tested from the first > change onwards. > > And this then forms a strong basis that we can build on top. > > Marcus > > -- > Marcus Denker -- http://marcusdenker.de > >

April 4, 2012

Re: [Pharo-project] SMark

by Stefan Marr

Hi Martin: On 03 Apr 2012, at 21:50, Martin Dias wrote: > I like SMark, so I am evaluating how straightforward would be to move Fuel benchmark suite. A couple of questions: > > 1) I had some undeclared references, no problem? > HeadlessSave class>>run: (RVMOperations is Undeclared) > ScriptStarter class>>transportersForFileOutMenu (Transporter is Undeclared) That's not a problem, both are RoarVM related and not necessary for you. [HeadlessSave was meant to make sure that no random processes are in the image anymore before it is saved. The RVMOperations thing I put in was probably for debugging. #transportersForFileOutMenu is something we use to better manage the fileouts with git. Also not relevant for you. Will try to clean these up soon.] > 2) Can I run benchmarks in headless mode using ScriptStarter? How can I try HelloWorld script? I couldn't figure out. Try: /.../../../cog -headless my.image SMarkHarness --help The class comment should also give you an idea how to use it, I hope. The HelloWorld is used similarly: /.../../../cog -headless my.image HelloWorld something something... ScriptStarter registers itself in the startUp handler chain and will try to figure out whether the first argument is a class name, and then perform #run: on the class. You might need to disable the file loader that is normally in your Pharo image. These two are not compatible unfortunately. Good luck Stefan PS: You are the second user for SMark as far as I know. So, please report any rough edges and missing documentation :) Reinout is more lucky, since he is sitting just in the next office ;) > > > Thanks, > MartÃn -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

April 4, 2012

Re: [Pharo-project] Fuel and Pharo Kernel

by Marcus Denker

On Apr 4, 2012, at 9:14 AM, StÃ©phane Ducasse wrote: >> >> >> I do strongly recommend to add Fuel very early in the development of >> 1.5 into the basic kernel packages. > > :) > Marcus added in the todo (BTW he should invite to the todo board we are just opening) to handle the old reference streamâ¦. :) The planning board will be public eventually... first we should finish 1.4. Marcus -- Marcus Denker -- http://marcusdenker.de

April 4, 2012

[Pharo-project] [Jenkins] Matrix build for tests and vm

by Marcus Denker

Hi, Christophe changed the Jenkins setup related to testing in a very nice way: -> first the current pharo 1.4 is updated to the latest. (as it used to be) -> new: then we have a Matrix job for running tests on all plattforms. This is one project, but it spawns test runs on all plattforms (Linux and Mac for now). https://ci.lille.inria.fr/pharo/view/Build%20pipeline/job/Pharo%201.4%20Tes… -> Only if this build is green, it triggers all depending builds. see https://ci.lille.inria.fr/pharo/view/Build%20pipeline/ The matrix is used already for other things -> build of Cog: https://ci.lille.inria.fr/pharo/job/Cog-VM/ win, linux, mac -> Testing Cog https://ci.lille.inria.fr/pharo/job/Cog-VM%20tests/ (not yet windows) This allows us to radically simplify the Jenkins setup and trigger actions when *all* plattforms are in a good state. This will allow us, for example, to automatically update the VM that is used for running builds and tests or that is packaged in the one-click. TODO -> fix 1.4 so that passing a script to the image works on Windows -> configure to run tests on windows -> One-Click build for 1.4 and 1.3 -> ..... So we are getting somewhere! I am sure that 1.5 will be the first Pharo where we build *the artefact of release* completely automatically and tested from the first change onwards. And this then forms a strong basis that we can build on top. Marcus -- Marcus Denker -- http://marcusdenker.de

April 4, 2012

Re: [Pharo-project] [update 1.4] #14419

by StÃ©phane Ducasse

On Apr 4, 2012, at 8:21 AM, Torsten Bergmann wrote: >> Torsten now the NewEcompletion should work. > > Yes, works for me now. Thanks! > > Using "Tools" -> "ConfigurationBrowser" you can > now also easily load the new Seaside 3.0.7 as well. > > No manual typing of Gofer scripts - just click, > load and run. Cool! And soon we want to get all the metacelloRepository config to be loaded, tests run because I always hate catalog of half working projects. Soon we will announce something cool to that respect. :) Stef > > Thanks > T. > -- > NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! > Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a >

April 4, 2012

Re: [Pharo-project] Fuel and Pharo Kernel

by StÃ©phane Ducasse

On Apr 3, 2012, at 10:42 PM, Martin Dias wrote: > Nice :) > > FuelPackageLoader is a functional prototype but needs many improvements. I am elaborating a proposal for GSoC, with features like: > > basic: > - emulate ClassBuilder (implies replacing it for something less monolithic): > - validating the class definition > - modifying an existent class > - recompiling methods (superclass change tolerance) > - mutating existing instances to the new format > - registering the class as a global > - send notifications > - more > - handle dependencies > - good migration support > - visual tool: integrate with Gofer or Monticello? martin writing a new class builder is indeed a really nice and great ideas. > > extra: > - run pre and post scripts (to avoid compilation the scripts should be fully serialized, not just the source code) > - new extension operations: add trait, add variable. > - clean uninstall: if an extension method overwrote an existing one, then it should be restored when package uninstalled (I think in VW is like this). > - ? > > Some items require community discussion, especially the extra ones. Also, I'm not sure what should be in the scope of GSoC. > > Cheers, > MartÃn > > On Tue, Apr 3, 2012 at 5:19 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > On Tue, Apr 3, 2012 at 7:36 PM, Mariano Martinez Peck > <marianopeck(a)gmail.com> wrote: > > > > > > On Tue, Apr 3, 2012 at 6:39 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > > wrote: > >> > >> Hi, > >> > >> I tried the Fuel with Pharo Kernel and... it works well. > > > > > > I am really happy to hear that. > > > >> > >> It needs only > >> very few modifications (removing of some dependencies). > > > > > > Right now I am extremelly busy, but in 2 ways I can spend some time in Fuel. > > If you think that some of these dependencies removal could be applied > > directly to Fuel core, please let us know. > > Hm, I used packages from the Fuel CI image. As I see some things were > changed. For the start, Fuel extensions of classes CharacterBlock and > MetacelloGoferLoad should not be in the basic package. > > > > >> > >> But the really > >> great thing is that the FLPackageLoader seems to work quite well too. > > > > > > Awesome. > > > >> > >> I do strongly recommend to add Fuel very early in the development of > >> 1.5 into the basic kernel packages. > > > > > > Indeed. That was the idea for 1.4 but we didn't have time. > > > >> > >> I can not wait to see a Pharo > >> image without the Compiler ;-) > >> > > > > In fact that was one of the things Stef had in mind when he decided to > > support and push Fuel. Because RMOD is working in boostrap and related works > > where you would like to boostrap and grow without a compiler ;) > > I know, but I expected that package loading in Fuel has much wider > dependencies and that it will require a lot of next work. > > -- Pavel > > > > > > > >> > >> -- Pavel > >> > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > >

April 4, 2012

[Pharo-project] FFI basics..

by S Krish

* How does FFI work for passing a char* argument that gets modified in the invoked module char* ctest ( char* test , char** test2) { test = "Modify this argument"; // loop and fill in data into test2 and return.. return "something else"; } ctest: test <cdecl: char* 'ctest' ( char* , long ) module: 'libctest'> So invoking this with say ExternalAddress allocate: **, gives us the values as modified by the module.. and be converted as required into ByteArray for the second

April 4, 2012

Re: [Pharo-project] Fuel and Pharo Kernel

by StÃ©phane Ducasse

> > > I do strongly recommend to add Fuel very early in the development of > 1.5 into the basic kernel packages. :) Marcus added in the todo (BTW he should invite to the todo board we are just opening) to handle the old reference streamâ¦. :) > > Indeed. That was the idea for 1.4 but we didn't have time. > > I can not wait to see a Pharo > image without the Compiler ;-) the dream will come true :) Since 1998 I want that, it is cool to see the vision getting reality because after we can do a lot more :) > In fact that was one of the things Stef had in mind when he decided to support and push Fuel. Because RMOD is working in boostrap and related works where you would like to boostrap and grow without a compiler ;) Mariano, Pavel knows it too because we talk about that years ago. Stef

April 4, 2012

[Pharo-project] current list of participants to the Pharo Conf :)

by StÃ©phane Ducasse

Hi guys we are excited because we will get a cool group of pharoers and we will meet some of the them for the first time :) I let you guess their names :) Sven you did not register yet :) Stef â¢ Igor â¢ Pavel â¢ Simon â¢ Philippe â¢ Tudor â¢ Nick â¢ Fernando â¢ Johan â¢ Philippe â¢ Nicolas â¢ Nwanguma â¢ Craig â¢ Emmanuel â¢ Guillermo â¢ Francisco â¢ Olivier â¢ Andre â¢ gerard â¢ Joachim â¢ Esteban â¢ Norbert â¢ Hein â¢ Stephan â¢ Noury â¢ Marcus â¢ Nicolas â¢ Veronica â¢ Luc â¢ jean baptiste â¢ Christophe â¢ Nick â¢ Camillo â¢ Usman â¢ Guillaume â¢ Benjamin â¢ Camille â¢ Mariano â¢ Damien â¢ StÃ©phane

April 4, 2012

[Pharo-project] [update 1.4] #14419

by Torsten Bergmann

>Torsten now the NewEcompletion should work. Yes, works for me now. Thanks! Using "Tools" -> "ConfigurationBrowser" you can now also easily load the new Seaside 3.0.7 as well. No manual typing of Gofer scripts - just click, load and run. Cool! Thanks T. -- NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a

April 4, 2012