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

[Pharo 8.0] Build #643: Remove-dependency-between-FileSystem-Core-and-Deprecated-file-package

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #643 was: SUCCESS. The Pull Request #4340 was integrated: "Remove-dependency-between-FileSystem-Core-and-Deprecated-file-package" Pull request url: https://github.com/pharo-project/pharo/pull/4340 Issue Url: https://github.com/pharo-project/pharo/issues/Remove Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 18, 2019

[Pharo 8.0] Build #642: Remove-PNGReader-test-missing-resources

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #642 was: FAILURE. The Pull Request #4345 was integrated: "Remove-PNGReader-test-missing-resources" Pull request url: https://github.com/pharo-project/pharo/pull/4345 Issue Url: https://github.com/pharo-project/pharo/issues/Remove Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 18, 2019

[Pharo 8.0] Build #641: Calypso-should-not-depend-on-deprecated-streams

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #641 was: FAILURE. The Pull Request #4342 was integrated: "Calypso-should-not-depend-on-deprecated-streams" Pull request url: https://github.com/pharo-project/pharo/pull/4342 Issue Url: https://github.com/pharo-project/pharo/issues/Calypso Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 18, 2019

[Pharo 8.0] Build #640: StartupPreferences-should-not-depend-on-deprecated-streams

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #640 was: FAILURE. The Pull Request #4348 was integrated: "StartupPreferences-should-not-depend-on-deprecated-streams" Pull request url: https://github.com/pharo-project/pharo/pull/4348 Issue Url: https://github.com/pharo-project/pharo/issues/StartupPreferences Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 18, 2019

fosdem

by ducasse

FOSDEM We now invite proposals for main track presentations, developer rooms, stands and lightning talks. FOSDEM offers open source and free software developers a place to meet, share ideas and collaborate. Renowned for being highly developer- oriented, the event brings together some 8000+ geeks from all over the world. The twentieth edition will take place on Saturday 1st and Sunday 2nd February 2020 at the usual location: ULB Campus Solbosch in Brussels. So any ideas how to coordinate efforts? Stef

Aug. 17, 2019

[Pharo 8.0] Build #639: Ensure-all-class-creation-methods-have-package-equivalent-instead-of-category

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #639 was: FAILURE. The Pull Request #4338 was integrated: "Ensure-all-class-creation-methods-have-package-equivalent-instead-of-category" Pull request url: https://github.com/pharo-project/pharo/pull/4338 Issue Url: https://github.com/pharo-project/pharo/issues/Ensure Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 17, 2019

Re: [Pharo-dev] possible Windows Update "1903" Iceberg problem

by ducasse

> On 17 Aug 2019, at 12:50, Ben Coman <btc(a)openinworld.com> wrote: > > hi Stef, > I feel you missed my point. Probably I wasn't clear this has already been tested with latest Pharo 8 launched by PharoLauncher. > The problem occurs with Pharo 7.0.3(64 bit) and with Pharo8.0-SNAPSHOT-build.635(64 bit) > after Microsoft Windows Update 1903... > https://www.computerworld.com/article/3409621/microsoft-starts-windows-10s-… <https://www.computerworld.com/article/3409621/microsoft-starts-windows-10s-…> > > If indeed 1903 is the cause, with this update now being *forced* down on people, this will potentially soon impact more and more Windows users. > But my guess that 1903 is the culprit needs to be confirmed. > So I am requesting someone with access to multiple Windows machines directly compare a 1903 machine with a pre-1903 machine. indeed I misunderstood you :) > > cheers -ben > > On Sat, 17 Aug 2019 at 12:58, ducasse <stepharo(a)netcourrier.com <mailto:stepharo@netcourrier.com>> wrote: > Hi ben > > in the pharo launcher if you click on P8.0 (development version) you get access to all the builds. > > Stef > >> On 16 Aug 2019, at 16:02, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote: >> >> IThis morning the May 2019 Windows Update "1903" forced itself onto my computer and now 64-bits Pharo seems to have a problem with git_remote_fetch() FFI callout. I no longer have a non-1903 machine to directly compare behaviour before "1903". Can someone familiar with this area with both "pre-1903" and "1903" machines triage whether "1903" is indeed the cause? >> >> A few other recent reports are noted here... >> https://github.com/pharo-project/pharo/issues/3418 <https://github.com/pharo-project/pharo/issues/3418> >> >> cheers -ben >

Aug. 17, 2019

Re: [Pharo-dev] possible Windows Update "1903" Iceberg problem

by Ben Coman

hi Stef, I feel you missed my point. Probably I wasn't clear this has already been tested with latest Pharo 8 launched by PharoLauncher. The problem occurs with Pharo 7.0.3(64 bit) and with Pharo8.0-SNAPSHOT-build.635(64 bit) after Microsoft Windows Update 1903... https://www.computerworld.com/article/3409621/microsoft-starts-windows-10s-… If indeed 1903 is the cause, with this update now being *forced* down on people, this will potentially soon impact more and more Windows users. But my guess that 1903 is the culprit needs to be confirmed. So I am requesting someone with access to multiple Windows machines directly compare a 1903 machine with a pre-1903 machine. cheers -ben On Sat, 17 Aug 2019 at 12:58, ducasse <stepharo(a)netcourrier.com> wrote: > Hi ben > > in the pharo launcher if you click on P8.0 (development version) you get > access to all the builds. > > Stef > > On 16 Aug 2019, at 16:02, Ben Coman <btc(a)openinworld.com> wrote: > > IThis morning the May 2019 Windows Update "1903" forced itself onto my > computer and now 64-bits Pharo seems to have a problem with > git_remote_fetch() FFI callout. I no longer have a non-1903 machine to > directly compare behaviour before "1903". Can someone familiar with this > area with both "pre-1903" and "1903" machines triage whether "1903" is > indeed the cause? > > A few other recent reports are noted here... > https://github.com/pharo-project/pharo/issues/3418 > > cheers -ben > > >

Aug. 17, 2019

[Pharo 8.0] Build #638: 4314-Cannot-use-slot-as-class-variable-Raise-explicit-error

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #638 was: FAILURE. The Pull Request #4331 was integrated: "4314-Cannot-use-slot-as-class-variable-Raise-explicit-error" Pull request url: https://github.com/pharo-project/pharo/pull/4331 Issue Url: https://github.com/pharo-project/pharo/issues/4314 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 17, 2019

[Pharo 8.0] Build #637: Revert "4204-Should-SystemDictionary-sort-classes-by-name"

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #637 was: FAILURE. The Pull Request #4333 was integrated: "Revert "4204-Should-SystemDictionary-sort-classes-by-name"" Pull request url: https://github.com/pharo-project/pharo/pull/4333 Issue Url: https://github.com/pharo-project/pharo/issues/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 17, 2019