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

Re: [Pharo-project] Increasing bots traffic

by Igor Stasenko

On 23 February 2012 23:01, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 23 February 2012 22:46, Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> Just curious, what is the goal of Jenkins build reports >> - focus developers attention on failing tests >> - marketing of the development process >> > nothing of the above, i think :) oh.. not nothing, of course. Yes they should "focus developers attention on failing tests" but for those who paying attention. There's a little sense putting them on main list, since most of people there do not care anyways :) > It is just a side effect of testing & improving reports from jenkins builds. > For me it is clear that those messages should belong to bugs list, not > to main list. > >> Notice I did not say developing the development process ;) > > > -- > Best regards, > Igor Stasenko. -- Best regards, Igor Stasenko.

Feb. 23, 2012

Re: [Pharo-project] Increasing bots traffic

by Nicolas Cellier

Le 23 fÃ©vrier 2012 23:01, Igor Stasenko <siguctua(a)gmail.com> a Ã©crit : > On 23 February 2012 22:46, Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> Just curious, what is the goal of Jenkins build reports >> - focus developers attention on failing tests >> - marketing of the development process >> > nothing of the above, i think :) > It is just a side effect of testing & improving reports from jenkins builds. > For me it is clear that those messages should belong to bugs list, not > to main list. > Is there such a bug list? >> Notice I did not say developing the development process ;) > > > -- > Best regards, > Igor Stasenko. >

Feb. 23, 2012

Re: [Pharo-project] Increasing bots traffic

by Igor Stasenko

On 23 February 2012 22:46, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > Just curious, what is the goal of Jenkins build reports > - focus developers attention on failing tests > - marketing of the development process > nothing of the above, i think :) It is just a side effect of testing & improving reports from jenkins builds. For me it is clear that those messages should belong to bugs list, not to main list. > Notice I did not say developing the development process ;) -- Best regards, Igor Stasenko.

Feb. 23, 2012

Re: [Pharo-project] Sticky TestRunner Progress Morph

by Nicolas Cellier

Here it is more than sticky, it is haunting the image... I select the morph ctrl+click inspect and evaluate self delete. But then, every time a SystemProgressMorph appears, it contains 3 bars related to the TestRunner that will refuse to close. I have plenty ConfigurationOf loaded or partially loaded, so maybe it's just me... I think it's time to drop the image in the waste basket... Nicolas Le 23 fÃ©vrier 2012 22:42, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> a Ã©crit : > > On Feb 23, 2012, at 10:37 PM, Nicolas Cellier wrote: > >> Is it only my 1.4 image or are the TestRunner Progress Morph sticky ? >> (they don't delete when tests are finished and obfuscate the debug window) > > :) > I just check and when the tests are green no problem > now I debug a test and make it pass the bar stay until I click on itâ¦ > Strange. > >> > >

Feb. 23, 2012

Re: [Pharo-project] Increasing bots traffic

by StÃ©phane Ducasse

On Feb 23, 2012, at 10:46 PM, Nicolas Cellier wrote: > Just curious, what is the goal of Jenkins build reports > - focus developers attention on failing tests > - marketing of the development process > Notice I did not say developing the development process ;) No idea. and the blue color is so strange :) > > Nicolas >

Feb. 23, 2012

Re: [Pharo-project] shadows problem with 1.4

by Igor Stasenko

see my code on issue tracker. On 23 February 2012 22:25, Hilaire Fernandes <hilaire.fernandes(a)edu.ge.ch> wrote: > Ok > > Le 22/02/2012 21:29, StÃ©phane Ducasse a Ã©crit : >> Yes we removed the shadow canvas and I tried to have a look. I just draw the morph instead of the black filled. >> I imagine that shifting the morph from some pixels should be simple but I did not get the time to really look at it. >> >> On Feb 22, 2012, at 10:01 AM, Hilaire Fernandes wrote: >> >>> A change somewhere broke the Morph shadow feature in 1.4. >>> Gary et al. do you have any idea? >>> See http://code.google.com/p/pharo/issues/detail?id=5314 >>> >>> Hilaire >>> >>> -- >>> Dr. Geo -- http://www.drgeo.eu >>> >>> >> >> >> > > > -- > Dr. Geo -- http://www.drgeo.eu > > -- Best regards, Igor Stasenko.

Feb. 23, 2012

[Pharo-project] Increasing bots traffic

by Nicolas Cellier

Just curious, what is the goal of Jenkins build reports - focus developers attention on failing tests - marketing of the development process Notice I did not say developing the development process ;) Nicolas

Feb. 23, 2012

Re: [Pharo-project] Sticky TestRunner Progress Morph

by StÃ©phane Ducasse

On Feb 23, 2012, at 10:37 PM, Nicolas Cellier wrote: > Is it only my 1.4 image or are the TestRunner Progress Morph sticky ? > (they don't delete when tests are finished and obfuscate the debug window) :) I just check and when the tests are green no problem now I debug a test and make it pass the bar stay until I click on itâ¦ Strange. >

Feb. 23, 2012

[Pharo-project] Sticky TestRunner Progress Morph

by Nicolas Cellier

Is it only my 1.4 image or are the TestRunner Progress Morph sticky ? (they don't delete when tests are finished and obfuscate the debug window)

Feb. 23, 2012

[Pharo-project] [update 1.4] #14350

by StÃ©phane Ducasse

14350 ----- - Issue 5365: Adding to the system useful extensions from Ecompletion http://code.google.com/p/pharo/issues/detail?id=5365 - Issue 5364: Added to Shout the Ecompletion extensions http://code.google.com/p/pharo/issues/detail?id=5364

Feb. 23, 2012