Re: [Pharo-dev] Still build errors :(

2019-01-28 Thread Esteban Lorenzano
This is building against the older version. Relaunching the tests is not enough here, you need to close and open again the PR (Which I just did). Esteban > On 28 Jan 2019, at 22:26, ducasse wrote: > > > HI guys > > we still have some issues…. I relaunched some jobs but I get regularly >

[Pharo-dev] [Pharo 8.0] Build #36: 22033-Use-FuzzyMatcher-in-spotter-search

2019-01-28 Thread ci-pharo-ci-jenkins2
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:

[Pharo-dev] [Pharo 8.0] Build #35: 2321-The-dark-age-is-coming

2019-01-28 Thread ci-pharo-ci-jenkins2
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:

[Pharo-dev] Still build errors :(

2019-01-28 Thread ducasse
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- 2330/32/src — cache

[Pharo-dev] [Pharo 8.0] Build #34: 2356-Remove-GT-Spotter-EventRecorder

2019-01-28 Thread ci-pharo-ci-jenkins2
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:

Re: [Pharo-dev] Build problems

2019-01-28 Thread ducasse
Thanks alistair. Yes I saw and I’m going over pr to flush the pipe. Stef > On 28 Jan 2019, at 19:33, Alistair Grant wrote: > > Hi Stef, > > The "unbound variable" error has been fixed in > https://github.com/pharo-project/pharo/pull/2368 (at least no one has > complained in the last 8 hours

Re: [Pharo-dev] naming convention for pharo-vm/lib/pharo/* directory?

2019-01-28 Thread Alistair Grant
Hi Dale, On Fri, 25 Jan 2019 at 22:10, Dale Henrichs wrote: > > Thanks, Nicolas (and Sven), > > VM search path is what I am looking for (UFFI external modules) and I am > curious whether or not this path `pharo-vm/lib/pharo/5.0-201806281256` is > constant or variable for the various Pharo

Re: [Pharo-dev] Build problems

2019-01-28 Thread Alistair Grant
Hi Stef, The "unbound variable" error has been fixed in https://github.com/pharo-project/pharo/pull/2368 (at least no one has complained in the last 8 hours :-)). Cheers, Alistair On Sun, 27 Jan 2019 at 20:35, ducasse wrote: > > Hi > > There are several problems with the build: > > First > > >

[Pharo-dev] Slowdown in writing code (to changes?) in 7 vs 6

2019-01-28 Thread stephan
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

[Pharo-dev] [Pharo 8.0] Build #33: Athens test3, 4 do work.

2019-01-28 Thread ci-pharo-ci-jenkins2
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:

[Pharo-dev] [Pharo 8.0] Build #32: 2342-memory-leak-through-GTSnippets-instance-cache

2019-01-28 Thread ci-pharo-ci-jenkins2
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

[Pharo-dev] [Pharo 8.0] Build #31: Small cleanups

2019-01-28 Thread ci-pharo-ci-jenkins2
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:

[Pharo-dev] [Pharo 8.0] Build #30: transform_32_into_64.sh: call envvars.sh

2019-01-28 Thread ci-pharo-ci-jenkins2
There is a new Pharo build available! The status of the build #30 was: SUCCESS. The Pull Request #2368 was integrated: "transform_32_into_64.sh: call envvars.sh" Pull request url: https://github.com/pharo-project/pharo/pull/2368 Issue Url: https://pharo.fogbugz.com/f/cases/transform32into64

[Pharo-dev] [Pharo 8.0] Build #29: FAILURE

2019-01-28 Thread ci-pharo-ci-jenkins2
There is a new Pharo build available! The status of the build #29 was: FAILURE. Could not extract further issue information from commit message: ping ci Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo8.0/29/

[Pharo-dev] [Pharo 8.0] Build #28: FAILURE

2019-01-28 Thread ci-pharo-ci-jenkins2
There is a new Pharo build available! The status of the build #28 was: FAILURE. Could not extract further issue information from commit message: update links to Pharo 8.0 Build Url: