- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50003 Home: https://github.com/pharo-project/pharo-core

April 21, 2015

Re: [Pharo-dev] Fwd: exception handling problem when running tests in Nautilus

by Otto Behrens

> We miss a functionality in Pharo to easily run (a shorcut) a set of selected tests (ex: your project tests). This way, you can have a quick feedback on your updates. > As it is not so easy, I often fallback to run tests from Nautilus (a test class or sometimes only a test method). This may be an idea: I once wrote a bit of Smalltalk code inspired by this: http://www.junitmax.com/ We ran it in our dev environment for about 2 years, and took it out when we upgraded to Pharo 3.0. I still miss it. Other members on the project do not, generally. When accepting a method, we ran some tests: 1. lint (on the method) 2. if the changed method is a test method, run it (debug) 3. if not, run at most 5 tests in the vicinity of the changed method (look for some appropriate senders) What we got for this: 1. TDD really beautiful. Accept a test method -> debugger pops up -> write the code in the debugger -> restart -> rinse and repeat. 2. Lint complained instantly. Very useful. As and when. 3. Change domain code: breaking test pops up -> edit code in the debugger! Problems we had: 1. Monkey patching OmniBrowser to do stuff when accepting a method. Work to figure out how in Nautilus :-( 2. Lint became slow. Lots of work to optimise and perhaps exclude some. 3. The responsiveness on accepting a method was just a slight bit slow which put people off 4. Editing in the debugger and lists of methods: no refactoring, no auto-formatting; pain Solutions: 1. Make it run in the background (continuously). Protect from running too often. 2. Get the method list browser and debugger editors to behave the same as Nautilus (at a method level) 3. Record information about failing tests, and run the ones that tend to fail more often 4. Use changes to help with "run tests for stuff that I am working on"

April 21, 2015

Re: [Pharo-dev] [Metacello] Re: [Vm-dev] Fixes to the SqueakSSL Plugin

by Tobias Pape

On 21.04.2015, at 17:20, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > thank you very much! > I will merge it with our branch. Note that the platform-specific files are still dispersed over the vm-dev list. I will put them into Ron's squeakssl repo > > Esteban > >> On 21 Apr 2015, at 16:59, Tobias Pape <Das.Linux(a)gmx.de> wrote: >> >> >> Dear Smalltalkers >> >> Starting with Levente Uzonyi's patches to the Linux version >> of the SqueakSSL-Plugin, we (Marcel Taeumel and me) have >> ported this to the OS X and Windows version as well. >> >> Find three binaries[1] that can be used instead of >> the ones found on versions found on SqueakSSL's google code >> page. >> >> SqueakSSL: >> - x86 32bit Linux ELF dynamic library >> - Contains Levente's SNI feature >> - needs SqueakSSL-ul.29 or equivalent for SNI support >> - can work without. >> - NOT linked against OpenSSL, but >> _statically_ linked against LibreSSL 2.1.6 [2]. >> - It should work on older and newer Debian/Ubuntu as well as on >> CentOS/RedHat/SuSE systems. >> >> SqueakSSL.dll >> - x86 32bit Windows dll (built with Visual Studio 2013) >> - Uses Schannel API >> - SNI Support >> - needs SqueakSSL-ul.29 or equivalent for SNI support >> - can work without. >> - setting an Int property via sqSetIntPropertySSL(...) >> - Unicode problems when extracting the correct peerName in sqExtractPeerName >> >> SqueakSSL.bundle >> - x86 32bit OS X Mach-O dylib (Linked against OS X 10.5 SDK) >> - Uses Security-Framework >> - SNI Support >> - needs SqueakSSL-ul.29 or equivalent for SNI support >> - can work without. >> --------------------------------------------------------------------------------- >> >> The changes necessary for Windows and OS X are not yet available in the >> squeakvm svn, the linux ones are. >> I have not yet found a good way to include the static linking in either >> the way the Autoconf works for Cog or CMake works for the interpreter, >> but I'll follow-up to this. >> >> -------------------------------------------------------------------------------- >> >> Best regards >> -Tobias >> >> >> >> >> [1]: http://forum.world.st/file/n4820846/squeakssl.zip >> [2]: http://www.libressl.org/

April 21, 2015

Re: [Pharo-dev] Fixes to the SqueakSSL Plugin

by Tobias Pape

Hi Ron, On 21.04.2015, at 17:16, Ron Teitelbaum <Ron(a)USMedRec.com> wrote: > Hi Tobias, > > I've ported squeakssl over to github. Thank you very much! > Did you want access to the repo at: > https://github.com/itsmeront/squeakssl/ that would be great. > > You could create a Pharo branch there. I think for the vm stuff we need no Flavor-specifc branches :) Best regards -Tobias > > All the best, > > Ron Teitelbaum

April 21, 2015

Re: [Pharo-dev] [Vm-dev] Fixes to the SqueakSSL Plugin

by Esteban Lorenzano

thank you very much! I will merge it with our branch. Esteban > On 21 Apr 2015, at 16:59, Tobias Pape <Das.Linux(a)gmx.de> wrote: > > > Dear Smalltalkers > > Starting with Levente Uzonyi's patches to the Linux version > of the SqueakSSL-Plugin, we (Marcel Taeumel and me) have > ported this to the OS X and Windows version as well. > > Find three binaries[1] that can be used instead of > the ones found on versions found on SqueakSSL's google code > page. > > SqueakSSL: > - x86 32bit Linux ELF dynamic library > - Contains Levente's SNI feature > - needs SqueakSSL-ul.29 or equivalent for SNI support > - can work without. > - NOT linked against OpenSSL, but > _statically_ linked against LibreSSL 2.1.6 [2]. > - It should work on older and newer Debian/Ubuntu as well as on > CentOS/RedHat/SuSE systems. > > SqueakSSL.dll > - x86 32bit Windows dll (built with Visual Studio 2013) > - Uses Schannel API > - SNI Support > - needs SqueakSSL-ul.29 or equivalent for SNI support > - can work without. > - setting an Int property via sqSetIntPropertySSL(...) > - Unicode problems when extracting the correct peerName in sqExtractPeerName > > SqueakSSL.bundle > - x86 32bit OS X Mach-O dylib (Linked against OS X 10.5 SDK) > - Uses Security-Framework > - SNI Support > - needs SqueakSSL-ul.29 or equivalent for SNI support > - can work without. > --------------------------------------------------------------------------------- > > The changes necessary for Windows and OS X are not yet available in the > squeakvm svn, the linux ones are. > I have not yet found a good way to include the static linking in either > the way the Autoconf works for Cog or CMake works for the interpreter, > but I'll follow-up to this. > > -------------------------------------------------------------------------------- > > Best regards > -Tobias > > > > > [1]: http://forum.world.st/file/n4820846/squeakssl.zip > [2]: http://www.libressl.org/ >

April 21, 2015

Re: [Pharo-dev] Fixes to the SqueakSSL Plugin

by Ron Teitelbaum

Hi Tobias, I've ported squeakssl over to github. Did you want access to the repo at: https://github.com/itsmeront/squeakssl/ You could create a Pharo branch there. All the best, Ron Teitelbaum -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Tobias Pape Sent: Tuesday, April 21, 2015 11:00 AM To: The general-purpose Squeak developers list; Squeak Virtual Machine Development Discussion; Pharo Development List; metacello(a)googlegroups.com Subject: [Pharo-dev] Fixes to the SqueakSSL Plugin Dear Smalltalkers Starting with Levente Uzonyi's patches to the Linux version of the SqueakSSL-Plugin, we (Marcel Taeumel and me) have ported this to the OS X and Windows version as well. Find three binaries[1] that can be used instead of the ones found on versions found on SqueakSSL's google code page. SqueakSSL: - x86 32bit Linux ELF dynamic library - Contains Levente's SNI feature - needs SqueakSSL-ul.29 or equivalent for SNI support - can work without. - NOT linked against OpenSSL, but _statically_ linked against LibreSSL 2.1.6 [2]. - It should work on older and newer Debian/Ubuntu as well as on CentOS/RedHat/SuSE systems. SqueakSSL.dll - x86 32bit Windows dll (built with Visual Studio 2013) - Uses Schannel API - SNI Support - needs SqueakSSL-ul.29 or equivalent for SNI support - can work without. - setting an Int property via sqSetIntPropertySSL(...) - Unicode problems when extracting the correct peerName in sqExtractPeerName SqueakSSL.bundle - x86 32bit OS X Mach-O dylib (Linked against OS X 10.5 SDK) - Uses Security-Framework - SNI Support - needs SqueakSSL-ul.29 or equivalent for SNI support - can work without. ---------------------------------------------------------------------------- ----- The changes necessary for Windows and OS X are not yet available in the squeakvm svn, the linux ones are. I have not yet found a good way to include the static linking in either the way the Autoconf works for Cog or CMake works for the interpreter, but I'll follow-up to this. ---------------------------------------------------------------------------- ---- Best regards -Tobias [1]: http://forum.world.st/file/n4820846/squeakssl.zip [2]: http://www.libressl.org/

April 21, 2015

Re: [Pharo-dev] missing packages in the Pharo50 repository

by Esteban Lorenzano

> On 21 Apr 2015, at 16:39, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > However I think that repositories of this project should be in the > list of default repositories. Maybe we should add copy of the > configurations to the Pharo50 repository too. yes, I agree

April 21, 2015

Fixes to the SqueakSSL Plugin

by Tobias Pape

Dear Smalltalkers Starting with Levente Uzonyi's patches to the Linux version of the SqueakSSL-Plugin, we (Marcel Taeumel and me) have ported this to the OS X and Windows version as well. Find three binaries[1] that can be used instead of the ones found on versions found on SqueakSSL's google code page. SqueakSSL: - x86 32bit Linux ELF dynamic library - Contains Levente's SNI feature - needs SqueakSSL-ul.29 or equivalent for SNI support - can work without. - NOT linked against OpenSSL, but _statically_ linked against LibreSSL 2.1.6 [2]. - It should work on older and newer Debian/Ubuntu as well as on CentOS/RedHat/SuSE systems. SqueakSSL.dll - x86 32bit Windows dll (built with Visual Studio 2013) - Uses Schannel API - SNI Support - needs SqueakSSL-ul.29 or equivalent for SNI support - can work without. - setting an Int property via sqSetIntPropertySSL(...) - Unicode problems when extracting the correct peerName in sqExtractPeerName SqueakSSL.bundle - x86 32bit OS X Mach-O dylib (Linked against OS X 10.5 SDK) - Uses Security-Framework - SNI Support - needs SqueakSSL-ul.29 or equivalent for SNI support - can work without. --------------------------------------------------------------------------------- The changes necessary for Windows and OS X are not yet available in the squeakvm svn, the linux ones are. I have not yet found a good way to include the static linking in either the way the Autoconf works for Cog or CMake works for the interpreter, but I'll follow-up to this. -------------------------------------------------------------------------------- Best regards -Tobias [1]: http://forum.world.st/file/n4820846/squeakssl.zip [2]: http://www.libressl.org/

April 21, 2015

Re: [Pharo-dev] Fwd: exception handling problem when running tests in Nautilus

by Christophe Demarey

Le 21 avr. 2015 Ã 16:32, Otto Behrens a Ã©crit : > Thanks. I do <alt>jc on a method sometimes when I have changed a > method. So sometimes I so <alt>jm and then immediately <alt>jc to > check all the tests in the class. > >> Indeed, Nautilus logic to run test differs a bit from the TestRunner logic. > > Does it really have to be? No, it should not. >> For example, if your test fails, it is run a second time to open a debugger but it could do side effects. > > This has been a problem for me for a long time. I would *love* it if > Nautilus runs a single test in debug mode (and not a second time). It > is especially painful when running selenium tests in our environment, > because firefox is launched on every test suite run, which makes > running a single test relatively expensive. I suppose solving the > problem of tests running a long time is first prize. > >> Why don't you just run your tests from the test runner or using MyTestClass run: #testSelector ? > > Because I normally run the tests that I work on while I'm in the > Nautilus browser (using shortcut keys). Why would I want to launch a > different browser, search for the class I'm working on and run the > tests there? It was a suggestion for your use case. If you only want to run the test you are working on, Nautilus helps. > I could be missing it totally here. I'm quite interested to know how > other people work. A sort of work flow, to the point of running tests. We miss a functionality in Pharo to easily run (a shorcut) a set of selected tests (ex: your project tests). This way, you can have a quick feedback on your updates. As it is not so easy, I often fallback to run tests from Nautilus (a test class or sometimes only a test method). > To run all my tests take a long time. There are quite a few. > >> We will need to clean this kind of logic that should not be part of Nautilus. Could you open a bug entry for that? > > https://pharo.fogbugz.com/f/cases/15374/exception-handling-when-running-tes… Yes.

April 21, 2015

Re: [Pharo-dev] Interrupt a locked pharo image from outside

by Thierry Goubier

Thanks, that works... now to make sense of all the debug stuff coming out ;) Thierry 2015-04-21 16:47 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > You may use: > > kill -USR1 <pid> > > Cheers, > -- Pavel > > > > 2015-04-21 16:36 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > > Hi all, > > > > anybody knows if it would be possible to generate an external > interruption > > (a signal) from outside the Pharo process which would trigger a Ctrl+. > > interrupt? > > > > OSProcess 4.5.13 has a tendancy to lock the image on some linux systems > > (ubuntu 14.10 at least), and it would be nice to be able to interrupt it > to > > be able to see where it is blocked. > > > > "killall pharo" or Ctrl+C does not give much information :( > > > > Thanks, > > > > Thierry > >

April 21, 2015