March 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Moose-dev] Re: where to report vm crashes? (while running Moose tests)
by Tudor Girba March 14, 2013

March 14, 2013

It would be good to have a parallel job, but the problem is that you will get a message saying that the VM is too old for the Pharo 2.0 image. Cheers, Doru On Tue, Mar 12, 2013 at 9:05 AM, Usman Bhatti <usman.bhatti(a)gmail.com>wrote: > Doru, > > In the meantime, can we revert to CogVM because currently we cannot see > the status of fixes and we cannot go any further with Moose 4.8 or may be > create parallel jobs on Cog and Pharo vms ? > > > > On Mon, Mar 11, 2013 at 9:53 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi, >> >> Where should I report Pharo VM crashes with Pharo 2.0? >> >> In particular, I wanted to report the problem related to running Moose >> tests from the command line: >> >> --- >> You can reproduce it on Mac, quite consistently: just run the attached >> script (you need to have wget installed), or do it manually: >> >> 1. download and unzip the latest Moose 4.8: >> >> https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/lastSuccessfulBuild/arti… >> 2. download and unzip the latest Pharo VM: >> http://pharo.gforge.inria.fr/ci/vm/pharo/mac/pharo-mac-latest.zip >> 3. execute: >> ./Pharo.app/Contents/MacOS/Pharo ./Moose-latest-dev-4.8.image moosetest >> >> The VM crashes, but there is no trace of the error. >> --- >> >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "It's not what we do that matters most, it's how we do it." >> >> > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- www.tudorgirba.com "Every thing has its own flow"

6 11

[Pharo-project] working moose build
by Tudor Girba March 14, 2013

March 14, 2013

Hi, The Moose build including running tests now works based on the NBCog VM and the latest Pharo 2.0 (built on Ubuntu): https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/lastCompletedBuild/testR… There are 27 test failures. I also tried on OS X using NBCog VM and the there is no crash. This scenario was also confirmed by Stephan although he reported more failures. For reference, we are using the following script on Jenkins: wget --quiet -qO - http://pharo.gforge.inria.fr/ci/script/ciPharo20NBCogVM.sh | bash wget http://pharo.gforge.inria.fr/ci/image/PharoV20.sources ./vm.sh Pharo.image save $JOB_NAME REPO=http://smalltalkhub.com/mc/Moose/Moose/main ./vm.sh $JOB_NAME.image config $REPO ConfigurationOfMoose --install=development ./vm.sh $JOB_NAME.image moosetest --junit-xml-output zip -r $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes PharoV20.sources Cheers, Doru -- www.tudorgirba.com "From an abstract enough point of view, any two things are similar."

2 2

[Pharo-project] [ANN] Amber 0.10 released!
by Nicolas Petton March 13, 2013

March 13, 2013

After a bit more than one year we have finally put together a new release of Amber - the web developer's best friend: http://www.amber-lang.net Yeah, we know, too long time for a release cycle, but we think you will like this release! First - let's run the numbers - since the 0.9.1 release there have been over 850 commits (compared to 250 for 0.9.1). We have closed 364 issues and added 150 new unit tests bringing us to 271 in total. All classes in the kernel now have comments and there are Travis jobs to keep us all in line. Forks on github have gone up from 43 to 83 with 365 followers. Phew. And what goodies does this give us? Well, first Nicolas got carried away with compiler technology (must have read a book or something) and added a whole new Super Duper compiler tool chain providing both an AST with annotations and an Intermediate Representation layer (IR) enabling semantic analysis and easier optimizations, a better inlining mechanism, support for block contexts (whoa!) and an AST interpreter to round it off. Wait a minute, what? An interpreter? Why on earth would we want a... oh. To be able to implement a full stepping debugger of course (coming in 1.0). Baddabing! Just the new compiler tool chain would have been enough for a release, but since Nicolas is not the only Elf in Amber land this release also includes SUnit improvements and cleanup with support for async assertions, a new build system based on gruntjs replacing the old makefiles (seems slicker in the land of JS), an improved ClassBuilder with better class migration support and a new amberc compiler written in Amber instead of that ghastly bash script... (deep breath) ...and an improved loader to be able to use 3rd party packages, improved kernel classes, and updated documentation. And we also split the github repo into three separate repos - Amber itself, the examples and the website - and yeah, the website got a new look. ...and a whole new IDE is brewing called Helios (in the helios branch). But nah, sorry, Helios will land in 1.0. :) We hope you join us in developing Amber and having fun! Fork at github, join in #amber-lang on freenode and hop onto the mailing list. /the Amber crew

1 0

[Pharo-project] [update 2.0] #20590
by Esteban Lorenzano March 13, 2013

March 13, 2013

20590 ----- Issue 7345: DNU with Glamour: PaginatedMorphTreeMorph>>setSelectedMorph: https://code.google.com/p/pharo/issues/detail?id=7345 https://pharo.fogbugz.com/f/cases/7282 Diff information: http://ss3.gemstone.com/ss/Pharo20/Morphic-EstebanLorenzano.1372.diff

1 0

[Pharo-project] Getting SoundRecorder to work: how?
by phil＠highoctane.be March 13, 2013

March 13, 2013

sr := SoundRecorder new. sr startRecording. sr stopRecording. sr playback. doesn't seem to do anything properly and gives me a DNU inside the playback... Clues? Phil

4 7

[Pharo-project] WhatsUp from: 2013-03-11 until: 2013-03-24
by Torsten Bergmann March 13, 2013

March 13, 2013

> ### Here's what I've been up to since the last WhatsUp: > > - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS - provided the config for simple persistence directly on the config browser - provided a "ConfigurationOfDeveloperWorkspace" in the config browser to make Pharo a more enjoyable environment for first time users - adopted SQLite3 to use latest FFI 2.7 config - changed SQLite3 tests to use the latest file API of Pharo 2.0 - migrated ScriptManager and SQLite3 and made them available on config browser - as ever providing some new on astares.blogspot.de - lurking on the squeak google hangout listening to Eliot and Jecel talking about VM magic > ### What's next, until 2013-03-24 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION - migrating more packages/configs to squeaksource and config browser - working on an own seaside app Bye T.

1 0

[Pharo-project] SmalltalkImage current reportCPUandRAM > DNU
by phil＠highoctane.be March 13, 2013

March 13, 2013

LogFullTally.txt cannot be produced. Weird that Smalltalk vm getParameters would give such a strange collection as shown in the left explorer. Phil

2 2

[Pharo-project] Debugger-driven development (was Re: WhatsUp from: 2013-03-11 until: 2013-03-24)
by Frank Shearar March 12, 2013

March 12, 2013

On 12 March 2013 22:41, Stephan Eggermont <stephan(a)stack.nl> wrote: > ### Here's what I've been up to since the last WhatsUp: > - Accepted proposal to show debugger-driven TDD at Devnology meetup April 3 in Eindhoven (+Willem van den Ende) I'd love to hear more about your presentation. I've been thinking how to run a kind've live-coding demonstration at work, showing how a Smalltalk debugger is so clearly superior to what other folk have. (Squeak trunk now lets you create methods not just on an MNU but also where people have things like "self subclassResponsibility", "self notYetImplemented" or "self shouldBeImplemented" flags such that you can debug-edit-and-continue.) frank

1 0

March 12, 2013

Dear Pharoers last january I visited another lab and I realised that the Pharo Team was not good at systematically telling what we were doing. I got quite frustrated by that situation, especially because we are working hard to build a better system. So we brainstormed when I came back and we want to apply the same ideas that what we do for our research team. For our research team every monday we get a simple mail that tell us to say to the others what we did and what we plan to do. Simple, easy. Then after people of the rmod team can discuss if they want more. We want to do the same with pharo. Often this is not that we are not doing things. Often we are doing boring, tedious stupid but $^%&&*^ important tasks and we want that you know it. In addition we want to share on what we are weekly working. So that you can be more engaged to join and collaborate with us. So we will launch an experience and see. For now we will send a notification every two weeks. the Pharo Team

8 9

Re: [Pharo-project] WhatsUp from: 2013-03-11 until: 2013-03-24
by Stephan Eggermont March 12, 2013

March 12, 2013

### Here's what I've been up to since the last WhatsUp: - Added a storymap view to StoryBoard. Stories can now be added to a goal of a stakeholder. (+Diego Lont) - Accepted proposal to show debugger-driven TDD at Devnology meetup April 3 in Eindhoven (+Willem van den Ende) - Created proposal for a distributed issue tracker GSoC with Diego - Did a spike for a distributed issue tracker with Diego - Convinced Diego to go to Pharo & Moose Days and show TutorialBrowser & Data Conversion with MOOSE - Did a spike with a gherkin glamour browser, tried moving it to latest pharo/MOOSE/vm :) ### What's next, until 2013-03-24 (*): - publish distributed issue tracker spike - prepare presentations with Diego - parse gherkin files, visualize as roassal nested polymetric views Stephan

1 0