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

Re: [Pharo-dev] test failures in downloaded image 30733

by btc＠openinworld.com

Feb. 2, 2014

test failures in downloaded image 30733 - OpenToolTest>>#testOpenBrowseOnInstalledTraitMethod

by btc＠openinworld.com

btc(a)openinworld.com wrote: > For diligence and curiosity leading up to the Pharo3 release, I > downloaded build image 30733 (with PharoLauncher) and immediately ran > all tests, which reported 7 failures and 1 error (see attached > snapshot). Error "KeyNotFound: key #localSelectors not found in MethodDictionary" occurrs in .... OpenToolTest>>#testOpenBrowseOnInstalledTraitMethod | browser | browser := (Class>>#localSelectors) browse. browser changed. browser close. Using PharoLauncher to manually bisect between builds by inspecting "Class>>#localSelectors" in Workspace * works for http://files.pharo.org/image/30/30520.zip * errors for http://files.pharo.org/image/30/30521.zip ----------- From Build 30521 Log Message: 11995 MenuMorph>>addList: sends #iconNamed: to an instance of Pharo3Theme, which raises a warning of deprecation. https://pharo.fogbugz.com/f/cases/11995 #localSelectors add to Trait so cleanup is possible in a second step ----------- Logged as https://pharo.fogbugz.com/f/cases/12771 I don't how to proceed with this. cheers -ben

Feb. 2, 2014

Re: [Pharo-dev] test failures in downloaded image 30733

by Marcus Denker

On 02 Feb 2014, at 14:31, btc(a)openinworld.com wrote: > For diligence and curiosity leading up to the Pharo3 release, I downloaded build image 30733 (with PharoLauncher) Getting an image green is a lot of little, trivial, hard workâ¦ and green always means âGreen in this contextâ. Just headless vs. non-headless changes a lot, for example. Another wonderful thing is that tests are fine when run individually, but fail when running all tests. We need to think about automatic UI testingâ¦ Loading an external package changes *everything*. We do not have a a release criterium that all tests are green after loading external packages. > and immediately ran all tests, which reported 7 failures and 1 error (see attached snapshot). Now presumably these did not occur in the CI build since otherwise it would not have been available to PharoLauncher, so this raises a few questions/ideas: > > 1. Why the discrepancy / how did these slip through ? Perhaps some difference in local environment / difference in VM? Can anyone else reproduce this for 30733? I've logged an new case [1] for this where I plan to either link to existing cases or add a subcase for each failure. Please add your results there, particularly if you see a known issue. > > Here are my failures... > BlockClosureTest>>#testTrace Not failing for me > JobTest>>#testCurrent Not failing for me > MetacelloRepositorySqueakCommonTestCase>>#testAsRepositorySpecFor > MetacelloRepositorySqueakCommonTestCase>>#testDirectoryRepository > MetacelloRepositorySqueakCommonTestCase>>#testFileTreeRepository Not failing fo rme > ReleaseTest>>#testObsoleteClasses Not failing for me > SimmulateMouseSpecification>>#testSimulateRightClick yes, that is failing > and errors... > OpenToolTest>>#testOpenBrowseOnInstalledTraitMethod > yes. The last two are examples of UI tests that are not run on the Build server in a way that they could fail. > 3. Assuming Pharo3 will go through a Release Candidate phase, Normally the idea is that we will just release. In the past we used an elaborate process, but the reality is that nobody looks at release candidates. You can tell 5 times that the release candidate will be released unchanged and people should check: they will not. They will download the release, though, and then complain that the âobviousâ thing X is not fixed that that the people who managed the release process did everything wrong. Because âreleaseâ means bug free. By magic. Marcus

Feb. 2, 2014

Re: [Pharo-dev] Comparing dates

by Sebastian Sastre

On Feb 1, 2014, at 12:26 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Sebastian, > > In my 3.0 image > > | today | > today := Date today. > (today translateTo: 2 hours) = today. > > => false > Yeah, here too > But what are you trying to accomplish ? Detect the most simple equality in the most conventional way. A true when two dates refers to the same date of the calendar > Dates are a bit ambiguous: my Feb 1st and your Feb 1st, in one sense they are the same, refer to the same date, but in another sense, yours started at a different point in time, right ? So are they equal ? Well dates are the same, thatâs the convention isnât it? Localisation and time is what's different there. If you want to have time involved in the equation the logic step given our options is that you use DateAndTime So, againâ¦ Is this a bug or a feature? 1. Feature: our convention is injecting time in dates so we are injecting an incompatibility with intuition in exchange of a surprising precision* 2. Bug: Date #= should not compare start *a precision that is redundant because DateAndTime also have the #translateTo: feature > Sven > > On 01 Feb 2014, at 14:01, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > >> Can somebody please clarify if this is a bug or feature? >> >> thanks >> >> >> >> >> On Jan 31, 2014, at 9:03 PM, Sebastian Sastre <SEBASTIAN(a)FLOWINGCONCEPT.COM> wrote: >> >>> self assert: Date today = Date today. >>> >>> today := Date today translateTo: 2 hours. >>> self assert: today = Date today >>> >>> Is this right? >>> >>> >>> >>> >> >> > >

Feb. 2, 2014

test failures in downloaded image 30733

by btc＠openinworld.com

For diligence and curiosity leading up to the Pharo3 release, I downloaded build image 30733 (with PharoLauncher) and immediately ran all tests, which reported 7 failures and 1 error (see attached snapshot). Now presumably these did not occur in the CI build since otherwise it would not have been available to PharoLauncher, so this raises a few questions/ideas: 1. Why the discrepancy / how did these slip through ? Perhaps some difference in local environment / difference in VM? Can anyone else reproduce this for 30733? I've logged an new case [1] for this where I plan to either link to existing cases or add a subcase for each failure. Please add your results there, particularly if you see a known issue. Here are my failures... BlockClosureTest>>#testTrace JobTest>>#testCurrent MetacelloRepositorySqueakCommonTestCase>>#testAsRepositorySpecFor MetacelloRepositorySqueakCommonTestCase>>#testDirectoryRepository MetacelloRepositorySqueakCommonTestCase>>#testFileTreeRepository ReleaseTest>>#testObsoleteClasses SimmulateMouseSpecification>>#testSimulateRightClick and errors... OpenToolTest>>#testOpenBrowseOnInstalledTraitMethod 2. How is the PharoLauncher VM synced with that used to test the Pharo CI builds ? (My VM comes from the PharoLauncher Windows Installer) 3. Assuming Pharo3 will go through a Release Candidate phase, apart from functionality testing which anyone may-or-not have time for, as many spectators as possible should download those Release Candidate images an just run All Tests. 4. It might be good for a small number of releases between now and Release Candidate to be designated for the community to similarly run All Tests - to reduce surprises at Release Candidate time? 5. I've seen times before when some failures as transitory/random (which had to do with unordered Sets being used by a test that presumed order). So at times when there are a lot of Pharoers together, such as at a Sprint, maybe the convention could be for everyone to run All Tests at the start of the day to provide broad comparison (and know you're starting with a clean slate) cheers -ben [1] https://pharo.fogbugz.com/f/cases/12770/

Feb. 2, 2014

Re: [Pharo-dev] ZTimestamp>>monthName spelling error

by Sven Van Caekenberghe

On 02 Feb 2014, at 10:44, Norbert Hartl <norbert(a)hartl.name> wrote: >> Now that example should work: >> >> (ZTimestampFormat fromString: 'Saturday, 3 February, 2001') >> german; >> format: Date today. >> >> => 'Samstag, 1 Februar, 2014â > > Does ZTimestampFormat handle the formatting of the date? If so then for germany it would be > > Samstag, 1. Februar 2014 ZTimestampFormat works 'by example', substituting known keys for actual values, possibly translated. It cannot reorder the specification. So it does not properly handle locale. But you could work around this limitation a bit by adjusting the format to the locale. In the above example: (ZTimestampFormat fromString: 'Saturday, 3. February 2001') german; format: Date today. should do the trick. Sven

Feb. 2, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by Sebastian Sastre

On Feb 1, 2014, at 9:33 PM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: >> >> So if we cannot break tradition then Traits should never have been introduced? We can. Innovation has a lot to do with that. But you have ways to introduce your innovation that will make all the difference. iPhone broke all the tradition about making mobile phones in the most epic way Again, my problem is not with innovation but with delivering poorly

Feb. 2, 2014

Re: [Pharo-dev] How to suck (and yet be awesome)

by Sebastian Sastre

On Feb 1, 2014, at 8:48 PM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > I always thought that I had a narcissic relationship with my mac :) but not with my car :) > yeah, we have a strong intellectual bias. Thatâs great because we make a tool to expand our creativity and expressions of intelligence Kathyâs point is that we might be doing more to help others be great themselves through our product/tool/service (Pharo in this case) You do that all the time with your students They, as everybody, have many options to be heroâs (like solving things with Phyton/Ruby, etc) so our challenge is to have a smooth learning curve with fast positive feedback Clean APIâs helps a lot on that because itâs like the UI of the code Great tutorials on how to do popular arctifacts (todo lists, blogs, CRUD apps) is something that comes to mind for making a bridge between theory and practical positive results At least that worked incredibly well for Rails and other frameworks

Feb. 2, 2014

Re: [Pharo-dev] subscript out of bounds in protocol creation

by Jordi Delgado

Great! Thanks a lot! Bests, Jordi > 2014-02-02 Jordi Delgado <jdelgado(a)lsi.upc.edu>: > > > Hi, > > > > I downloaded the most recent image with the most recent VM. > > I'm using a macbook air with Mountain Lion 10.8.5, image 30733 and System > > Reporter says: > > > > Virtual Machine > > --------------- > > /Users/jdelgado/Smalltalk/Pharo-latest/Pharo.app/Contents/MacOS/Pharo > > NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > > acc98e51-2fba-4841-a965-2975997bba66 Dec 26 2013 > > NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > > acc98e51-2fba-4841-a965-2975997bba66 Dec 26 2013 > > https://github.com/pharo-project/pharo-vm.git Commit: > > e698e14f38003258fa49506b14307d83863a5ac1 Date: 2013-12-16 06:32:59 -0800 > > By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14780 > > > > Mac Cocoa Cog 5.8b12 21-Sep-10 >1B0534FA-246C-47C5-AB29-7A76C81CCDCB< > > VMMaker versionString https://github.com/pharo-project/pharo-vm.gitCommit: e698e14f38003258fa49506b14307d83863a5ac1 Date: 2013-12-16 06:32:59 > > -0800 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14780 > > NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > > acc98e51-2fba-4841-a965-2975997bba66 Dec 26 2013 > > NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > > acc98e51-2fba-4841-a965-2975997bba66 Dec 26 2013 > > > > However: This time the error does not appear, no matter what I do. Maybe > > it's solved (?) > > > > Bests, > > > > Jordi > > > > > > > > > > > > > > > > Am 01.02.2014 um 16:41 schrieb Jordi Delgado <jdelgado(a)lsi.upc.edu>: > > > > > > > That's what I mean, I did *exactly* that, and the chosen class was > > > > KMKeymapBuilder (from Keymapping-Pragmas package). The private > > > > protocol was added with no problem. So...? No idea. > > > > > > > > Bests, > > > > > > > > Jordi > > > > > > > > PS: Also with a freshly 30733 image downloaded > > > > > > > > > > > OK, I tried it with KMKeymapBuilder and got the errors. > > > So we need to check for the operating system and VM. > > > On my machine (OSX 10.9.1) System Reporter says for VM General: > > > > > > Virtual Machine > > > --------------- > > > /Applications/Pharo.app/Contents/MacOS/Pharo > > > NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > > acc98e51-2fba-4841-a965-2975997bba66 Dec 12 2013 > > > NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > > acc98e51-2fba-4841-a965-2975997bba66 Dec 12 2013 > > > https://github.com/pharo-project/pharo-vm.git Commit: > > 71adca113a9aff2876288927e5c1c86bf7ac13e2 Date: 2013-12-07 05:00:47 -0800 > > By: Philippe Back <philippeback(a)gmail.com> Jenkins build #14777 > > > > > > Mac Cocoa Cog 5.8b12 21-Sep-10 >1B0534FA-246C-47C5-AB29-7A76C81CCDCB< > > > VMMaker versionString https://github.com/pharo-project/pharo-vm.gitCommit: 71adca113a9aff2876288927e5c1c86bf7ac13e2 Date: 2013-12-07 05:00:47 > > -0800 By: Philippe Back <philippeback(a)gmail.com> Jenkins build #14777 > > > NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > > acc98e51-2fba-4841-a965-2975997bba66 Dec 12 2013 > > > NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > > acc98e51-2fba-4841-a965-2975997bba66 Dec 12 2013 > > > > > > > > > What are you using? > > > > > > Regards, > > > Andreas > > > > > > > > > > > > > > > > > >> Hi Jordi and all, > > > >> > > > >> here is my detailed receipt with a freshly downloaded 30733.zip from > > Pharo files: > > > >> > > > >> 1. Open Nautilus > > > >> 2. Select an arbitrary package > > > >> 3. Select an arbitrary class from that package > > > >> 4. Right-click in the methods panel and select "Add protocol..." > > from the popup menu. > > > >> 5. Enter "private" in the dialog without selecting any entry in > > the listbox on top. > > > >> 6. Hit "enter" or press "OK" with a left-click. > > > >> > > > >> -> Bummer! A cascade of 3 "SubscriptOutOfBounce: 1" pre-debuggers. > > > >> > > > >> Regards, > > > >> Andreas > > > >> > > > >> > > > >> > > > >> Am 01.02.2014 um 11:46 schrieb Jordi Delgado <jdelgado(a)lsi.upc.edu>: > > > >> > > > >>> Hi, > > > >>> > > > >>> With a fresh image, I do that with a class randomly selected > > > >>> (obviously, with no class selected nothing happens) and the > > > >>> protocol gets added without problems. Then, I choose another class, > > > >>> again I pick a random one, and after doing exactly the same the > > > >>> error appears. Why? No clue. > > > >>> > > > >>> I said that the error is difficult to reproduce because sometimes > > > >>> it appears, and sometimes not. And I am not able to ascertain the > > > >>> circumstances under which it will pop up. > > > >>> > > > >>> Bests, > > > >>> > > > >>> Jordi > > > >>> > > > >>> > > > >>> > > > >>> > > > >>>> Hi, > > > >>>> > > > >>>> Am 31.01.2014 um 08:36 schrieb Jordi Delgado <jdelgado(a)lsi.upc.edu > > >: > > > >>>> > > > >>>>> Hi, > > > >>>>> > > > >>>>> I realized that sometimes, when creating new protocols, it appears > > an > > > >>>>> error "subscript out of bounds: 1". I have not been able -yet- > > > >>>>> to reproduce it from a clean image, but it happens often (at least > > > >>>>> to me). It seems to me that it has something to do with protocol > > > >>>>> creation before any method has been written, but I am still > > investigating. > > > >>>>> > > > >>>> I guess I can produce this easily :-) > > > >>>> Just hit "Add protocol..." in the popup menu of the method protocol > > pane. > > > >>>> Enter a name like "private" in the dialog. And then press enter > > without selecting anything in the listbox above. > > > >>>> And voilÃ ... > > > >>>> > > > >>>> Regards, > > > >>>> Andreas > > > >>>> > > > >>>> > > > >>>> > > > >>> > > > >> > > > >> > > > > > > > > > > > > > > > > Not fixed in 30733, but now in 30735.

Feb. 2, 2014

Re: [Pharo-dev] subscript out of bounds in protocol creation

by Nicolai Hess

2014-02-02 Jordi Delgado <jdelgado(a)lsi.upc.edu>: > Hi, > > I downloaded the most recent image with the most recent VM. > I'm using a macbook air with Mountain Lion 10.8.5, image 30733 and System > Reporter says: > > Virtual Machine > --------------- > /Users/jdelgado/Smalltalk/Pharo-latest/Pharo.app/Contents/MacOS/Pharo > NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > acc98e51-2fba-4841-a965-2975997bba66 Dec 26 2013 > NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > acc98e51-2fba-4841-a965-2975997bba66 Dec 26 2013 > https://github.com/pharo-project/pharo-vm.git Commit: > e698e14f38003258fa49506b14307d83863a5ac1 Date: 2013-12-16 06:32:59 -0800 > By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14780 > > Mac Cocoa Cog 5.8b12 21-Sep-10 >1B0534FA-246C-47C5-AB29-7A76C81CCDCB< > VMMaker versionString https://github.com/pharo-project/pharo-vm.gitCommit: e698e14f38003258fa49506b14307d83863a5ac1 Date: 2013-12-16 06:32:59 > -0800 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14780 > NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > acc98e51-2fba-4841-a965-2975997bba66 Dec 26 2013 > NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > acc98e51-2fba-4841-a965-2975997bba66 Dec 26 2013 > > However: This time the error does not appear, no matter what I do. Maybe > it's solved (?) > > Bests, > > Jordi > > > > > > > > > Am 01.02.2014 um 16:41 schrieb Jordi Delgado <jdelgado(a)lsi.upc.edu>: > > > > > That's what I mean, I did *exactly* that, and the chosen class was > > > KMKeymapBuilder (from Keymapping-Pragmas package). The private > > > protocol was added with no problem. So...? No idea. > > > > > > Bests, > > > > > > Jordi > > > > > > PS: Also with a freshly 30733 image downloaded > > > > > > > > OK, I tried it with KMKeymapBuilder and got the errors. > > So we need to check for the operating system and VM. > > On my machine (OSX 10.9.1) System Reporter says for VM General: > > > > Virtual Machine > > --------------- > > /Applications/Pharo.app/Contents/MacOS/Pharo > > NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > acc98e51-2fba-4841-a965-2975997bba66 Dec 12 2013 > > NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > acc98e51-2fba-4841-a965-2975997bba66 Dec 12 2013 > > https://github.com/pharo-project/pharo-vm.git Commit: > 71adca113a9aff2876288927e5c1c86bf7ac13e2 Date: 2013-12-07 05:00:47 -0800 > By: Philippe Back <philippeback(a)gmail.com> Jenkins build #14777 > > > > Mac Cocoa Cog 5.8b12 21-Sep-10 >1B0534FA-246C-47C5-AB29-7A76C81CCDCB< > > VMMaker versionString https://github.com/pharo-project/pharo-vm.gitCommit: 71adca113a9aff2876288927e5c1c86bf7ac13e2 Date: 2013-12-07 05:00:47 > -0800 By: Philippe Back <philippeback(a)gmail.com> Jenkins build #14777 > > NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > acc98e51-2fba-4841-a965-2975997bba66 Dec 12 2013 > > NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > acc98e51-2fba-4841-a965-2975997bba66 Dec 12 2013 > > > > > > What are you using? > > > > Regards, > > Andreas > > > > > > > > > > > > >> Hi Jordi and all, > > >> > > >> here is my detailed receipt with a freshly downloaded 30733.zip from > Pharo files: > > >> > > >> 1. Open Nautilus > > >> 2. Select an arbitrary package > > >> 3. Select an arbitrary class from that package > > >> 4. Right-click in the methods panel and select "Add protocol..." > from the popup menu. > > >> 5. Enter "private" in the dialog without selecting any entry in > the listbox on top. > > >> 6. Hit "enter" or press "OK" with a left-click. > > >> > > >> -> Bummer! A cascade of 3 "SubscriptOutOfBounce: 1" pre-debuggers. > > >> > > >> Regards, > > >> Andreas > > >> > > >> > > >> > > >> Am 01.02.2014 um 11:46 schrieb Jordi Delgado <jdelgado(a)lsi.upc.edu>: > > >> > > >>> Hi, > > >>> > > >>> With a fresh image, I do that with a class randomly selected > > >>> (obviously, with no class selected nothing happens) and the > > >>> protocol gets added without problems. Then, I choose another class, > > >>> again I pick a random one, and after doing exactly the same the > > >>> error appears. Why? No clue. > > >>> > > >>> I said that the error is difficult to reproduce because sometimes > > >>> it appears, and sometimes not. And I am not able to ascertain the > > >>> circumstances under which it will pop up. > > >>> > > >>> Bests, > > >>> > > >>> Jordi > > >>> > > >>> > > >>> > > >>> > > >>>> Hi, > > >>>> > > >>>> Am 31.01.2014 um 08:36 schrieb Jordi Delgado <jdelgado(a)lsi.upc.edu > >: > > >>>> > > >>>>> Hi, > > >>>>> > > >>>>> I realized that sometimes, when creating new protocols, it appears > an > > >>>>> error "subscript out of bounds: 1". I have not been able -yet- > > >>>>> to reproduce it from a clean image, but it happens often (at least > > >>>>> to me). It seems to me that it has something to do with protocol > > >>>>> creation before any method has been written, but I am still > investigating. > > >>>>> > > >>>> I guess I can produce this easily :-) > > >>>> Just hit "Add protocol..." in the popup menu of the method protocol > pane. > > >>>> Enter a name like "private" in the dialog. And then press enter > without selecting anything in the listbox above. > > >>>> And voilÃ ... > > >>>> > > >>>> Regards, > > >>>> Andreas > > >>>> > > >>>> > > >>>> > > >>> > > >> > > >> > > > > > > > > > Not fixed in 30733, but now in 30735.

Feb. 2, 2014