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

Re: [Pharo-project] where to report vm crashes? (while running Moose tests)

by phil＠highoctane.be

Eliot as a new VM as of yesterday http://www.mirandabanda.org/files/Cog/VM/VM.r2701/README.2701 That kind of fixes things. But I guess the Pharo team still has to integrate these fixes. BTW, here is the version string from the Cog VM explaining the "too old message": Smalltalk vm version. 'CoInterpreter VMMaker.oscog-eem.272 uuid: 8f4167f2-5bf0-4d90-9b7f-5355c741c68f Mar 11 2013 StackToRegisterMappingCogit VMMaker.oscog-eem.270 uuid: 014f0153-bb02-49b7-b544-d8f3ac2deef6 Mar 11 2013 VM: r2701 http://www.squeakvm.org/svn/squeak/branches/Cog Plugins: r2545 http://squeakvm.org/svn/squeak/trunk/platforms/Cross/plugins ' Obviously different :-) Phil 2013/3/12 Stephan Eggermont <stephan(a)stack.nl>: > Esteban wrote: >> Eliot builds will always have the old vm warning, even if they are not old :)... >> you need one of the pharo builds (CogVM, NBCogVM or PharoVM) > > Well, Doru reported they crashed. Eliot's one doesn't: >> 15875 run, 15472 passes, 2 skipped, 88 expected failures, 216 failures, 99 errors, 0 unexpected passes > > On the other hand, not being able to add a monticello directory repository > is also not helpful. No filedialog is shown (receiver of bitAt: is nil, looks like a problem with > filesystem permissions) > > Stephan

March 12, 2013

Re: [Pharo-project] where to report vm crashes? (while running Moose tests)

by Stephan Eggermont

Esteban wrote: > Eliot builds will always have the old vm warning, even if they are not old :)... > you need one of the pharo builds (CogVM, NBCogVM or PharoVM) Well, Doru reported they crashed. Eliot's one doesn't: > 15875 run, 15472 passes, 2 skipped, 88 expected failures, 216 failures, 99 errors, 0 unexpected passes On the other hand, not being able to add a monticello directory repository is also not helpful. No filedialog is shown (receiver of bitAt: is nil, looks like a problem with filesystem permissions) Stephan

March 12, 2013

Re: [Pharo-project] where to report vm crashes? (while running Moose tests)

by phil＠highoctane.be

Eliot's CogVM vs PharoVM on Mac application contents. Quite different. And worth some explanations :-) Why is it that way? Phil 2013/3/12 Stephan Eggermont <stephan(a)stack.nl>: >>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. > > I started the latest MOOSE image on Eliots latest VM on mac. > It still has the 'old vm' warning. > Adding a monticello repository (directory) doesn't work. > Tests are still running > > Stephan > >

March 12, 2013

[Pharo-project] SmalltalkImage current reportCPUandRAM > DNU

by phil＠highoctane.be

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

March 12, 2013

Re: [Pharo-project] Geometric model in Pharo

by phil＠highoctane.be

You can always have a morph that actually isn't shown. 2013/3/12 Henrik Johansen <henrik.s.johansen(a)veloxit.no>: > > On Mar 12, 2013, at 10:14 AM, Tristan Bourgois wrote: > >> That's totally what I need! Thanks! >> >> But that's not strange to use Morph objects like geometric object? >> >> Tristan. > > Well, the whole point of Morphs was to be "graphical objects" (in other words, objects that also knew how to draw themselves/ be graphically manipulated). > Having geometric objects as Morphs is merely a consequence of that philosophy. > > Whether you prefer a more distinct separation between a model and view of that model than what Morphs were built for, is another matter :) > > Cheers, > Henry

March 12, 2013

Re: [Pharo-project] Geometric model in Pharo

by Henrik Johansen

On Mar 12, 2013, at 10:14 AM, Tristan Bourgois wrote: > That's totally what I need! Thanks! > > But that's not strange to use Morph objects like geometric object? > > Tristan. Well, the whole point of Morphs was to be "graphical objects" (in other words, objects that also knew how to draw themselves/ be graphically manipulated). Having geometric objects as Morphs is merely a consequence of that philosophy. Whether you prefer a more distinct separation between a model and view of that model than what Morphs were built for, is another matter :) Cheers, Henry

March 12, 2013

Re: [Pharo-project] [Moose-dev] Re: where to report vm crashes? (while running Moose tests)

by Sven Van Caekenberghe

Camillo, On 12 Mar 2013, at 09:39, Camillo Bruni <camillobruni(a)gmail.com> wrote: > from that point of view, it is just a warning. Unless you do some fancy > new FileSystem stuff it will continue to work with 2.0 and for a while with > 3.0. Is it not possible to clarify *exactly* what is missing and will not work well. Right now this is like a mystery. We are all developers and capable of understanding a technical explanation ;-) Which primitives are we talking about, how are they used and what end user effect do they have ? I know that NativeBoost is an important difference. The question is, will the image start without proper NB support and will something be broken if NB is non-functional (apart from NB code itself, I mean high level normal stuff) ? Thx, Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

March 12, 2013

Re: [Pharo-project] where to report vm crashes? (while running Moose tests)

by phil＠highoctane.be

Eliot's VMs on Mac will always give the warning as the version isn't the same kind of string as Esteban's. Some kind of git thing, like: #define REVISION_STRING "git://gitorious.org/cogvm/blessed.git Commit: 63aa6ed8a070fc730224b496e0dda7c3f8482e10 Date: 2013-02-14 11:43:21 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com>" Phil 2013/3/12 Stephan Eggermont <stephan(a)stack.nl>: >>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. > > I started the latest MOOSE image on Eliots latest VM on mac. > It still has the 'old vm' warning. > Adding a monticello repository (directory) doesn't work. > Tests are still running > > Stephan > >

March 12, 2013

Re: [Pharo-project] Geometric model in Pharo

by Tristan Bourgois

That's totally what I need! Thanks! But that's not strange to use Morph objects like geometric object? Tristan. 2013/3/11 stephane ducasse <stephane.ducasse(a)free.fr>: > > On Mar 11, 2013, at 4:30 PM, Tristan Bourgois <tristan.bourgois(a)gmail.com> wrote: > >> Hi! >> >> I'm actually doing my final-year internship in ThalÃ¨s and I'm porting >> an application, for creating UI, from VisualWorks to Pharo (Using >> Athens :). The problem is they use a geometric model already >> implemented in VisualWorks (Graphics-Geometry package). >> The features which are very important to have is the possibility to >> convert a figure (like a Circle) to a Polyline representation. (They >> use it, for example, to know if the mouse are on a shape) >> >> That there is something in Pharo that I could use? >> > > look at the PolygonMorph and subclasses. > > > > > > This class implements a morph which can behave as four different objects depending on the the following two facts: > - is it OPEN or CLOSED? > - is it SEGMENTED or SMOOTHED. > > 1. The OPEN and SEGMENTED variant looks like polyline. > > 2. The OPEN and SMOOTHED variant looks like spline (kind of curve) > > 3. The CLOSED and SEGMENTED variant looks like polygon. This is actually what you get when you do > PolygonMorph new openInWorld > You get a triangle. See below how to manipulate these objects... > > 4. The CLOSED and SMOOTHED variant looks like blob (???) > > Prototypes of this morph can also be found in "Object Catalog". Several (different variants) of this object are among "Basic" morphs. > > Explore the assiciated morph-menu. It enables you > - to toggle showing of "handles". They make it possible to > - reposition already existing vertices (by moving yellow handles) > - create new vertices (by moving green handles) > - delete already existing vertices (by dragging and dropping one yellow handle closely > nearby the adjacent yellow handle > Handles can be made visible/hidden by shift+leftclicking the morph. This way it is possible > to quickly show handles, adjust vertices and then again hide handles. > - making closed polygon open, i.e. converting it to a curve (and vice versa) > - toggle smoothed/segmented line/outline > - set up custom dashing (for line, curves or borders of closed polygons > - set up custom arrow-heads (for lines resp. curves) > > ------------------------------------------------------------------------------------------ > Implementation notes: > > This class combines the old Polygon and Curve classes. > > The 1-bit fillForm to make display and containment tests reasonably fast. However, this functionality is in the process of being supplanted by balloon capabilities, which should eventually provide anti-aliasing as well. > > wiz 7/18/2004 21:26 > s have made some changes to this class to > > 1) correct some bugs associated with one vertex polygons. > > 2) prepare for some enhancements with new curves. > >

March 12, 2013

Re: [Pharo-project] where to report vm crashes? (while running Moose tests)

by stephane ducasse

> Hi Stef, > > I do not assume that people have to work on my bug reports. > > I simply clarified the confusion: Esteban was asking for a reproducible case and the reproducible steps were right below his email :). > > Btw, you even replied to the first report, but I should have made the title more clear :) Ok :) > > Cheers, > Doru > > > > > On Tue, Mar 12, 2013 at 9:54 AM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > Doru > > You cannot expect people to work when there are on vacation :). > BTW I only saw the second report. > In addition this is why we are building the consortium because our team will not be able to pay one full time engineer in the long > run. > > Many people do not get that this is not granted that we have a vm and system that fully work :) > So help us convincing companies :) > I'm not talking about you. > > > Stef > > >> I do not understand. I sent the mail with a reproducible case twice (one is just below) :) >> >> Is this enough? Could you reproduce it? >> >> Doru >> >> >> On Tue, Mar 12, 2013 at 9:36 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Hi Doru, >> >> We are working hard to try to fix the vm stability issues and users help is the only way we can have enough crash cases to debug. >> Sending a mail to the list with a reproducible case is the best way to help up fix the vm. >> >> Any report is welcomed :) >> >> Esteban >> >> On Mar 12, 2013, at 9:20 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >>> Great. >>> >>> Is there anything I can do to help fixing the problem? (my problem is that I do not even know where to start) >>> >>> As you can imagine this is an important blocker for the Moose team. >>> >>> Cheers, >>> Doru >>> >>> >>> >>> >>> On Mon, Mar 11, 2013 at 9:58 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >>> thanks doru! >>> >>> >>> > Hi, >>> > >>> > Where should I report Pharo VM crashes with Pharo 2.0? >>> >>> here first :) >>> >>> > >>> > 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." >>> > >>> > <crasher.sh> >>> >>> >>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

March 12, 2013