- Pharo-dev - lists.pharo.org

Still build errors :(
by ducasse Jan. 29, 2019

Jan. 29, 2019

HI guys we still have some issuesâ¦. I relaunched some jobs but I get regularly [32] Loaded -> ReferenceFinder-Core-tonel.1 --- tonel:///builds/workspace/uest_and_branch_Pipeline_PR- <tonel:///builds/workspace/uest_and_branch_Pipeline_PR-> 2330/32/src â cache <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] Loaded -> Refactoring2-Core-tonel.1 --- tonel:///builds/workspace/uest_and_branch_Pipeline_PR-2330/32/src --- cache <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] Loaded -> Refactoring2-Transformations-tonel.1 --- tonel:///builds/workspace/uest_and_branch_Pipeline_PR-2330/32/src --- cache <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] Loaded -> Refactoring2-Transformations-Tests-tonel.1 --- tonel:///builds/workspace/uest_and_branch_Pipeline_PR-2330/32/src --- cache <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] ...RETRY->BaselineOfIceberg <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] ...RETRY->BaselineOfIcebergFileDoesNotExistException: '/tmp/github--pharovcsicebergv155244117191520248649118411290184974148839.zip' <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] File>>openForWrite: <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] File>>openForRead <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] File class>>openForReadFileNamed: <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] ZipArchive>>readFrom: <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] MetacelloPharo30Platform(MetacelloPharoPlatform)>>downloadZipArchive:to: <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] MCGitHubRepository class(MCGitBasedNetworkRepository class)>>projectDirectoryFrom:version: <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] MCGitHubRepository(MCGitBasedNetworkRepository)>>calculateRepositoryDirectory <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] MCGitHubRepository(MCGitBasedNetworkRepository)>>resolveLocalRespository <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] MCGitHubRepository(MCGitBasedNetworkRepository)>>ensureLocalRepository <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] MCGitHubRepository(MCGitBasedNetworkRepository)>>localRepository <https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen…>[32] MCGitHubRepository(MCGitBasedNetworkRepository)>>goferReferences

2 4

[Pharo 8.0] Build #36: 22033-Use-FuzzyMatcher-in-spotter-search
by ci-pharo-ci-jenkins2＠inria.fr Jan. 28, 2019

Jan. 28, 2019

There is a new Pharo build available! The status of the build #36 was: SUCCESS. The Pull Request #1854 was integrated: "22033-Use-FuzzyMatcher-in-spotter-search" Pull request url: https://github.com/pharo-project/pharo/pull/1854 Issue Url: https://pharo.fogbugz.com/f/cases/22033 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #35: 2321-The-dark-age-is-coming
by ci-pharo-ci-jenkins2＠inria.fr Jan. 28, 2019

Jan. 28, 2019

There is a new Pharo build available! The status of the build #35 was: FAILURE. The Pull Request #2322 was integrated: "2321-The-dark-age-is-coming" Pull request url: https://github.com/pharo-project/pharo/pull/2322 Issue Url: https://pharo.fogbugz.com/f/cases/2321 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #34: 2356-Remove-GT-Spotter-EventRecorder
by ci-pharo-ci-jenkins2＠inria.fr Jan. 28, 2019

Jan. 28, 2019

There is a new Pharo build available! The status of the build #34 was: FAILURE. The Pull Request #2357 was integrated: "2356-Remove-GT-Spotter-EventRecorder" Pull request url: https://github.com/pharo-project/pharo/pull/2357 Issue Url: https://pharo.fogbugz.com/f/cases/2356 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Build problems
by ducasse Jan. 28, 2019

Jan. 28, 2019

2 2

naming convention for pharo-vm/lib/pharo/* directory?
by Dale Henrichs Jan. 28, 2019

Jan. 28, 2019

I am in the process of porting the GemStone-GCI[1] project to Pharo6.1 (32 bit) and Pharo7.0 (64 bit) and I'm curious what the naming convention for the library directories are. For Pharo5.0 and earlier, I copied my 32 bit gemstone gci library files (.so on linux) into the pharo-vm directory. For Pharo6.1 I just figured out that I need to copy the gci library files into the pharo-vm/lib/pharo/5.0-201806281256 directory ... at list the libraries are found when I do so? I would like to be able to write a bash script that copies the gci library files into the proper directory, but the directory for the Pharo6.1 vm looks like some kind of magic number and I assume that different builds of the 6.1 vm could have different names and possibly even multiple directories under pharo-vm/lib/pharo/? I haven't looked at Pharo7.0 yet to see what it's pharo-vm directory structure looks like... A pointer to where the naming conventions for these directories is described for Pharo6.x, Pharo7.x and Pharo8.x would be greatly appreciated ... would also be nice if the error message for the "module not found" error could be a bit more descriptive as well ... Thanks, Dale [1] https://github.com/GsDevKit/GemStone-GCI

4 6

Slowdown in writing code (to changes?) in 7 vs 6
by stephan Jan. 28, 2019

Jan. 28, 2019

Writing code in this way seems to be about 2.4 times slower in Pharo 7 vs Pharo 6. I also tried with smaller numbers, and there I noticed a rather high number of calls to File>>basicOpenForWrite:. With 4*4*4 methods, 768, and 5*5*5 1502. |organizer aToZ| organizer := RPackageOrganizer default. aToZ := 'ABCDEFGHIJKLMNOPQRSTUVWXYZ'. [ aToZ do: [ :ch | |packageName package| packageName := 'Package', ch asString. package := organizer createPackageNamed: packageName. aToZ do: [ :classCh | |cls| cls := Object subclass: (ch asString, 'Class', classCh asString) asSymbol instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' package: packageName. package addClassDefinition: cls. aToZ do: [ :m | cls compile: m asString asLowercase, String cr, ' ^self' ] ] ] ] timeProfile (221 s vs 93) Do I need all those calls to #basicOpenForWrite? Stephan

1 0

[Pharo 8.0] Build #33: Athens test3, 4 do work.
by ci-pharo-ci-jenkins2＠inria.fr Jan. 28, 2019

Jan. 28, 2019

There is a new Pharo build available! The status of the build #33 was: SUCCESS. The Pull Request #2326 was integrated: "Athens test3, 4 do work." Pull request url: https://github.com/pharo-project/pharo/pull/2326 Issue Url: https://pharo.fogbugz.com/f/cases/2275 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #32: 2342-memory-leak-through-GTSnippets-instance-cache
by ci-pharo-ci-jenkins2＠inria.fr Jan. 28, 2019

Jan. 28, 2019

There is a new Pharo build available! The status of the build #32 was: SUCCESS. The Pull Request #2344 was integrated: "2342-memory-leak-through-GTSnippets-instance-cache" Pull request url: https://github.com/pharo-project/pharo/pull/2344 Issue Url: https://pharo.fogbugz.com/f/cases/2342 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #31: Small cleanups
by ci-pharo-ci-jenkins2＠inria.fr Jan. 28, 2019

Jan. 28, 2019

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

1 0