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

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

by Esteban Lorenzano

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) On Mar 12, 2013, at 10:05 AM, Stephan Eggermont <stephan(a)stack.nl> wrote: >> 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] where to report vm crashes? (while running Moose tests)

by Tudor Girba

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

Re: [Pharo-project] 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

March 12, 2013

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

by stephane ducasse

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"

March 12, 2013

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

by Usman Bhatti

On Tue, Mar 12, 2013 at 9:39 AM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > not really true... the old vm should appear just in really old vm builds > (there was a bug last week introduced in the last moment that was showing > again the warning, but that is fixed now). > > now... I would really like you to stay using the new vms, and report the > crashes so we can work on them... we cannot blindly fix, you now :) > Agreed, I proposed it because we didn't know when the bug was going to be fixed and with this bug, we do not see the progress of our bug fixes in Moose 4.8. But now that you say you'll have a look today (and hopefully it's fixed today :-), there's no need to create a parallel job on Cog. usman > > Esteban > > On Mar 12, 2013, at 9:22 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > 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" > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > >

March 12, 2013

[Pharo-project] migrating PharoNonCorePackages/Sound to PharoExtras/Sound

by stephane ducasse

Hi guys I will also copy the configuration files from MetacelloRepository. Then I will update these configurations to propose SoundSynthesis SoundScore SoundTools Then I will try to make them work on 2.0 Stef

March 12, 2013

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

by Esteban Lorenzano

I will try it today :) On Mar 12, 2013, at 9:38 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > 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"

March 12, 2013

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

by Esteban Lorenzano

not really true... the old vm should appear just in really old vm builds (there was a bug last week introduced in the last moment that was showing again the warning, but that is fixed now). now... I would really like you to stay using the new vms, and report the crashes so we can work on them... we cannot blindly fix, you now :) Esteban On Mar 12, 2013, at 9:22 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > 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"

March 12, 2013

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

by Camillo Bruni

On 2013-03-12, at 09:22, Tudor Girba <tudor(a)tudorgirba.com> wrote: > 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. 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. So if you just keep it as a backup job that is fine then :) > 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"

March 12, 2013

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

by Tudor Girba

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"

March 12, 2013