Re: [Pharo-dev] poolDictionaries removal breaks my projects
I added https://pharo.fogbugz.com/default.asp?12769 Fix included. took me less than 10 min including downloading the latest version of Pharo and scanning complete sources. Stef
Re: [Pharo-dev] [Review]: Case 12737 Morph sends mouseUp twice to handlers
Well did we lived perfectly with it over last year? yes - 40 no - 30 Because changing Morphic now sounds a bit shaky to me :) That's why I'm asking for a lot of input. But it is a bug. And I think this slice version is very unlikely to break anything - 2 lines changed. I'd at least appreciate someone taking a look. If you agree that it's a straight-forward change, I will take responsibility for getting it right or reverting. Cheers, Sean View this message in context: Re: [Review]: Case 12737 Morph sends mouseUp twice to handlers Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] poolDictionaries removal breaks my projects
Le 31/01/2014 13:21, Esteban Lorenzano a écrit : Said so… I still does not understand why this particular change couldn’t wait for pharo 4. But well… now is there, so it needs to work fine. As long as you don't learn to reject, you will face this situation over and over. Believe me. Hilaire -- Dr. Geo http://drgeo.eu
Re: [Pharo-dev] poolDictionaries removal breaks my projects
Why state 'responded' - would it not be better if the monkey checked the slice, even though no unit tests will hit the change, it shows at least that nothing obvious broke. On 02 Feb 2014, at 09:12, Pharo4Stef pharo4s...@free.fr wrote: I added https://pharo.fogbugz.com/default.asp?12769 Fix included. took me less than 10 min including downloading the latest version of Pharo and scanning complete sources. Stef
Re: [Pharo-dev] subscript out of bounds in protocol creation
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 esteba...@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.git Commit: e698e14f38003258fa49506b14307d83863a5ac1 Date: 2013-12-16 06:32:59 -0800 By: Esteban Lorenzano esteba...@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 jdelg...@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 philippeb...@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.git Commit: 71adca113a9aff2876288927e5c1c86bf7ac13e2 Date: 2013-12-07 05:00:47 -0800 By: Philippe Back philippeb...@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 jdelg...@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 jdelg...@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
Re: [Pharo-dev] ZTimestampmonthName spelling error
Am 01.02.2014 um 17:26 schrieb Sven Van Caekenberghe s...@stfx.eu: Sabine, On 01 Feb 2014, at 15:15, Sabine Knöfel sabine.knoe...@gmail.com wrote: Hi Sven, thank you for the quick fix. It works fine now. I do not call this directly but from DateAndTime date: self endDate time: self endTime Your example: I am no english native speaker but I assume, that 'saterday' should be spelled as 'saturday'. If yes, there are several occurences of saterday. Terrible spelling of me! === Name: ZTimestamp-SvenVanCaekenberghe.33 Author: SvenVanCaekenberghe Time: 1 February 2014, 5:18:50.139922 pm UUID: 40111894-d387-432a-a3e1-2245af4a269b Ancestors: ZTimestamp-SvenVanCaekenberghe.32 Even worse: Saterday = Saturday (thx Sabine Knöfel) === ConfigurationOfZTimestamp has been updated everywhere. I saw this when trying your example: (ZTimestampFormat fromString: 'Saterday, 3 February, 2001') german; format: Date today. =='Samstag, 1 Februar, 2014' (ZTimestampFormat fromString: 'Saturday, 3 February, 2001') german; format: Date today. =='Samurday, 1 Februar, 2014' Also, 'Samurday' is no german word. 'Saturday' means 'Samstag' in German. 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 Norbert Thanks for the feedback. Sven Regards Sabine On Sat, Feb 1, 2014 at 1:31 PM, Sven Van Caekenberghe s...@stfx.eu wrote: Sabine, On 01 Feb 2014, at 12:52, Sabine Knöfel sabine.knoe...@gmail.com wrote: Hi Sven, could you change Februari into February please? Ah, terrible typo, it was all over the place. === Name: ZTimestamp-SvenVanCaekenberghe.32 Author: SvenVanCaekenberghe Time: 1 February 2014, 1:27:02.50151 pm UUID: 70fd3b88-e15e-4139-922c-9c602e3fc532 Ancestors: ZTimestamp-SvenVanCaekenberghe.31 The English spelling of the 2nd month name was consistently wrong: Februari instead of the correct February (thx Sabine Knöfel); Now use #monthIndex instead of the less consistent #month === Btw, did you know you can do: (ZTimestampFormat fromString: 'Saterday, 3 February, 2001') german; format: Date today. = 'Samstag, 1 Februar, 2014' Regards, Sven (I use http://mc.stfx.eu/Neo, this is the right place?) Regards Sabine ZTimestampmonthName Return the English name of the month of the receiver, according to the Gregorian calendar, a Symbol ^ #(January Februari March April May June July August September October November December) at: self monthIndex -- View this message in context: http://forum.world.st/ZTimestamp-monthName-spelling-error-tp4740821.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
[Pharo-dev] [pharo-project/pharo-core]
Branch: refs/tags/30735 Home: https://github.com/pharo-project/pharo-core
[Pharo-dev] [pharo-project/pharo-core] 84479c: 30735
Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 84479c3be512ca637893e3061cf4843e85816d5b https://github.com/pharo-project/pharo-core/commit/84479c3be512ca637893e3061cf4843e85816d5b Author: Jenkins Build Server bo...@pharo-project.org Date: 2014-02-02 (Sun, 02 Feb 2014) Changed paths: A Polymorph-Widgets.package/ListDialogWindow.class/instance/actions/doubleClickOk.st M Polymorph-Widgets.package/ListDialogWindow.class/instance/items creation/buildListMorph.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script388.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30735.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tools.package/AbstractTool.class/class/private/requestProtocolNameFor_initialAnswer_.st M Tools.package/AbstractTool.class/instance/class/addCategoryIn_before_.st Log Message: --- 30735 12469 Sometimes an empty protocol is created https://pharo.fogbugz.com/f/cases/12469 http://files.pharo.org/image/30/30735.zip
Re: [Pharo-dev] subscript out of bounds in protocol creation
2014-02-02 Jordi Delgado jdelg...@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 esteba...@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 esteba...@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 jdelg...@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 philippeb...@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 philippeb...@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 jdelg...@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 jdelg...@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.
Re: [Pharo-dev] subscript out of bounds in protocol creation
Great! Thanks a lot! Bests, Jordi 2014-02-02 Jordi Delgado jdelg...@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 esteba...@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 esteba...@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 jdelg...@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 philippeb...@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 philippeb...@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 jdelg...@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 jdelg...@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à...
Re: [Pharo-dev] How to suck (and yet be awesome)
On Feb 1, 2014, at 8:48 PM, Pharo4Stef pharo4s...@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
Re: [Pharo-dev] poolDictionaries removal breaks my projects
On Feb 1, 2014, at 9:33 PM, Pharo4Stef pharo4s...@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
Re: [Pharo-dev] ZTimestampmonthName spelling error
On 02 Feb 2014, at 10:44, Norbert Hartl norb...@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
[Pharo-dev] test failures in downloaded image 30733
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/
Re: [Pharo-dev] Comparing dates
On Feb 1, 2014, at 12:26 PM, Sven Van Caekenberghe s...@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 sebast...@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 sebast...@flowingconcept.com wrote: self assert: Date today = Date today. today := Date today translateTo: 2 hours. self assert: today = Date today Is this right?
Re: [Pharo-dev] test failures in downloaded image 30733
On 02 Feb 2014, at 14:31, b...@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
[Pharo-dev] test failures in downloaded image 30733 - OpenToolTest#testOpenBrowseOnInstalledTraitMethod
b...@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 MenuMorphaddList: 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
Re: [Pharo-dev] test failures in downloaded image 30733
Thanks for your feedback Marcus. A couple of thought inline... Marcus Denker wrote: On 02 Feb 2014, at 14:31, b...@openinworld.com wrote: For diligence and curiosity leading up to the Pharo3 release, I downloaded build image 30733 (with PharoLauncher) Another wonderful thing is that tests are fine when run individually, but fail when running all tests. It seems that when clicking on the failed test, the test is re-run and that result is debugged - but sometimes the error doesn't occur. It would be great the context of the error in the original execution was stored so that actual error could be inspected. Indeed, (to dream) presuming you're working off fresh CI build, it would be cool if using Fuel in one step you send the context of the original error (with CI build meta-info attached) to someone else's PharoLauncher, which automatically downloads the required CI build, and launches with the Fuel file loaded and ready to debug. 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. No external packages loaded here. btw, What was your OS environment? 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. I've seen that happening previously. In trying to understand the reality of this, perhaps... * "check if this is okay" is an open ended question that doesn't have a deliverable to drive people to action. How do you know when its time to report success/failure? * people do download and try it but its only shallow testing * people only report by exception. Perhaps a more defined task such as "Run All Tests" is easier for people to do (single button press) and to report success/failure. PharoLaucher also makes it easier and quicker to do this. You don't need to call it a Release Candidate. Just have a specified version that multiple people run in multiple environments. Of course, that could also open up a can of worms of being hard from your end to dealing every test failure due to other people's environments. There would need a pragmatic approach about which ones to deal with to stay on schedule with the release date. cheers -ben
Re: [Pharo-dev] Comparing dates
Why are you adding hours to a Date in the first place? I don't understand. Does that make it the next day or the same day 2 hours past the start of the day in whatever timezone you are in, intuitively? I vote: b. Bug. #= should compare calendar (gregorian, julian etc,), year, month, day or year, day # of year On Feb 1, 2014, at 12:26 PM, Sven Van Caekenberghe lt;sven@gt; 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 lt;sebastian@gt; wrote: Can somebody please clarify if this is a bug or feature? thanks On Jan 31, 2014, at 9:03 PM, Sebastian Sastre lt;SEBASTIAN@gt; wrote: self assert: Date today = Date today. today := Date today translateTo: 2 hours. self assert: today = Date today Is this right? -- View this message in context: http://forum.world.st/Comparing-dates-tp4740789p4741022.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] How to suck (and yet be awesome)
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 I like her point of view. I will change what I will wrote in my book and it is related to the discussion with the pool dictionary. stef
Re: [Pharo-dev] Comparing dates
#translateTo: just shifts the timezone. So he's not adding hours to anything. Why are you adding hours to a Date in the first place? I don't understand. Does that make it the next day or the same day 2 hours past the start of the day in whatever timezone you are in, intuitively? I vote: b. Bug. #= should compare calendar (gregorian, julian etc,), year, month, day or year, day # of year sebast...@flowingconcept.com wrote On Feb 1, 2014, at 12:26 PM, Sven Van Caekenberghe lt; sven@ gt; 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 lt; sebastian@ gt; wrote: Can somebody please clarify if this is a bug or feature? thanks On Jan 31, 2014, at 9:03 PM, Sebastian Sastre lt; SEBASTIAN@ gt; wrote: self assert: Date today = Date today. today := Date today translateTo: 2 hours. self assert: today = Date today Is this right? -- View this message in context: http://forum.world.st/Comparing-dates-tp4740789p4741029.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] Seaside extensions and lowercase package names in Pharo
Chris There are several points: - we will maintain compatibility when filein/out using * - now I was not aware that the class extensions should be lower case. - Pharo should clean the packages because some of the extensions are for packages not existing anymore and other edge cases. Stef On Fri, Jan 31, 2014 at 3:57 AM, Torsten Bergmann asta...@gmx.de wrote: Now that Pharo uses real packages beside categories I see some lowercase ghost packages in Monticello Browser list after loading Seaside. To reproduce just load Seaside using config browser and check in Monticello browser. I guess this is coming from methods in lowercase extension categories like *seaside-pharo-core which do not really match Seaside-Pharo-Core package. Any comments? Using a star (*) and all-lowercase method category names has been the convention for PackageInfo / Monticello for method extensions since the beginning (that is, for many many years now). You'll undoubtedly run into this several more times - at least you will when bringing in older Monticello packages or those created outside of Pharo. Not all, but some. -cbc Thx T.
Re: [Pharo-dev] Can someone help me with this issue 12469 (Sometimes an empty protocol is created)
Thank you, Nicolai, for the fix ! On 02 Feb 2014, at 19:12, Nicolai Hess nicolaih...@web.de wrote: Thank you. 2014-02-01 Sven Van Caekenberghe s...@stfx.eu: On 01 Feb 2014, at 23:03, Sean P. DeNigris s...@clipperadams.com wrote: Nicolai Hess wrote Every time the slice marks the all classes and methods as changed, I've experienced that when viewing changes for a whole slice. If you view the changes for each package individually instead, you should see it is fine. Yeah, it seems to be a fluke, very confusing though. I see Sven has created a new slice for the monkey... And it seemed to have passed.
Re: [Pharo-dev] ZTimestampmonthName spelling error
Thank you for the fix, Sven. It works fine now. Sabine On Sat, Feb 1, 2014 at 5:26 PM, Sven Van Caekenberghe s...@stfx.eu wrote: Sabine, On 01 Feb 2014, at 15:15, Sabine Knöfel sabine.knoe...@gmail.com wrote: Hi Sven, thank you for the quick fix. It works fine now. I do not call this directly but from DateAndTime date: self endDate time: self endTime Your example: I am no english native speaker but I assume, that 'saterday' should be spelled as 'saturday'. If yes, there are several occurences of saterday. Terrible spelling of me! === Name: ZTimestamp-SvenVanCaekenberghe.33 Author: SvenVanCaekenberghe Time: 1 February 2014, 5:18:50.139922 pm UUID: 40111894-d387-432a-a3e1-2245af4a269b Ancestors: ZTimestamp-SvenVanCaekenberghe.32 Even worse: Saterday = Saturday (thx Sabine Knöfel) === ConfigurationOfZTimestamp has been updated everywhere. I saw this when trying your example: (ZTimestampFormat fromString: 'Saterday, 3 February, 2001') german; format: Date today. =='Samstag, 1 Februar, 2014' (ZTimestampFormat fromString: 'Saturday, 3 February, 2001') german; format: Date today. =='Samurday, 1 Februar, 2014' Also, 'Samurday' is no german word. 'Saturday' means 'Samstag' in German. Now that example should work: (ZTimestampFormat fromString: 'Saturday, 3 February, 2001') german; format: Date today. = 'Samstag, 1 Februar, 2014' Thanks for the feedback. Sven Regards Sabine On Sat, Feb 1, 2014 at 1:31 PM, Sven Van Caekenberghe s...@stfx.eu wrote: Sabine, On 01 Feb 2014, at 12:52, Sabine Knöfel sabine.knoe...@gmail.com wrote: Hi Sven, could you change Februari into February please? Ah, terrible typo, it was all over the place. === Name: ZTimestamp-SvenVanCaekenberghe.32 Author: SvenVanCaekenberghe Time: 1 February 2014, 1:27:02.50151 pm UUID: 70fd3b88-e15e-4139-922c-9c602e3fc532 Ancestors: ZTimestamp-SvenVanCaekenberghe.31 The English spelling of the 2nd month name was consistently wrong: Februari instead of the correct February (thx Sabine Knöfel); Now use #monthIndex instead of the less consistent #month === Btw, did you know you can do: (ZTimestampFormat fromString: 'Saterday, 3 February, 2001') german; format: Date today. = 'Samstag, 1 Februar, 2014' Regards, Sven (I use http://mc.stfx.eu/Neo, this is the right place?) Regards Sabine ZTimestampmonthName Return the English name of the month of the receiver, according to the Gregorian calendar, a Symbol ^ #(January Februari March April May June July August September October November December) at: self monthIndex -- View this message in context: http://forum.world.st/ZTimestamp-monthName-spelling-error-tp4740821.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
[Pharo-dev] leadingChar and friends
During my journey to the leadingChar realm I took notes and I share them with you. leadingChar: leadChar code: code code = 16r40 ifTrue: [ self error: 'code is out of range'. ]. leadChar = 256 ifTrue: [ self error: 'lead is out of range'. ]. code 256 ifTrue: [ ^self value: code ]. ^self value: (leadChar bitShift: 22) + code. charCode ^ (value bitAnd: 16r3F). leadingChar ^ (value bitAnd: (16r3FC0)) bitShift: -22. characterSet ^ EncodedCharSet charsetAt: self leadingChar = a character encodes the characterSet. Why are we using Latin1leadingChar ^ 0. UnicodeleadingChar ^ 0 and I do not get why GreekEnvironmentleadingChar ^0 Latin2EnvironmentleadingChar ^0 Latin1EnvironmentleadingChar ^0 Latin9EnvironmentleadingChar ^0 RussianEnvironmentleadingChar ^0 SimplifiedChineseEnvironmentleadingChar ^0 == I do not understand why Unicode is declared as 1 and not 0. Unicode classinitialize EncodedCharSet declareEncodedCharSet: self atIndex: 0+1. EncodedCharSet declareEncodedCharSet: self atIndex: 256. I do not understand why Latin1 does not use declareEncodedCharSet Latin1 classinitialize self initialize compoundTextSequence := String streamContents: [ :s | s nextPut: (Character value: 27). s nextPut: $(. s nextPut: $B ]. rightHalfSequence := String streamContents: [ :s | s nextPut: (Character value: 27). s nextPut: $-. s nextPut: $A ] I started to distribute the initialization into subclasses starting from this method: declareEncodedCharSet: anEncodedCharSetOrLanguageEnvironmentClass atIndex: aNumber this method is used to modularize the old initialize method: EncodedCharSets at: 0+1 put: Unicode. EncodedCharSets at: 1+1 put: JISX0208. EncodedCharSets at: 2+1 put: GB2312. EncodedCharSets at: 3+1 put: KSX1001. EncodedCharSets at: 4+1 put: JISX0208. EncodedCharSets at: 5+1 put: JapaneseEnvironment. EncodedCharSets at: 6+1 put: SimplifiedChineseEnvironment. EncodedCharSets at: 7+1 put: KoreanEnvironment. EncodedCharSets at: 8+1 put: GB2312. EncodedCharSets at: 12+1 put: KSX1001. EncodedCharSets at: 13+1 put: GreekEnvironment. EncodedCharSets at: 14+1 put: Latin2Environment. EncodedCharSets at: 15+1 put: RussianEnvironment. EncodedCharSets at: 17+1 put: Latin9Environment. EncodedCharSets at: 256 put: Unicode. and indeed Latin1Environment was not part of the list. Now apparently we can remove Latin1 because EncodedCharSets of EncodedCharSet do not contain Latin1 == No senders emitSequenceToResetStateIfNeededOn: aStream forState: state rightDirection Funny nextPutRightHalfValue: ascii toStream: aStream withShiftSequenceIfNeededForTextConverterState: state nextPutValue: ascii toStream: aStream withShiftSequenceIfNeededForTextConverterState: state == Ideas of cleaning steps step one: what if CharacterleadingChar ^ 0 We can probably kill the encodedSet. It looks like Latin1Environment and Latin1 are not used. Stef
[Pharo-dev] WhatsUp from: 2014-02-03 until: 2014-02-16
Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2014-02-16 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)
Re: [Pharo-dev] Comparing dates
Please use #assert:equals (that won't change the result though :-)) On Feb 1, 2014 12:04 AM, Sebastian Sastre sebast...@flowingconcept.com wrote: self assert: Date today = Date today. today := Date today translateTo: 2 hours. self assert: today = Date today Is this right?
[Pharo-dev] [pharo-project/pharo-core] 857012: 30736
Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 85701269c487dc49fa2fd4f7c6b1f35593baf903 https://github.com/pharo-project/pharo-core/commit/85701269c487dc49fa2fd4f7c6b1f35593baf903 Author: Jenkins Build Server bo...@pharo-project.org Date: 2014-02-02 (Sun, 02 Feb 2014) Changed paths: A Nautilus.package/PackageTreeNautilusUI.class/instance/package/alertCategoryName_exitstsAlreadyIn_.st A Nautilus.package/PackageTreeNautilusUI.class/instance/package/category_existsIn_.st M Nautilus.package/PackageTreeNautilusUI.class/instance/private dispatch/renameClassCategory_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script389.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30736.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Slot.package/BitsLayout.class/instance/testing/isBytes.st A Slot.package/BitsLayout.class/instance/testing/isWords.st A Slot.package/ByteLayout.class/instance/testing/isBytes.st A Slot.package/WordLayout.class/instance/testing/isBytes.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests-integration/testFixedClassWhenTraitCompositionChangedShouldAnnounceClassModified.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests-integration/testFixedClassWithTraitCreatedShouldntAnnounceClassModified.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests-integration/testVariableByteClassWhenTraitCompositionChangedShouldAnnounceClassModified.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests-integration/testVariableByteClassWithTraitCreatedShouldntAnnounceClassModified.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests-integration/testVariableClassWhenTraitCompositionChangedShouldAnnounceClassModified.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests-integration/testVariableClassWithTraitCreatedShouldntAnnounceClassModified.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests-integration/testVariableWordClassWhenTraitCompositionChangedShouldAnnounceClassModified.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests-integration/testVariableWordClassWithTraitCreatedShouldntAnnounceClassModified.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests-integration/testWeakClassWhenTraitCompositionChangedShouldAnnounceClassModified.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests-integration/testWeakClassWithTraitCreatedShouldntAnnounceClassModified.st M SlotTests.package/TOne.class/README.md M SlotTests.package/TTwo.class/README.md M SlotTests.package/TestSharedPool.class/README.md M System-Announcements.package/ClassModifiedClassDefinition.class/README.md A Traits.package/TClass.class/instance/subclass creation - private/subclass_uses_with_.st M Traits.package/TClass.class/instance/subclass creation/subclass_uses_instanceVariableNames_classVariableNames_poolDictionaries_category_.st M Traits.package/TClass.class/instance/subclass creation/variableByteSubclass_uses_instanceVariableNames_classVariableNames_poolDictionaries_category_.st M Traits.package/TClass.class/instance/subclass creation/variableSubclass_uses_instanceVariableNames_classVariableNames_poolDictionaries_category_.st M Traits.package/TClass.class/instance/subclass creation/variableWordSubclass_uses_instanceVariableNames_classVariableNames_poolDictionaries_category_.st M Traits.package/TClass.class/instance/subclass creation/weakSubclass_uses_instanceVariableNames_classVariableNames_poolDictionaries_category_.st Log Message: --- 30736 12727 Duplicated categories in Nautilus https://pharo.fogbugz.com/f/cases/12727 12157 Wrong announcement of ClassModifiedClassDefinition https://pharo.fogbugz.com/f/cases/12157 11670 strange MC package Generated-code-non-existing-package https://pharo.fogbugz.com/f/cases/11670 http://files.pharo.org/image/30/30736.zip
[Pharo-dev] [pharo-project/pharo-core]
Branch: refs/tags/30736 Home: https://github.com/pharo-project/pharo-core
Re: [Pharo-dev] test failures in downloaded image 30733
On 02 Feb 2014, at 16:27, b...@openinworld.com wrote: Thanks for your feedback Marcus. A couple of thought inline... Marcus Denker wrote: On 02 Feb 2014, at 14:31, b...@openinworld.com wrote: For diligence and curiosity leading up to the Pharo3 release, I downloaded build image 30733 (with PharoLauncher) Another wonderful thing is that tests are fine when run individually, but fail when running all tests. It seems that when clicking on the failed test, the test is re-run and that result is debugged - but sometimes the error doesn't occur. It would be great the context of the error in the original execution was stored so that actual error could be inspected. Indeed, (to dream) presuming you're working off fresh CI build, it would be cool if using Fuel in one step you send the context of the original error (with CI build meta-info attached) to someone else's PharoLauncher, which automatically downloads the required CI build, and launches with the Fuel file loaded and ready to debug. On the ci server this is already done: failing tests are serialise with Fuel for debugging. In addition, the image is save and can be downloaded (in the state after the test run). 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. No external packages loaded here. Launcher? It’s external in the sense that this is not code that is in the image when we run all tests on the build server. btw, What was your OS environment? Mac 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. I've seen that happening previously. In trying to understand the reality of this, perhaps... * check if this is okay is an open ended question that doesn't have a deliverable to drive people to action. How do you know when its time to report success/failure? * people do download and try it but its only shallow testing * people only report by exception. Perhaps a more defined task such as Run All Tests is easier for people to do (single button press) and to report success/failure. PharoLaucher also makes it easier and quicker to do this. You don't need to call it a Release Candidate. Just have a specified version that multiple people run in multiple environments. Of course, that could also open up a can of worms of being hard from your end to dealing every test failure due to other people's environments. There would need a pragmatic approach about which ones to deal with to stay on schedule with the release date. yes… its important that we don burn ourselves while doing the release, that is why the idea was to move as much things upfront as possible (“the build is the release unchanged”) Marcus
