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

Re: [Pharo-project] NBOpenGL issue with latest 1.4 Pharo image and latest NBCog VM

by Igor Stasenko

I think this is because previously i used Carbon configuration for building VM with NativeBoost. Now its Cocoa.. So, what happens there is best to be answered by Esteban :) On 24 March 2012 16:26, Lawson English <lenglish5(a)cox.net> wrote: > I isolated the issue. Both the latest NBCog and the CogVM for the Mac show > this visual artifact when resizing the screen using Pharo 1.4 latest image: > > http://www.youtube.com/watch?v=0T_WGYWh5JM > > > I dropped back to NBCog dated 12/11/11 and the artifact doesn't show. At the > same time, the procedure below works without errors. > > > Lawson > > > > On 3/23/12 9:49 AM, Lawson English wrote: >> >> I procure the latest and greatest of each of the components: >> >> NBCog, Pharo 1.4.image Pharo 1.4.changes etc >> >> I procure the latest CofigurationOfNBOpenGL from: >> >> MCHttpRepository >> Â Â location: 'http://www.squeaksource.com/NBOpenGL' >> Â Â user: '' >> Â Â password: ''. >> >> I run the following in a workspace: >> >> ConfigurationOfNBOpenGL project lastVersion load. >> >> NBInstaller install. >> >> Now, when I evaluate: Â GLTTRenderingDemo new OpenInWorld. >> >> >> Pharo hangs. cmd+. doesn't interrupt. >> >> >> Sigh.... >> >> >> Lawson >> >> > -- Best regards, Igor Stasenko.

March 24, 2012

Re: [Pharo-project] 1.4 is now green...

by Nicolas Cellier

Then if I introduce a new test documenting an old bug, it will then be rejected right ? I wonder if I'd really want such a dumb system without an ounce of human expertise... Nicolas Le 24 mars 2012 15:37, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> a Ã©crit : > >> > >> > >>> .. 1.4 has now all tests green on jenkins (Mac and Linux). > >>> > >>> The nice side-effect is that all the jobs that check VM builds are now > green, too. > >>> > >>> https://ci.lille.inria.fr/pharo/view/Pharo%201.4/ > >>> > >>> The idea is to now to just never ever integrate anything that makes a > test break... > >> > >> ok but it means that we should run 20 min tests each we integrate > somethingâ¦. how boring. > >> We can try. > >> > >> Stef > > > > That's why you should use a full automatized process .... :whistle: ^^ > > indeed. > I want :) > > Stef >

March 24, 2012

Re: [Pharo-project] 1.4 is now green...

by Schwab,Wilhelm K

Stef, Naive question: could you simply let Jenkins do the testing, and investigate/roll-back if it reports problems? If Jenkins can reliably, based on unit tests, report a last successful build, you might be at a good place. In that world, you would integrate and let Jenkins tell you if it was a bad thing to do. Like I said, it might be naive. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] Sent: Saturday, March 24, 2012 10:37 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] 1.4 is now green... >> >> >>> .. 1.4 has now all tests green on jenkins (Mac and Linux). >>> >>> The nice side-effect is that all the jobs that check VM builds are now green, too. >>> >>> https://ci.lille.inria.fr/pharo/view/Pharo%201.4/ >>> >>> The idea is to now to just never ever integrate anything that makes a test break... >> >> ok but it means that we should run 20 min tests each we integrate somethingâ¦. how boring. >> We can try. >> >> Stef > > That's why you should use a full automatized process .... :whistle: ^^ indeed. I want :) Stef

March 24, 2012

Re: [Pharo-project] 1.4 is now green...

by StÃ©phane Ducasse

>> >> >>> .. 1.4 has now all tests green on jenkins (Mac and Linux). >>> >>> The nice side-effect is that all the jobs that check VM builds are now green, too. >>> >>> https://ci.lille.inria.fr/pharo/view/Pharo%201.4/ >>> >>> The idea is to now to just never ever integrate anything that makes a test break... >> >> ok but it means that we should run 20 min tests each we integrate somethingâ¦. how boring. >> We can try. >> >> Stef > > That's why you should use a full automatized process .... :whistle: ^^ indeed. I want :) Stef

March 24, 2012

Re: [Pharo-project] 1.4 is now green...

by Benjamin

On Mar 24, 2012, at 3:28 PM, StÃ©phane Ducasse wrote: > > On Mar 24, 2012, at 1:46 PM, Marcus Denker wrote: > >> .. 1.4 has now all tests green on jenkins (Mac and Linux). >> >> The nice side-effect is that all the jobs that check VM builds are now green, too. >> >> https://ci.lille.inria.fr/pharo/view/Pharo%201.4/ >> >> The idea is to now to just never ever integrate anything that makes a test break... > > ok but it means that we should run 20 min tests each we integrate somethingâ¦. how boring. > We can try. > > Stef That's why you should use a full automatized process .... :whistle: ^^ Ben > >> >> Marcus >> >> -- >> Marcus Denker -- http://marcusdenker.de >> >> > >

March 24, 2012

Re: [Pharo-project] 1.4 is now green...

by StÃ©phane Ducasse

On Mar 24, 2012, at 1:46 PM, Marcus Denker wrote: > .. 1.4 has now all tests green on jenkins (Mac and Linux). > > The nice side-effect is that all the jobs that check VM builds are now green, too. > > https://ci.lille.inria.fr/pharo/view/Pharo%201.4/ > > The idea is to now to just never ever integrate anything that makes a test break... ok but it means that we should run 20 min tests each we integrate somethingâ¦. how boring. We can try. Stef > > Marcus > > -- > Marcus Denker -- http://marcusdenker.de > >

March 24, 2012

Re: [Pharo-project] NBOpenGL issue with latest 1.4 Pharo image and latest NBCog VM

by Lawson English

I isolated the issue. Both the latest NBCog and the CogVM for the Mac show this visual artifact when resizing the screen using Pharo 1.4 latest image: http://www.youtube.com/watch?v=0T_WGYWh5JM I dropped back to NBCog dated 12/11/11 and the artifact doesn't show. At the same time, the procedure below works without errors. Lawson On 3/23/12 9:49 AM, Lawson English wrote: > I procure the latest and greatest of each of the components: > > NBCog, Pharo 1.4.image Pharo 1.4.changes etc > > I procure the latest CofigurationOfNBOpenGL from: > > MCHttpRepository > location: 'http://www.squeaksource.com/NBOpenGL' > user: '' > password: ''. > > I run the following in a workspace: > > ConfigurationOfNBOpenGL project lastVersion load. > > NBInstaller install. > > Now, when I evaluate: GLTTRenderingDemo new OpenInWorld. > > > Pharo hangs. cmd+. doesn't interrupt. > > > Sigh.... > > > Lawson > >

March 24, 2012

Re: [Pharo-project] 1.4 is now green...

by Damien Cassou

On Sat, Mar 24, 2012 at 1:46 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > .. 1.4 has now all tests green on jenkins (Mac and Linux). Yeahh. Thank you so much all of you and thank you Marcus. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

March 24, 2012

[Pharo-project] 1.4 is now green...

by Marcus Denker

.. 1.4 has now all tests green on jenkins (Mac and Linux). The nice side-effect is that all the jobs that check VM builds are now green, too. https://ci.lille.inria.fr/pharo/view/Pharo%201.4/ The idea is to now to just never ever integrate anything that makes a test break... Marcus -- Marcus Denker -- http://marcusdenker.de

March 24, 2012

[Pharo-project] [update 1.4] #14410

by Marcus Denker

14410 ----- Issue 5539: Clean up unused source file related machinery http://code.google.com/p/pharo/issues/detail?id=5539 Issue 5536: Disabled background color for list is not dark enough http://code.google.com/p/pharo/issues/detail?id=5536 Issue 5461: Test failing: MCFileInTest>>testStWriter http://code.google.com/p/pharo/issues/detail?id=5461 -- Marcus Denker -- http://marcusdenker.de

March 24, 2012