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

Re: [Pharo-project] [Vm-dev] Android Cog VM/Pharo Builds at INRIA Jenkins

by David T. Lewis

Really nice! Thank you for this Android VM work, and also for the excellent documentation on installation and usage. (CC to squeak-dev also) Dave On Tue, Aug 07, 2012 at 10:04:48AM -0400, Dmitry Golubovsky wrote: > > Hi, > > There are two CI (continuous integration) jobs running periodically at > the INRIA Jenkins server: CogDroid and PharoDroid. The former is an > unbundled NonJIT Cog VM for Android which can run any Smalltalk image > original Cog VM can run. The latter is the same Cog VM bundled with a > generic Pharo 1.4 Smalltalk image. These two builds complement each > other, and together they comprise an Android analog of the one-click > Pharo distribution: a practically usable piece of software ready for > development and exploration of possible uses of Smalltalk on mobile > devices. > > Whoever is interested to try Pharo and other compatible Smalltalk > implementations on Android devices are welcome to use these builds. A > brief overview with installation and usage recommendations can be > found here: > > http://code.google.com/p/squeakvm-tablet/wiki/JenkinsBuilds > > The developer of CogDroid and PharoDroid hopes that these new Android > applications will help the adoption of Smalltalk for writing > applications for mobile devices. > > Any thoughts, suggestions and critics are welcome. > > Thanks. > > -- > Dmitry Golubovsky > > Anywhere on the Web

Aug. 7, 2012

[Pharo-project] Android Cog VM/Pharo Builds at INRIA Jenkins

by Dmitry Golubovsky

Hi, There are two CI (continuous integration) jobs running periodically at the INRIA Jenkins server: CogDroid and PharoDroid. The former is an unbundled NonJIT Cog VM for Android which can run any Smalltalk image original Cog VM can run. The latter is the same Cog VM bundled with a generic Pharo 1.4 Smalltalk image. These two builds complement each other, and together they comprise an Android analog of the one-click Pharo distribution: a practically usable piece of software ready for development and exploration of possible uses of Smalltalk on mobile devices. Whoever is interested to try Pharo and other compatible Smalltalk implementations on Android devices are welcome to use these builds. A brief overview with installation and usage recommendations can be found here: http://code.google.com/p/squeakvm-tablet/wiki/JenkinsBuilds The developer of CogDroid and PharoDroid hopes that these new Android applications will help the adoption of Smalltalk for writing applications for mobile devices. Any thoughts, suggestions and critics are welcome. Thanks. -- Dmitry Golubovsky Anywhere on the Web

Aug. 7, 2012

Re: [Pharo-project] R.I.P. SystemChangeNotifier

by Mariano Martinez Peck

On Tue, Aug 7, 2012 at 12:50 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > Hi, > > Today we finally finish the removal of SystemChangeNotifier. This is a big > step forward to unify all system events into announcements. Current > notification center is named "SystemAnnouncer" and all events has been > reified into more meaningful announcements... > This operation was really hard because is like changing the heart of a > living person :) > For 99.99% of users, this will be absolute transparent, but there are some > cases where maybe some problems emerge. Please, take this into account to > migrate your code soon. > Don't wait until is to late! > > mmmmm did you remove #doSilently: ? -- Mariano http://marianopeck.wordpress.com

Aug. 7, 2012

Re: [Pharo-project] R.I.P. SystemChangeNotifier

by camille teruel

Cool! We won't miss it! Le mardi 7 aoÃ»t 2012, Guillermo Polito <guillermopolito(a)gmail.com> a Ã©crit : > Great!! :D > > On Tue, Aug 7, 2012 at 12:50 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> Hi, >> >> Today we finally finish the removal of SystemChangeNotifier. This is a big step forward to unify all system events into announcements. Current notification center is named "SystemAnnouncer" and all events has been reified into more meaningful announcements... >> This operation was really hard because is like changing the heart of a living person :) >> For 99.99% of users, this will be absolute transparent, but there are some cases where maybe some problems emerge. Please, take this into account to migrate your code soon. >> Don't wait until is to late! >> >> Cheers, >> Esteban > >

Aug. 7, 2012

Re: [Pharo-project] [update 2.0] #20245

by Camillo Bruni

>>> >> Shouldn't Jenkins help us here? >> > > > We have about three options: > 1) use Jenkins for updates checking > - maybe it was the original plan but it doesn't work because we do not > want to rollback updates I think the original plan was to only use images that completed all the tests. Much like the VM builds. > 2) create a fake update server and create Jenkins jobs that will check the > updates and will not pass the dirty ones to mainstream I guess that goes along with #1, we should be able to rollback changes easily. And yes, we should have a 2 level publish system, first internally for checking and only then publicly.. > 3) improve the Monkey do do more checks on fixes of issues - to run more > tests etc. And do not allow fixes that do not pass. the monkey should filter out as much as possible. since at that point we didn't change anything yet, so it's the ideal moment to fix things :) - do strict testing (of everything) - do some code critics (undeclared vars ...) - provide simple heuristics about the complexity of the fix

Aug. 7, 2012

Re: [Pharo-project] [update 2.0] #20245

by Pavel Krivanek

On Tue, Aug 7, 2012 at 10:37 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Tue, Aug 7, 2012 at 10:32 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com>wrote: > >> We are starting to have a lot of failing tests again >> >> CompressionTests.Archive.ZipArchiveTest.testCreateWithRelativeNames >> CompressionTests.Archive.ZipArchiveTest.testZip >> FileSystem.Tests.Disk.DiskFileSystemTest.testEntryAt >> FileSystem.Tests.Memory.MemoryFileSystemTest.testEntryAt >> KernelTests.Chronology.StopwatchTest.testSingleTiming >> KernelTests.Chronology.StopwatchTest.testStartStop >> KernelTests.Chronology.TimeStampTest.testComparing >> KernelTests.Chronology.TimeStampTest.testSorting >> Zinc.Tests.ZnLogSupportTests.testLogEvent >> RPackage.Tests.RPackageWithDoTest.testInvariant >> Tests.Release.ReleaseTest.testMethodsWithUnboundGlobals >> Tests.Release.ReleaseTest.testUndeclared >> >> I think that we have to upgrade the monkey checking to stop such >> regressions... >> >> > Shouldn't Jenkins help us here? > We have about three options: 1) use Jenkins for updates checking - maybe it was the original plan but it doesn't work because we do not want to rollback updates 2) create a fake update server and create Jenkins jobs that will check the updates and will not pass the dirty ones to mainstream 3) improve the Monkey do do more checks on fixes of issues - to run more tests etc. And do not allow fixes that do not pass. The current state when we do not rollback updates and have poor issues checking may seem to look good for the fast development of the system with big radical changes but in reality it ends in state when if somebody wants to improve something he firstly has to fix things that started to be broken. -- Pavel > > >> -- Pavel >> >> On Mon, Aug 6, 2012 at 4:27 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> > 20245 >> > ----- >> > >> > Issue 6510: update zinc >> > http://code.google.com/p/pharo/issues/detail?id=6510 >> > >> > Issue 6514: Add allDefinedExtensionMethods to RPackage >> > http://code.google.com/p/pharo/issues/detail?id=6514 >> > >> > Issue 6521: RPackageOrganizer>>initialize does not initialize from >> scratch >> > http://code.google.com/p/pharo/issues/detail?id=6521 >> > >> > Issue 6523: Bug in RPackage >> systemSubPackages >> > http://code.google.com/p/pharo/issues/detail?id=6523 >> > >> > Issue 6526: RPackage is not removing extensions from a removed class >> > http://code.google.com/p/pharo/issues/detail?id=6526 >> > >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > >

Aug. 7, 2012

Re: [Pharo-project] R.I.P. SystemChangeNotifier

by Guillermo Polito

Great!! :D On Tue, Aug 7, 2012 at 12:50 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > Hi, > > Today we finally finish the removal of SystemChangeNotifier. This is a big > step forward to unify all system events into announcements. Current > notification center is named "SystemAnnouncer" and all events has been > reified into more meaningful announcements... > This operation was really hard because is like changing the heart of a > living person :) > For 99.99% of users, this will be absolute transparent, but there are some > cases where maybe some problems emerge. Please, take this into account to > migrate your code soon. > Don't wait until is to late! > > Cheers, > Esteban >

Aug. 7, 2012

[Pharo-project] R.I.P. SystemChangeNotifier

by Esteban Lorenzano

Hi, Today we finally finish the removal of SystemChangeNotifier. This is a big step forward to unify all system events into announcements. Current notification center is named "SystemAnnouncer" and all events has been reified into more meaningful announcements... This operation was really hard because is like changing the heart of a living person :) For 99.99% of users, this will be absolute transparent, but there are some cases where maybe some problems emerge. Please, take this into account to migrate your code soon. Don't wait until is to late! Cheers, Esteban

Aug. 7, 2012

[Pharo-project] [update 2.0] #20246

by Esteban Lorenzano

20246 ----- Issue 6518: SystemChangeNotifier - cleanup step 4 http://code.google.com/p/pharo/issues/detail?id=6518 Issue 6524: StartupPreferences loads non-Smalltalk files http://code.google.com/p/pharo/issues/detail?id=6524 Issue 6528: GroupAnnouncer announcer DNU http://code.google.com/p/pharo/issues/detail?id=6528 Issue 6529: Method changes not picked up by MC Browser http://code.google.com/p/pharo/issues/detail?id=6529

Aug. 7, 2012

Re: [Pharo-project] Jenkins: SCM polling activity overload

by Camillo Bruni

how hard can it be.... (I think my silly laptop here handles more...) seriously this piece of software kills my last nerves :D On 2012-08-07, at 04:10, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > See https://ci.lille.inria.fr/pharo/descriptor/hudson.triggers.SCMTrigger/ : > > There are more SCM polling activities scheduled than handled, so the threads > are not keeping up with the demands. Check if your polling is hanging, > and/or increase the number of threads if necessary. > The following polling activities are currently in progress: > > Project â > Running for > Scripts-download 18 hr > > > > > -- > View this message in context: http://forum.world.st/Jenkins-SCM-polling-activity-overload-tp4643404.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Aug. 7, 2012