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

[Pharo 8.0] Build #6: FAILURE

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

There is a new Pharo build available! The status of the build #6 was: FAILURE. Could not extract further issue information from commit message: reset set -f after using it Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 9, 2019

[Pharo 7.0] Build #114: 22880-GTPlaygroundBasicTest-leaves-empty-protocols

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

There is a new Pharo build available! The status of the build #114 was: FAILURE. The Pull Request #2199 was integrated: "22880-GTPlaygroundBasicTest-leaves-empty-protocols" Pull request url: https://github.com/pharo-project/pharo/pull/2199 Issue Url: https://pharo.fogbugz.com/f/cases/22880 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 9, 2019

[Pharo 7.0] Build #113: 22724-Setting-to-disable-job-interruption

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

There is a new Pharo build available! The status of the build #113 was: SUCCESS. The Pull Request #2034 was integrated: "22724-Setting-to-disable-job-interruption" Pull request url: https://github.com/pharo-project/pharo/pull/2034 Issue Url: https://pharo.fogbugz.com/f/cases/22724 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 9, 2019

[Pharo 8.0] Build #5: 22224-ZipArchiveMember-still-uses-deprecated-RWBinaryOrTextStream-and-MultiByteBinaryOrTextStream

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

There is a new Pharo build available! The status of the build #5 was: FAILURE. The Pull Request #2180 was integrated: "22224-ZipArchiveMember-still-uses-deprecated-RWBinaryOrTextStream-and-MultiByteBinaryOrTextStream" Pull request url: https://github.com/pharo-project/pharo/pull/2180 Issue Url: https://pharo.fogbugz.com/f/cases/22224 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 9, 2019

[Pharo 7.0] Build #112: 22677-Renaming-a-class-variable-in-a-SharedPool-does-not-rename-the-places-where-its-used

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

There is a new Pharo build available! The status of the build #112 was: FAILURE. The Pull Request #2200 was integrated: "22677-Renaming-a-class-variable-in-a-SharedPool-does-not-rename-the-places-where-its-used" Pull request url: https://github.com/pharo-project/pharo/pull/2200 Issue Url: https://pharo.fogbugz.com/f/cases/22677 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 9, 2019

[Pharo 7.0] Build #111: 22877-Update-Iceberg-and-Tonel

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

There is a new Pharo build available! The status of the build #111 was: SUCCESS. The Pull Request #2196 was integrated: "22877-Update-Iceberg-and-Tonel" Pull request url: https://github.com/pharo-project/pharo/pull/2196 Issue Url: https://pharo.fogbugz.com/f/cases/22877 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 9, 2019

[Pharo 7.0] Build #110: 22428-Code-in-TimeProfiler-is-no-longer-highlighted

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

There is a new Pharo build available! The status of the build #110 was: SUCCESS. The Pull Request #2191 was integrated: "22428-Code-in-TimeProfiler-is-no-longer-highlighted" Pull request url: https://github.com/pharo-project/pharo/pull/2191 Issue Url: https://pharo.fogbugz.com/f/cases/22428 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 9, 2019

[Pharo 7.0] Build #109: 22874-System-Settings-package-should-be-removed-since-it-was-splitted

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

There is a new Pharo build available! The status of the build #109 was: FAILURE. The Pull Request #2182 was integrated: "22874-System-Settings-package-should-be-removed-since-it-was-splitted" Pull request url: https://github.com/pharo-project/pharo/pull/2182 Issue Url: https://pharo.fogbugz.com/f/cases/22874 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 9, 2019

[Pharo 7.0] Build #108: 22875-Some-test-packages-are-not-loaded

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

There is a new Pharo build available! The status of the build #108 was: SUCCESS. The Pull Request #2183 was integrated: "22875-Some-test-packages-are-not-loaded" Pull request url: https://github.com/pharo-project/pharo/pull/2183 Issue Url: https://pharo.fogbugz.com/f/cases/22875 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 9, 2019

Fwd: FileSystem and references to FIle

by Reg Krock

Forgot to copy the Pharo dev list. Begin forwarded message: > From: Reg Krock <rkrock3(a)yahoo.ca> > Subject: FileSystem and references to FIle > Date: 8 January, 2019 at 2:05:15 PM EST > To: Guillermo Polito <guillermopolito(a)gmail.com>, Sven Van Caekenberghe <sven(a)stfx.eu> > Cc: Dale Henrichs <dale.henrichs(a)gemtalksystems.com>, Martin McClure <martin.mcclure(a)gemtalksystems.com> > > Guille, > > As I have been working on porting FileStream to Gemstone, I have found that AbstractBinaryStream could be made more generic if the references to File were handled slightly differently. The idea is to delegate the call of File in AbstractBinaryStream to the instance side of File. > > For example: > AbstractBinaryFIleStream >>#flush > File flush: handle > > would be implemented as follows: > > AbstractBinaryFIleStream >>#flush > file flush: handle > > File>>#flush: aHandle > self class flush: aHandle > > From a compatibility perspective, GemStone would then also implement a GsFile>>#flush: and handle the flush as appropriate for GemStone. > > I have looked at the VA Smalltalk code as well and this would also work well with their code base. > > The methods that would need to be changed are: > 1) AbstractBinaryFileStream > atEnd > flush > next:intoBuffer: > next:putAll: > position > position: > readInto:startingAt: > size > sync > 2) BinaryFileStream > close > closed > truncate: > 2) StdioStream > next: > > Other references to File in the FileSystem classes, could the be changed to a FileSystem fileClass which would return the file class for the variation of Smalltalk. > Pharo would return File, GemStone would return GsFile, VA Smalltalk would return CfsFileDescriptor. > > Your thoughts on this are greatly appreciated. > > Regards, > > Reg >

Jan. 8, 2019