Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

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

by Tudor Girba

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"

12 years, 1 month

Re: mini-moose sprint tomorrow

by Usman Bhatti

Can you please send me the fix so that I can give it a try with Glamour and Moose browsers tests? On Fri, Mar 8, 2013 at 2:55 PM, Goubier Thierry <thierry.goubier(a)cea.fr>wrote: > Ok, I have a correction for that. How do I upload it ? > > Technical: if pager is nil in a PaginatedMorphTreeMorph, do a ^ super > update: to recover the original MorphTreeMorph behavior (i.e. a one line > change). > > Hum, I'm unable to try all Galmour tests. I ended with a nice segfault:(. > At least I got GLMUpdateMorphicTest green. > > Thierry > > Le 08/03/2013 14:10, Usman Bhatti a écrit : > >> Hello Thierry, >> >> We are moving Moose to Pharo 2.0 and trying to make build green. There >> was a Glamour-related bug fix in MorphTreeMroph to correct this issue: >> http://code.google.com/p/**moose-technology/issues/**detail?id=905<http://code.google.com/p/moose-technology/issues/detail?id=905> >> >> The fix is integrated in Pharo2.0 and now when loading and running tests >> of Glamour and Moose-related browsers, there are a few failing tests and >> the trail leads to the update method in MorphTreeMorph because the pager >> is nil. Can you please have a look? >> >> You can get the latest dev image of Moose on pharo2.0 here: >> https://ci.inria.fr/moose/job/**Moose-latest-dev-4.8<https://ci.inria.fr/moose/job/Moose-latest-dev-4.8> >> and the problem can be reproduced when running glamour-related tests >> (e.g. GLMUpdateMorphicTest >>testInvalidateSelection). >> >> tx, >> >> Usman >> >> >> >> >> >> On Thu, Mar 7, 2013 at 10:36 PM, Tudor Girba <tudor(a)tudorgirba.com >> <mailto:tudor@tudorgirba.com>> wrote: >> >> Hi, >> >> Great. >> >> In the meantime, I fixed Mondrian and EyeSee to not throw errors. >> The problem was that in Pharo 2.0 Morphs send announcements, and >> these got confused with the specific announcements for Mondrian and >> EyeSee. >> >> Now Glamour has 7 errors but they are all due to the same problem of >> not being able to set the value of a port from outside when >> rendering a list. The issue comes from some internal modifications >> of MorphTreeMorph. It would be cool if someone could take a look at >> this. >> >> There are also a couple of Mondrian tests failing, but they are due >> to Easel accessing a missing class MorphicTextEditor which was >> already deprecated in 1.4. Nevertheless, the Easel is no longer >> really needed because we have one in Glamour. >> >> Cheers, >> Doru >> >> >> On Mar 7, 2013, at 4:26 PM, Usman Bhatti <usman.bhatti(a)gmail.com >> <mailto:usman.bhatti@gmail.com**>> wrote: >> >> > For info. >> > >> > ---------- Forwarded message ---------- >> > From: Usman Bhatti <usman.bhatti(a)gmail.com >> <mailto:usman.bhatti@gmail.com**>> >> > Date: Thu, Mar 7, 2013 at 4:15 PM >> > Subject: mini-moose sprint tomorrow >> > To: RMoD private list <lsehub-staff(a)lists.gforge.**inria.fr<lsehub-staff(a)lists.gforge.inria.fr> >> <mailto:lsehub-staff@lists.**gforge.inria.fr<lsehub-staff(a)lists.gforge.inria.fr> >> >> >> > >> > >> > Now that Moose has moved to SThub and we loading it on Pharo 2.0, >> there are some failing tests in Moose: >> https://ci.inria.fr/moose/job/**Moose-latest-dev-4.8/** >> lastCompletedBuild/testReport/<https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/lastCompletedBuild/testR…> >> > >> > Tomorrow, we will try to make green FAMIX/Moose related tests. >> > >> > The place will be decided at "runtime" according to the number of >> participants. >> > >> > usman >> > >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com> >> >> >> "Every thing has its own flow." >> >> >> >> >> >> > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des Systèmes Temps Réel Embarqués > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

12 years, 1 month

Re: [Pharo-project] WhatsUp from: 2013-03-11 until: 2013-03-24

by Tudor Girba

Actually, I would love to get this mechanism also for Moose. Would it be possible? Cheers, Doru On Mar 12, 2013, at 10:15 PM, Stéphane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Mar 12, 2013, at 9:04 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi, >> >> First of all, I think this is a very cool initiative. > > > thanks > I really hope that it will improve our sharing and community building :) > > Stef > > >> >>> ### Here's what I've been up to since the last WhatsUp: >> >> - Working on getting Moose to work on Pharo 2.0 >> - Extended (and documented) the CommandLineHandler to run multiple tests based on context specific requirements >> - Attracted sponsors for PharoConf + MooseDay to make the event free to attend >> - Annoyed people with requests for giving talks and tutorial at PharoConf + MooseDay >> - Brainstormed and reviewed with Andrei around a very cool (really :)) and modular debugger model >> >>> ### What's next, until 2013-03-24 (*): >>> >>> - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION >>> >>> (*) we'll be expecting results by then ;) >> >> - Find a solution for running Moose on a Pharo 2.0-compatible VM >> - Organize the PharoConf + MooseDay >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "Things happen when they happen, >> not when you talk about them happening." >> >> > > -- www.tudorgirba.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."

12 years, 1 month

Re: WhatsUp from: 2013-03-11 until: 2013-03-24

by Stephan Eggermont

### 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

12 years, 1 month

Importing multiple versions

by Alexandre Bergel

Hi! Alejandro is interesting in visualizing commits of methods along a time line (in the same spirit than Kumpel and Chronia). So far, we have experimented using the data contained in the .changes file. It works well, but this it is not really comfortable and nor reliable. Can Moose be used for this purpose on Smalltalk code? A few years ago I have worked on a Monticello importer. But has someone revived this effort? What would be a reliable solution to import multiple versions of a bunch of Monticello packages? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

12 years, 1 month

Re: Latest pharo issue with Eliot's latest Cog

by Stephan Eggermont

Esteban wrote: >Pharo 2.0 does not work with Eliot builds (and it will not work in some scenarios). >In this case, the main reason is that we rebuild (and use) FilePlugin and it is not >incorporated in Eliot branch of the vm... so the FileDialogWindow will take years to open if opens at all. >You need to use one of our VM builds (anyone from last 6 months to now should work) Ah, I didn't know the differences were already so that we need a Pharo-specific vm. nbcog-mac-latest.zip from 27-11-2012 doesn't crash. 15883 run, 15493 passes, 2 skipped, 88 expected failures, 207 failures, 95 errors, 0 unexpected passes Would it be possible to have the vm warning more informative? Something like "expected FilePlugIn, ..."? Stephan

12 years, 1 month

did we migrate Collection Extensions?

by Stéphane Ducasse

http://www.squeaksource.com/@SLrcvkKbyWk_uj91/ZNU-ZAa5 If this is the case it would be good to say it in the description of the squeaksource project Else I can migrate it. Stef

12 years, 1 month

Re: where to report vm crashes? (while running Moose tests)

by Stephan Eggermont

Phil wrote: >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. This is with 2701. The Moose image is based on Pharo 20589 Stephan

12 years, 1 month

Re: 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

12 years, 1 month

Re: where to report vm crashes? (while running Moose tests)

by Stephan Eggermont

>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

12 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev