- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Test Resources
by stephane ducasse March 1, 2013

March 1, 2013

do you have a list =of features that have been added? that are planned? > Dear Stephane, > as Jan says, we had a good pair-programming session on SUnit in Glasgow. (I hope we'll have another when time permits.) I also have some stuff not yet in the OR (follow-on from my 10-min talk in Ghent) that improves/exploits TestResources. I am working to get this stuff visible so the community can comment (and porting help would be great too). It's been very busy here - and a month-long illness I had after Christmas has not helped. > > > Points that I reported in 2009 > > Were these at an ESUG (in which case I should have notes) or somewhere else. I note what you say about test-state-when-committing (would need repository-specific implementations; one for Store, one for Monticello, ... ?) > > If any list of SUnit wishes is on the web somewhere that I should be (re)reading, by all means email (to the above email address for this topic) to remind me. My aim for soon (ideally for end-March, but I've lots to do - the illness put me behind) is to make the current work visible, after which more can be looked at. > > Looking forward to Annecy > Niall Ross > > >>> Not entirely true. In Barcelona, me and Niall merged some of stx fixes into SUnit 4.0 and Niall spent a __lot__ of time questioning people >>> behind various dialects to find out what he could cleanup. >>> >>> Last summer, we had a coding session and started with 'to-be-5.0' by >>> integrating St/X SUnit (based on 4.0) and SUnitToo. St/X changes mainly >>> involves better support for interactive and reporting tools (such as one that generates JUnit-style reports), refactoring to ease customization >>> and changes to allow integration with other testing frameworks (like JUnit and GNU Testlet, mainly used by STX:LIBJAVA). >>> >>> During last ESUG's CS Niall finished the merge in VW and I have to merge it back to St/X. My shame, this haven't happened yet - no time. I should do it. >>> >>> So, feel free to go to Cincom's Public Repository and have look at Niall's last development version and see now "nothing" look like :-) >>> >> >> >> Good to know. This is still strange that nobody ever contacted us. I have no idea about integration/creation of points that I reported in 2009. I do not know if there is a list of features that I have been considered and/or integrated. >> For example knowing if the test were green when the application/tests were committed. >> >> Now when there will be a real release we will see if we port it. May be being able to load the two versions side by side would be good. >> >> Stef >> >> > > >

1 0

[Pharo-project] [update 2.0] #20577
by Marcus Denker March 1, 2013

March 1, 2013

20577 ----- Issue 7624: #condenseSources should not do a CompiledMethod cleanUp http://code.google.com/p/pharo/issues/detail?id=7624 Diff information: http://ss3.gemstone.com/ss/Pharo20/System-Support-MarcusDenker.796.diff

1 0

[Pharo-project] String asPacked/fromPacked:
by Martin Dias March 1, 2013

March 1, 2013

Hi I discovered this protocol in String hierarchy. Are you familiar with it? The method comment of #fromPacked: is: "Convert from a longinteger to a String of length 4." The only sender in Pharo 2.0 is MethodFinder. For WideString, it does not work. In examples: ByteString fromPacked: 'text' asPacked. ---> 'text' ByteString fromPacked: 'martin' asPacked. ---> 'rtin' WideString fromPacked: ('text' asWideString asPacked). ---> error WideString>>asPacked can be easily fixed adding an explicit return to the calculation (it's now implicitly returning self). But... it only encodes one letter: WideString fromPacked: 'martin' asWideString asPacked ---> 'n' I checked that in Squeak 4.3 there are not senders too. So... Should we fix the WideString implementation, or directly remove this protocol? Martin

7 14

[Pharo-project] [update 2.0] #20576
by Marcus Denker March 1, 2013

March 1, 2013

20576 ----- Issue 7589: ScriptLoader is too large to ship http://code.google.com/p/pharo/issues/detail?id=7589

1 0

[Pharo-project] One-Click now uses latest build VMS
by Marcus Denker March 1, 2013

March 1, 2013

The one click at: https://ci.inria.fr/pharo/job/Pharo-2.0/lastSuccessfulBuild/artifact/Pharo2… now uses the -latest zips from http://pharo.gforge.inria.fr/ci/vm/pharo/ Marcus

1 1

[Pharo-project] [update 2.0] #20575
by Esteban Lorenzano Feb. 28, 2013

Feb. 28, 2013

20575 ----- Issue 7621: Protocols are sometimes messed up https://code.google.com/p/pharo/issues/detail?id=7621 Issue 7620: remove IslandVMTweaksTestCase https://code.google.com/p/pharo/issues/detail?id=7620 Issue 7615: unload NativeBoost tests for now... https://code.google.com/p/pharo/issues/detail?id=7615 Issue 7609: [Horrible Error]: Class creation not logged in changes https://code.google.com/p/pharo/issues/detail?id=7609 Diff information: http://ss3.gemstone.com/ss/Pharo20/Tests-EstebanLorenzano.517.diff http://ss3.gemstone.com/ss/Pharo20/System-Support-EstebanLorenzano.794.diff http://ss3.gemstone.com/ss/Pharo20/System-Changes-EstebanLorenzano.198.diff http://ss3.gemstone.com/ss/Pharo20/KernelTests-EstebanLorenzano.472.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-EstebanLorenzano.1322.diff

2 1

[Pharo-project] Kind of Stuff I would like to change in 3.0
by Noury Bouraqadi Feb. 28, 2013

Feb. 28, 2013

TestCase>>cleanUpInstanceVariables self class allInstVarNames do: [ :name | name = 'testSelector' ifFalse: [ self instVarNamed: name put: nil ] ] Jannik & Noury -- http://twitter.com/#!/NouryBouraqadi http://car.mines-douai.fr/noury Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de necessite Please consider the environment before you print

2 3

Re: [Pharo-project] IslandVMTweaksTestCase and Memory corruption
by Fernando Olivero Feb. 28, 2013

Feb. 28, 2013

Island are part of the TeaTime implementation in Croquet. If the tests are referring to that "Island" then why should Pharo include such tests? Fernando On Thu, Feb 28, 2013 at 4:23 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Feb 28, 2013, at 4:15 PM, Ciprian Teodorov <ciprian.teodorov(a)gmail.com<mailto:ciprian.teodorov@gmail.com>> wrote: > > > No, I think that those tests should be shipped... And fix the VM to not corrupt the memory. That's only in the case these test are wrote in pure smalltalk. If they use ffi then yeah they should be removed > > They have primitives in methods for which the primitive was not written. > > On Feb 28, 2013 3:11 PM, "Marcus Denker" <marcus.denker(a)inria.fr<mailto:marcus.denker@inria.fr>> wrote: > > On Feb 28, 2013, at 3:09 PM, ClÃ©ment Bera <bera.clement(a)gmail.com<mailto:bera.clement@gmail.com>> wrote: > > Hello, > > I was looking for VM tests in the Pharo image and I found the class IslandVMTweaksTestCase. The strange thing is its comments : > "Test case for some tweaks to the VM that Islands requires. These tests are largely for documentation; with an un-tweaked VM, the tests mostly still succeed, albeit with possible memory corruption." > > Does that really mean if I run those tests it might result into memory corruption ? > > I don't think it is a good idea to ship Pharo with this memory corruption tests in IslandVMTweaksTestCase. I suggest that if the tests may really corrupt memory we remove them from Pharo, or if they cannot corrupt memory then we fix the memory corruption comment. > > Yes, we should not ship code like that. > > Marcus > >

1 0

Feb. 28, 2013

Hello, I was looking for VM tests in the Pharo image and I found the class IslandVMTweaksTestCase. The strange thing is its comments : "Test case for some tweaks to the VM that Islands requires. These tests are largely for documentation; with an un-tweaked VM, the tests mostly still succeed, albeit *with possible memory corruption*." Does that really mean if I run those tests it might result into memory corruption ? I don't think it is a good idea to ship Pharo with this memory corruption tests in IslandVMTweaksTestCase. I suggest that if the tests may really corrupt memory we remove them from Pharo, or if they cannot corrupt memory then we fix the memory corruption comment. Regards,

3 3

[Pharo-project] fast #becomeForward: crashes without PharoV10.sources
by Camillo Bruni Feb. 28, 2013

Feb. 28, 2013

While setting up the new multi platform VM tests I saw that the tests fail extremely quickly when there are not PharoV10.sources available. It is still our know #becomeForward: but on CompiledMethods, but I just want to share that.

5 6