- Pharo-dev - lists.pharo.org

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Sept. 19, 2013

Sept. 19, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=li… 169 regressions found. Gofer.Tests.GoferOperationTest.testLocalChanges Gofer.Tests.GoferOperationTest.testReinitialize Gofer.Tests.GoferOperationTest.testRemoteChanges RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testAddCategoryCreatesPackage RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testRenameCategoryAlsoRenameAllExtensionProtocols RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testAddCategoryIsAlreadyAPackageDoesNotCreatePackage RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testRenameCategoryChangeTheNameOfThePackage RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testRenameUnknownCategoryCreatesNewRPackage RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testRenameCategoryUpdateTheOrganizer RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRecategorizeClassWithMetaClassMethodsRegisterAllClassMethodsInTheNewPackage RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testReorganizeClassByRenamingExtensionCategoryToClassicCategoryMoveMethodsFromExtendingPackageToParentPackage RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRecategorizeClassRaisesClassRepackagedEvent RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRecategorizeClassWithUnexistingPackageNameRegisterTheClassInANewPackage RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRenameClassUpdateClassDefinedSelectorsInTheParentPackage RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRenameClassUpdateOrganizerClassExtendingPackagesMapping RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testReorganizeClassByAddingNewProtocolDoesNothing RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRemoveClassUpdateTheOrganizerMappings RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRenameClassUpdateOrganizerClassPackageMapping RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRecategorizeClassRegisterTheClassInTheExactMatchPackage RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRemoveClassUnregisterTheClassExtensionMethodsFromTheCorrespondingPackage ...

1 0

"OS" and "OS-Windows" project on STHub
by Torsten Bergmann Sept. 19, 2013

Sept. 19, 2013

Damien wrote: >Do you already have continuous integration set up or do you want me to do it? No, not yet. I've a CI account but was not able to create projects with it. Would be nice if you could help setting it up. Obvious that it requires a windows slave. The code already takes care that the tests run only on Windows (there is a class WindowsSpecificTest as a subclass of TestCase overriding #isAbstract). Bye T.

2 1

Re: [Pharo-dev] [update 3.0] #30407
by Mariano Martinez Peck Sept. 19, 2013

Sept. 19, 2013

On Thu, Sep 19, 2013 at 6:10 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > 30407 > ----- > > 11631 Disable History navigation buttons in Inspectors when not usable > https://pharo.fogbugz.com/f/cases/11631 > > 11413 Make a diff tool to show recategorization as a change properly > https://pharo.fogbugz.com/f/cases/11413 This is soooooo COOOOl!! THanks guys! > > > 11632 Add browse shortcut to critics browser > https://pharo.fogbugz.com/f/cases/11632 > > > Diff information: > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Inspector-MarcusDenker.7… > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Debugger-MarcusDenker.11… > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Tools-Diff-MarcusDe… > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Monticello-MarcusDenker.865.d… > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Manifest-CriticBrowser-Marcus… > > -- Mariano http://marianopeck.wordpress.com

1 0

voyage/mongo reset vs. allInstancesDo: #reset
by Sabine KnÃ¶fel Sept. 19, 2013

Sept. 19, 2013

Hi Esteban, all, in the mongo/voyage tutorial at ESUG, I understood, that "VOMongoRepository reset" can be used instead of "VOMongoRepository allInstancesDo: #reset". and the code looks like that ( flush...) It seems that I can't - I think, using "VOMongoRepository reset" does _not_ reset the cache. So, the objects are not read new from database. Voyage does not enter the <mongoDescription> methods. This is not a problem for me, I can also use "VOMongoRepository allInstancesDo: #reset", but I want to tell you about that. To reproduce I did the following, 1) read objects from mongo (ClassXXX readAll) 2) put halt in one of the <mongoDescription> methods 3 a) do "VOMongoRepository reset" and then (ClassXXX readAll) again -> no debugger 3 b) do "VOMongoRepository allInstancesDo: #reset" and then (ClassXXX readAll) again -> debugger comes up ==> so, 3a does not work, 3b works Regards Sabine -- View this message in context: http://forum.world.st/voyage-mongo-reset-vs-allInstancesDo-reset-tp4709120.… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

2 4

Can't correctly inspect ring definitions
by Martin Dias Sept. 19, 2013

Sept. 19, 2013

Hi, In the attached png I show how 'annotations' is a dictionary in the "all inst vars" entry, while it is nil in the 'annotations' entry. The reason is that #instVarNamed: is redefined in RGClassDescriptionDefinition to answer the RGInstanceVariableDefinition representing the requested instance variable of the *represented class* (or nil if there is no instance variable with that name). I know that a purpose of ring entities is to be polymorphic with the represented system entities. But #instVarNamed: is protocol of Object, not of Class or ClassDescription. I you agree I will open an issue and submit a fix: To rename the method in RGClassDescriptionDefinition to #instanceVariableNamed: and update the test. MartÃn

4 8

[update 3.0] #30407
by Marcus Denker Sept. 19, 2013

Sept. 19, 2013

30407 ----- 11631 Disable History navigation buttons in Inspectors when not usable https://pharo.fogbugz.com/f/cases/11631 11413 Make a diff tool to show recategorization as a change properly https://pharo.fogbugz.com/f/cases/11413 11632 Add browse shortcut to critics browser https://pharo.fogbugz.com/f/cases/11632 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Inspector-MarcusDenker.7… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Debugger-MarcusDenker.11… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Tools-Diff-MarcusDe… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Monticello-MarcusDenker.865.d… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Manifest-CriticBrowser-Marcus…

1 0

Re: [Pharo-dev] Smalltalkhub => 503
by Stephan Eggermont Sept. 19, 2013

Sept. 19, 2013

Yes, smalltalkhub is nice. And installing your own is very easy. I think more people should do so. It doesn't seem to be as solid as ss3, but can be installed much easier, and on legacy platforms (windows). Running your own mirror should not take that much space and capacity, and makes you less dependent on central infrastructure staying up. Stephan

5 5

Do not use shouldnt:raise:
by Camillo Bruni Sept. 19, 2013

Sept. 19, 2013

Warning, long post. I accidentally run the dev version of moose on a 2.0 to check if the VMs work properly and I ran into a bunch of failing tests. https://ci.inria.fr/pharo/view/3.0-VM/job/PharoVM-AcceptanceTest/27/SLAVE=p… First of all, my problem, since I wanted to test the #stable release anyway. In any case I had a look at the bugs since I was interested to see if it was in any way VM-related: https://ci.inria.fr/pharo/view/3.0-VM/job/PharoVM-AcceptanceTest/27/SLAVE=p… Ok, 0 information :(, why? Because of #shouldnt:raise:. On a linguistic basis the #shouldnt:raise: message makes sense, sort of the counter part of #should:raise:... BUT how does it handle errors exactly? Example 1: ---------- self shouldnt: [ 1 doeSomething ] raise: MessageNotUnderstood. ok, seems fine, the test should fail, most probably with an assertion failure, and this is what it does indeed. Example 2: ---------- self shouldnt: [ 1/0 ] raise: MessageNotUnderstood. will that now fail or not? Because it doesn't raise the MessageNotUnderstood, so the logic conclusion is that it doesn't fail. Well, you're wrong, it WILL FAIL, with a ZeroDivide, which is the major reason #shouldnt:raise: is not helpful. That is utterly confusing and rather useless. Because you can just write 1 doeSomething. 1/0. - In case 1 you get an MessageNotUnderstood instead of an AssertionFailure => test fails in both cases - In the second case you get the same message, so nothing to discuss about. The interesting part is, that case 1 almost never happens like I've shown it. Most of the time it looks more like this (including the failing moose tests): self shouldnt: [ 1 doeSomething ] raise: Error. This is in my eye useless, even worse, it is obstructing, since you basically mute an otherwise useful error. In the original example, I was left with no stack trace nor a decent reason why the test would fail. Whereas with a bit of stack trace I would get reasonable context to start real debugging efforts. Conclusion: ----------- a) do not use #shouldnt:raise: b) still don't use it c) if you want to use #shouldnt:raise: for dubious reasons, use very specific errors you test for, othew

1 0

OSX Pharo VMs
by news{＠bestley.co.uk Sept. 19, 2013

Sept. 19, 2013

I am on OSX 10.8.5 (Mac mini Late 2012 2.6 GHz Intel Core i7 ) and tried to download a VM The ones on the download page<http://www.pharo-project.org/pharo-download> all seem to give me an .app that OSX says is damaged when I try to open it. I went to <http://files.pharo.org/vm/pharo/3.0/mac/> The stable which has the same date as the one on the download pages is reported as damaged but the <http://files.pharo.org/vm/pharo/3.0/mac/Pharo-VM-mac-latest.zip> dated 16th Sept starts. I have a older working VM Smalltalk vm version. 'NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 git://gitorious.org/cogvm/blessed.git Commit: 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 ' Which is the correct stable Mac VM? -- Mark

3 6

Re: [Pharo-dev] [Pharo-users] PBE2?
by Yuriy Tymchuk Sept. 18, 2013

Sept. 18, 2013

On 18 Ð²ÐµÑ. 2013, at 18:17, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >>>> What do you think? >>> >>> >>> I agree. We need someone to take the lead and distribute the work. Do >>> you volunteer? >> I'm thinking about starting doing that myself, and if I'll manage to review a couple of paragraphs each day I can say that I can take a lead :). >> >> Do you think that moving PBE to pier will be too hard? > > No we should just simplify when something is not working at the latex level. > So indeed it would be cool to migrate the book using the pier syntax like that we will get a new one > in pdf, latex and more. > > We can set up a new jenkins script, git hub repo and get started. Would be nice. > > Stef >> >>> >>> -- >>> Damien Cassou >>> http://damiencassou.seasidehosting.st >>> >>> "Success is the ability to go from one failure to another without >>> losing enthusiasm." >>> Winston Churchill >>> >> >> > >

3 4