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

Re: [Pharo-project] [Failing Tests] Cleaned up failing test serialization

by Esteban Lorenzano

yep... something like that :) On Sat, Feb 16, 2013 at 3:25 PM, Ben Coman <btc(a)openinworld.com> wrote: > Camillo Bruni wrote: > >> On 2013-02-16, at 14:14, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >> >> >>> On 2013-02-16, at 14:11, Ben Coman <btc(a)openInWorld.com> wrote: >>> >>> >>> >>>> Marcus Denker wrote: >>>> >>>> >>>>> Hi, >>>>> >>>>> To make it easy to explore why a test fails on the test server we >>>>> serialize the stack of falling tests. >>>>> >>>>> With two changes this has now gotten much easier: >>>>> >>>>> 1) Drag and Drop support for .fuel file >>>>> Just drag the file to the Pharo Desktop --> Debugger opens >>>>> >>>>> >>>>> >>>> Could you advise how to do this from an operational image (that is, not >>>> a CI test image). I would like to use this to demonstrate Pharo's >>>> outstanding development environment. A killer feature would be the >>>> debugger having a <File out> button, that a user could use to mail to >>>> support. Does any other programming system allow this ? >>>> >>>> >>> you can just select "fileout / serialize stack" in the debugger >>> somewhere. >>> The you get a local .fuel file with the serialized stack :) >>> >>> >> >> it's the last entry "File out Stack" in the right-click menu of the >> debugger >> >> >> > Brilliant! I thought the idea was obvious :) > > Now that sparks a following thought, what might be interesting for > customer/support interaction would a mechanism packaging together: > * the serialized stack > * a manifest of all loaded ConfigurationOfXXX versions > * the diff of any dirty ConfigurationOfXXX > subject to user review to avoid leaking proprietary information. > > cheers, Ben > >

Feb. 16, 2013

Re: [Pharo-project] Pharo vm builds restored

by Camillo Bruni

You use the wrong configuration in VMMaker (thanks to the strange naming conventions this happens way too easily) :/ I think you can just use Pharo.*Config instead of Cog.*Config? On 2013-02-16, at 15:18, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > And inside the app, there is a CogVM executable, not a pharo one. > > Confused I am. > > Phil > > 2013/2/16 Camillo Bruni <camillobruni(a)gmail.com>: >> >> On 2013-02-16, at 14:30, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >> >>> Well, this is the script from hell... >>> >>> newImage.sh doesn't executes the last line: >>> >>> # ---------------------------------------------------------------------------- >>> # try to open the image... >>> set -e >>> openImage "$PWD/$VERSION.image" "$PWD/../codegen-scripts/LoadVMMaker.st" >>> rm -rf "$PWD/$VERSION.image" "$PWD/$VERSION.changes"; >>> openImage "$PWD/$generator.image" "$PWD/ImageConfiguration.st" >>> >>> >>> because openImage exits the script... >>> >>> Question: can't we run all of this headless? >> >> >> yes please ;) I guess I never fully tested it under unix/win and nobody really used it >> besides me. >> >> => run everything in headless mode >> => use the zeroconf scripts >> >> >> >

Feb. 16, 2013

Re: [Pharo-project] [Failing Tests] Cleaned up failing test serialization

by Ben Coman

Camillo Bruni wrote: > On 2013-02-16, at 14:14, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > >> On 2013-02-16, at 14:11, Ben Coman <btc(a)openInWorld.com> wrote: >> >> >>> Marcus Denker wrote: >>> >>>> Hi, >>>> >>>> To make it easy to explore why a test fails on the test server we serialize the stack of falling tests. >>>> >>>> With two changes this has now gotten much easier: >>>> >>>> 1) Drag and Drop support for .fuel file >>>> Just drag the file to the Pharo Desktop --> Debugger opens >>>> >>>> >>> Could you advise how to do this from an operational image (that is, not a CI test image). I would like to use this to demonstrate Pharo's outstanding development environment. A killer feature would be the debugger having a <File out> button, that a user could use to mail to support. Does any other programming system allow this ? >>> >> you can just select "fileout / serialize stack" in the debugger somewhere. >> The you get a local .fuel file with the serialized stack :) >> > > it's the last entry "File out Stack" in the right-click menu of the debugger > > Brilliant! I thought the idea was obvious :) Now that sparks a following thought, what might be interesting for customer/support interaction would a mechanism packaging together: * the serialized stack * a manifest of all loaded ConfigurationOfXXX versions * the diff of any dirty ConfigurationOfXXX subject to user review to avoid leaking proprietary information. cheers, Ben

Feb. 16, 2013

Re: [Pharo-project] Pharo vm builds restored

by phil＠highoctane.be

And inside the app, there is a CogVM executable, not a pharo one. Confused I am. Phil 2013/2/16 Camillo Bruni <camillobruni(a)gmail.com>: > > On 2013-02-16, at 14:30, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > >> Well, this is the script from hell... >> >> newImage.sh doesn't executes the last line: >> >> # ---------------------------------------------------------------------------- >> # try to open the image... >> set -e >> openImage "$PWD/$VERSION.image" "$PWD/../codegen-scripts/LoadVMMaker.st" >> rm -rf "$PWD/$VERSION.image" "$PWD/$VERSION.changes"; >> openImage "$PWD/$generator.image" "$PWD/ImageConfiguration.st" >> >> >> because openImage exits the script... >> >> Question: can't we run all of this headless? > > > yes please ;) I guess I never fully tested it under unix/win and nobody really used it > besides me. > > => run everything in headless mode > => use the zeroconf scripts > > >

Feb. 16, 2013

Re: [Pharo-project] Pharo vm builds restored

by phil＠highoctane.be

Still, when doing a cmake . and make in the build/ folder, I do get a CogVM.app in results. Shouldn't I get a Pharo.app? Where is this occuring? Phil 2013/2/16 Camillo Bruni <camillobruni(a)gmail.com>: > > On 2013-02-16, at 14:30, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > >> Well, this is the script from hell... >> >> newImage.sh doesn't executes the last line: >> >> # ---------------------------------------------------------------------------- >> # try to open the image... >> set -e >> openImage "$PWD/$VERSION.image" "$PWD/../codegen-scripts/LoadVMMaker.st" >> rm -rf "$PWD/$VERSION.image" "$PWD/$VERSION.changes"; >> openImage "$PWD/$generator.image" "$PWD/ImageConfiguration.st" >> >> >> because openImage exits the script... >> >> Question: can't we run all of this headless? > > > yes please ;) I guess I never fully tested it under unix/win and nobody really used it > besides me. > > => run everything in headless mode > => use the zeroconf scripts > > >

Feb. 16, 2013

Re: [Pharo-project] Pharo vm builds restored

by phil＠highoctane.be

ZeroConf runs already in another place. It is nice! 2013/2/16 Camillo Bruni <camillobruni(a)gmail.com>: > > On 2013-02-16, at 14:30, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > >> Well, this is the script from hell... >> >> newImage.sh doesn't executes the last line: >> >> # ---------------------------------------------------------------------------- >> # try to open the image... >> set -e >> openImage "$PWD/$VERSION.image" "$PWD/../codegen-scripts/LoadVMMaker.st" >> rm -rf "$PWD/$VERSION.image" "$PWD/$VERSION.changes"; >> openImage "$PWD/$generator.image" "$PWD/ImageConfiguration.st" >> >> >> because openImage exits the script... >> >> Question: can't we run all of this headless? > > > yes please ;) I guess I never fully tested it under unix/win and nobody really used it > besides me. > > => run everything in headless mode > => use the zeroconf scripts > > >

Feb. 16, 2013

Re: [Pharo-project] [Failing Tests] Cleaned up failing test serialization

by Esteban Lorenzano

talking about the debugger... yesterday we were talking about putting also a "report bug" button there, for 3.0 :) Esteban On Feb 16, 2013, at 2:30 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Feb 16, 2013, at 2:30 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > >> >> >> On Sat, Feb 16, 2013 at 10:27 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> > We should >> > >> > -> rename it "Fuel out stack" >> > -> set a post-dematerialization action >> > Because right now drag-and-drop does not lead to any result. >> >> >> >> that is strange.. since I remember Mariano added a post action >> that opens the debugger: >> >> >> But I think Marcus is talking about the button in the debugger, not the HDTestRunner > yes! > > > > Marcus >

Feb. 16, 2013

Re: [Pharo-project] Pharo vm builds restored

by phil＠highoctane.be

sure does. 2013/2/16 Camillo Bruni <camillobruni(a)gmail.com>: > > On 2013-02-16, at 14:25, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > >> I was looking in the image/ folder with the newImage.sh script as I >> wanted to understand what was happening in there. >> >> So, this requires something like $PHAROVM to exist and be set to >> something proper (added to my .profile) >> Then, there is still ci.lille... in there, to be removed. >> >> Next, I wanted to make sense of the script itself. >> >> I commented out the part where the pregenerated image got downloaded >> as I wanted to see things work from zero and not merely a prebuilt >> image. >> >> So, I commented out the prebuilt part. >> >> # ---------------------------------------------------------------------------- >> # echo -e "${YELLOW}LOADING PREBUILT IMAGE" $NO_COLOR >> # echo " $PREBUILT_IMAGE_URL" >> >> # wget $WGET_CERTCHECK "$PREBUILT_IMAGE_URL" --output-document="image.zip" && \ >> # unzip image.zip && \ >> # rm image.zip && \ >> # openImage "$PWD/generator.image" "$PWD/ImageConfiguration.st" && exit 1 >> >> And then, I got: >> >> [PhilMac:~/Documents/Smalltalk/2-MyWorkspaces/workspacePharoVMFebruary2013/buildarea/cog/image >> philippeback$] ./newImage.sh >> FETCHING FRESH IMAGE >> https://ci.inria.fr/pharo/job/Pharo%201.4/lastSuccessfulBuild/artifact/Phar… >> --2013-02-16 14:10:11-- >> https://ci.inria.fr/pharo/job/Pharo%201.4/lastSuccessfulBuild/artifact/Phar… >> >> Which failed. >> >> The right URL is: >> URL="https://ci.inria.fr/pharo/view/Pharo-1.4/job/Pharo-1.4/lastSuccessfulBuild/…" >> >> Also, it seems that the original contents of PharoVM do not contain >> the .sources, and this generates a UI message one has to click, which >> is annoying. >> > > => use the urls from our file server and the new build scripts > > I didn't forgot to update the descriptions since we were out of builds for a while: > > #get a vm: > > wget http://files.pharo.org/script/ciPharoVM.sh > bash ciPharoVM.sh > > #get an image: > > wget http://files.pharo.org/script/ciPharo14.sh > bash ciPharo14.sh > > > => to see what the scripts do run > bash ciPharoVM.sh --help > bash ciPharo14 --help > > => to run an image headlessly do > > ./vm.sh Pharo.image > > => you'll find a complete lists of images under http://files.pharo.org/image/14 > > I hope that helps? > > >

Feb. 16, 2013

Re: [Pharo-project] [Failing Tests] Cleaned up failing test serialization

by Camillo Bruni

On 2013-02-16, at 14:30, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Feb 16, 2013, at 2:30 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > >> >> >> On Sat, Feb 16, 2013 at 10:27 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> We should >>> >>> -> rename it "Fuel out stack" >>> -> set a post-dematerialization action >>> Because right now drag-and-drop does not lead to any result. >> >> >> >> that is strange.. since I remember Mariano added a post action >> that opens the debugger: >> >> >> But I think Marcus is talking about the button in the debugger, not the HDTestRunner sorry, right... if I were fully awake I'd have realized :D

Feb. 16, 2013

Re: [Pharo-project] Pharo vm builds restored

by Camillo Bruni

On 2013-02-16, at 14:30, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > Well, this is the script from hell... > > newImage.sh doesn't executes the last line: > > # ---------------------------------------------------------------------------- > # try to open the image... > set -e > openImage "$PWD/$VERSION.image" "$PWD/../codegen-scripts/LoadVMMaker.st" > rm -rf "$PWD/$VERSION.image" "$PWD/$VERSION.changes"; > openImage "$PWD/$generator.image" "$PWD/ImageConfiguration.st" > > > because openImage exits the script... > > Question: can't we run all of this headless? yes please ;) I guess I never fully tested it under unix/win and nobody really used it besides me. => run everything in headless mode => use the zeroconf scripts

Feb. 16, 2013