- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] why we removed debugTest from nautilus?

by Ben Coman

>From the perspective of a TestCase... * "running" a test wraps execution in error handling so it can log errors without TestRunner breaking open a debugger. * "debugging" executes without that error handling so an error breaks open a debugger. The functionality required is that a debugger opens immediately on the first line of the test method. cheers -ben On Sun, Apr 12, 2015 at 3:35 AM, Max Leske <maxleske(a)gmail.com> wrote: > > On 11 Apr 2015, at 21:31, Ben Coman <btc(a)openinworld.com> wrote: > > > > On Sun, Apr 12, 2015 at 3:07 AM, Ben Coman <btc(a)openinworld.com> wrote: > >> Returning to build 40486 which exhibits the freeze, as a first step, why >> don't we replace all that complicated stack manipulation stuff with... >> >> NautilusUI>>debugTest: aMethod >> [ aMethod methodClass debug: aMethod selector ] fork. >> >> > Sorry. Pretend I didn't say that. That is the <run test> behaviour. > > > Really? Why does it send #debug: then?? > > cheers -ben > > >

April 11, 2015

Re: [Pharo-dev] why we removed debugTest from nautilus?

by Max Leske

> On 11 Apr 2015, at 21:31, Ben Coman <btc(a)openinworld.com> wrote: > > > > On Sun, Apr 12, 2015 at 3:07 AM, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: > Returning to build 40486 which exhibits the freeze, as a first step, why don't we replace all that complicated stack manipulation stuff with... > > NautilusUI>>debugTest: aMethod > [ aMethod methodClass debug: aMethod selector ] fork. > > > Sorry. Pretend I didn't say that. That is the <run test> behaviour. Really? Why does it send #debug: then?? > cheers -ben >

April 11, 2015

Re: [Pharo-dev] why we removed debugTest from nautilus?

by Max Leske

> On 11 Apr 2015, at 21:07, Ben Coman <btc(a)openinworld.com> wrote: > > Returning to build 40486 which exhibits the freeze, as a first step, why don't we replace all that complicated stack manipulation stuff with... > > NautilusUI>>debugTest: aMethod > [ aMethod methodClass debug: aMethod selector ] fork. I donât see any immediate losses. Even the stack should look fine I guess (top context is the one we want etc.). > > cheers -ben > > On Sun, Apr 12, 2015 at 1:31 AM, ClÃ©ment Bera <bera.clement(a)gmail.com <mailto:bera.clement@gmail.com>> wrote: > > > 2015-04-11 1:10 GMT-07:00 Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>>: > > > 2015-04-10 17:28 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com <mailto:bera.clement@gmail.com>>: > Well I guess I used to click proceed and not close the debugger... > > > I don't know who is working on the breakpoint support and I don't know how long it will take. > Maybe we can fix thie image freeze and re-include the debugtest code until the new breakpoint support. > > what do you think? > > > I think break points were done by Clara Allende. As far as I know, they work but there's no IDE support for them. I think they are not ready for this release but I am not sure about the status. Marcus can confirm it will not be ready. > > Yes this image freeze could be fixed but I can't really work on the Pharo release this week (I'm working with Eliot on Cogit...). I could review the fix if you want just tagged me in fogbugz. > > 2015-04-10 1:24 GMT-07:00 Max Leske <maxleske(a)gmail.com <mailto:maxleske@gmail.com>>: > > For a little more context: the issue was originally raised by Clara in the thread titled "MNU: receiver of "stepToCallee:" is nilâ. IIRC the issue was easily reproducible when debugging a test, then closing the debugger (via the close icon). Clicking âProceedâ on the other hand gracefully terminated the process. > > Cheers, > Max > > >> On 10 Apr 2015, at 09:56, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: >> >> 2015-04-10 2:37 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com <mailto:bera.clement@gmail.com>>: >> I was using it frequently too and I have never experienced any issues... >> >> Ok, can you describe a use case, what test case you can start and >> close the debugger without image freeze? >> >> Maybe we can find what is the difference between that >> test case and those that freeze the image, and than find a fix. >> >> >> 2015-04-09 14:58 GMT-07:00 Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>>: >> >> >> 2015-04-09 23:38 GMT+02:00 phil(a)highoctane.be <mailto:phil@highoctane.be> <phil(a)highoctane.be <mailto:phil@highoctane.be>>: >> No Debug Tests? >> >> Geez, I am using that all the time. >> >> And you're never encountered this issue 14689 <https://pharo.fogbugz.com/default.asp?14689>? >> Or did this work in older versions? >> >> >> >> >> Phil >> >> >> On Thu, Apr 9, 2015 at 10:21 PM, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> >> > On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean(a)clipperadams.com <mailto:sean@clipperadams.com>> wrote: >> > >> > Nicolai Hess wrote >> >> http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-… <http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-…> >> > >> > Ah, I miss that too! From that thread, it seems it was removed temporarily >> > until we have real breakpoints. Is there an issue for its return? >> > >> >> Not yet. >> >> Marcus >> >> >> >> > > > > >

April 11, 2015

Re: [Pharo-dev] why we removed debugTest from nautilus?

by Ben Coman

On Sun, Apr 12, 2015 at 3:07 AM, Ben Coman <btc(a)openinworld.com> wrote: > Returning to build 40486 which exhibits the freeze, as a first step, why > don't we replace all that complicated stack manipulation stuff with... > > NautilusUI>>debugTest: aMethod > [ aMethod methodClass debug: aMethod selector ] fork. > > Sorry. Pretend I didn't say that. That is the <run test> behaviour. cheers -ben

April 11, 2015

Re: [Pharo-dev] why we removed debugTest from nautilus?

by Ben Coman

Returning to build 40486 which exhibits the freeze, as a first step, why don't we replace all that complicated stack manipulation stuff with... NautilusUI>>debugTest: aMethod [ aMethod methodClass debug: aMethod selector ] fork. cheers -ben On Sun, Apr 12, 2015 at 1:31 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > > 2015-04-11 1:10 GMT-07:00 Nicolai Hess <nicolaihess(a)web.de>: > >> >> >> 2015-04-10 17:28 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: >> >>> Well I guess I used to click proceed and not close the debugger... >>> >> >> >> I don't know who is working on the breakpoint support and I don't know >> how long it will take. >> Maybe we can fix thie image freeze and re-include the debugtest code >> until the new breakpoint support. >> >> what do you think? >> >> > I think break points were done by Clara Allende. As far as I know, they > work but there's no IDE support for them. I think they are not ready for > this release but I am not sure about the status. Marcus can confirm it will > not be ready. > > Yes this image freeze could be fixed but I can't really work on the Pharo > release this week (I'm working with Eliot on Cogit...). I could review > the fix if you want just tagged me in fogbugz. > >> >>> 2015-04-10 1:24 GMT-07:00 Max Leske <maxleske(a)gmail.com>: >>> >>> For a little more context: the issue was originally raised by Clara in >>>> the thread titled "MNU: receiver of "stepToCallee:" is nilâ. IIRC the >>>> issue was easily reproducible when debugging a test, then closing the >>>> debugger (via the close icon). Clicking âProceedâ on the other hand >>>> gracefully terminated the process. >>>> >>>> Cheers, >>>> Max >>>> >>>> >>>> On 10 Apr 2015, at 09:56, Nicolai Hess <nicolaihess(a)web.de> wrote: >>>> >>>> 2015-04-10 2:37 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: >>>> >>>>> I was using it frequently too and I have never experienced any >>>>> issues... >>>>> >>>> >>>> Ok, can you describe a use case, what test case you can start and >>>> close the debugger without image freeze? >>>> >>>> Maybe we can find what is the difference between that >>>> test case and those that freeze the image, and than find a fix. >>>> >>>> >>>>> >>>>> 2015-04-09 14:58 GMT-07:00 Nicolai Hess <nicolaihess(a)web.de>: >>>>> >>>>> >>>>>> 2015-04-09 23:38 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: >>>>>> >>>>>>> No Debug Tests? >>>>>>> >>>>>>> Geez, I am using that all the time. >>>>>>> >>>>>> >>>>>> And you're never encountered this issue 14689 >>>>>> <https://pharo.fogbugz.com/default.asp?14689>? >>>>>> Or did this work in older versions? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> Phil >>>>>>> >>>>>>> >>>>>>> On Thu, Apr 9, 2015 at 10:21 PM, Marcus Denker < >>>>>>> marcus.denker(a)inria.fr> wrote: >>>>>>> >>>>>>>> >>>>>>>> > On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean(a)clipperadams.com> >>>>>>>> wrote: >>>>>>>> > >>>>>>>> > Nicolai Hess wrote >>>>>>>> >> >>>>>>>> http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-… >>>>>>>> > >>>>>>>> > Ah, I miss that too! From that thread, it seems it was removed >>>>>>>> temporarily >>>>>>>> > until we have real breakpoints. Is there an issue for its return? >>>>>>>> > >>>>>>>> >>>>>>>> Not yet. >>>>>>>> >>>>>>>> Marcus >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>>> >>> >> >

April 11, 2015

Re: [Pharo-dev] [Urgent]: Clean up Download Instructions before 4.0 Release

by Sean P. DeNigris

Peter UhnÃ¡k wrote > it should be written on the > download page - so new debian people can decide what to choose and why > they > should choose one or the other. Agreed, I've updated https://github.com/pharo-project/pharo-workingRoadmaps/blob/master/Download… to split GNU/Linux into more relevant categories: ### Ubuntu Follow PPA instructions - Link to new Launcher tutorial ### Debian (jessie and later) Can we make a deb from the PPA? See https://wiki.debian.org/CreatePackageFromPPA ### Distributions with glibc < 2.15 [Former Debian instructions] ----- Cheers, Sean -- View this message in context: http://forum.world.st/Urgent-Clean-up-Download-Instructions-before-4-0-Rele… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 11, 2015

Re: [Pharo-dev] [Urgent]: Clean up Download Instructions before 4.0 Release

by Sean P. DeNigris

Peter UhnÃ¡k wrote > (especially considering the build is 6 months old and unlike pharo-vm > master branch I > don't see any newer version). I'm assuming it's only building the stable VM, which was last updated 9/26, so that explains its age. Peter UhnÃ¡k wrote > why is there a separate zeroconf for debian downloading some "swing" vm? I think the confusion comes from the name. If we are building this for old libC, let's call it that. The vanilla GNU/Linux VM is named Pharo-VM-linux-stable.zip, so let's name the swing version Pharo-VM-linux-old_libC-stable.zip Also, what is preventing us from building the glibc 2.15 version on our CI? If we still can't, can we at least pick up the VM and: 1. mirror it at files.pharo.org 2. build a Pharo Launcher with it ----- Cheers, Sean -- View this message in context: http://forum.world.st/Urgent-Clean-up-Download-Instructions-before-4-0-Rele… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 11, 2015

Re: [Pharo-dev] [Urgent]: Clean up Download Instructions before 4.0 Release

by Peter UhnÃ¡k

On Sat, Apr 11, 2015 at 8:13 PM, Bernardo Ezequiel Contreras < vonbecmann(a)gmail.com> wrote: > Peter, > here is the announcement > > http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2014-September/1… > Yeah, this is exactly what I had in mind; it should be written on the download page - so new debian people can decide what to choose and why they should choose one or the other. Peter

April 11, 2015

Jenkins Not Compiling Launcher Chapter`

by Sean P. DeNigris

https://ci.inria.fr/pharo-contribution/job/PharoBookWorkInProgress/22/artif… only contains the .pillar file - no html, pdf, etc. Anyone know why? I nosed through the config, build script, and console output but didn't see anything obvious. Thanks. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Jenkins-Not-Compiling-Launcher-Chapter-tp4819089.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 11, 2015

Re: [Pharo-dev] [Urgent]: Clean up Download Instructions before 4.0 Release

by Jigyasa Grover

Apologies. The link to the tutorial is : https://github.com/SquareBracketAssociates/PharoInProgress/tree/master/Phar… . On Sat, Apr 11, 2015 at 11:48 PM, Jigyasa Grover <grover.jigyasa1(a)gmail.com> wrote: > As discussed, a tutorial for Pharo Launcher ( > https://github.com/SquareBracketAssociates/PharoInProgress/pull/5) has > been included in Pharo In Progress under the guidance of Mr. Sean DeNigris. > Kindly review it and post in your suggestions/comments. > Thanks > Jigyasa Grover > > On Sat, Apr 11, 2015 at 11:43 PM, Bernardo Ezequiel Contreras < > vonbecmann(a)gmail.com> wrote: > >> Peter, >> here is the announcement >> >> http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2014-September/1… >> >> made by Jan Vrany. you can ask him. >> >> >> >> On Sat, Apr 11, 2015 at 4:37 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >>> On Sat, Apr 11, 2015 at 5:31 AM, Bernardo Ezequiel Contreras < >>> vonbecmann(a)gmail.com> wrote: >>> >>>> Peter, >>>> The latest vm (http://files.pharo.org/vm/pharo/linux/latest.zip) in >>>> debian wheezy gives you the already know problem >>>> >>>> /lib/i386-linux-gnu/i686/cmov/libc.so.6: *version `GLIBC_2.15' not >>>> found* (required by /home/vonbecmann/workspaces/pharo-40/target/pharo) >>>> >>>> that's why you need the vm ( >>>> https://swing.fit.cvut.cz/jenkins/view/Projects/job/pharo-vm-stable-swing/l…) >>>> that requires glibc 2.13. >>>> >>> >>> Ah, debian stable; I didn't think of that. But does the swing vm support >>> glibc 2.13 _intentionally_ or on accident by just being half a year old? >>> Because it doesn't say that anywhere so as a user I would have no idea of >>> knowing. And since I have debian testing/unstable then I already have glibc >>> 2.19+. And this is why I am that some explanation should be put there. >>> >>> Peter >>> >> >> >> >> -- >> Bernardo E.C. >> >> Sent from a cheap desktop computer in South America. >> > >

April 11, 2015