- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60010 Home: https://github.com/pharo-project/pharo-core

May 17, 2016

[pharo-project/pharo-core] 96698c: 60010

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 96698cbeb27393860effe85738f937fb4dd96338 https://github.com/pharo-project/pharo-core/commit/96698cbeb27393860effe857… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-17 (Tue, 17 May 2016) Changed paths: M Collections-Strings.package/String.class/instance/converting/repeat_.st M Collections-Tests.package/StringTest.class/instance/testing - converting/testRepeat.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60009.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60010.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60009.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60010.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60010 18229 Allow String>>#repeat: to repeat a string 0 times https://pharo.fogbugz.com/f/cases/18229 http://files.pharo.org/image/60/60010.zip

May 17, 2016

about spurious conflicts

by stepharo

Hi while migrating some of the issues from 50 to 60, I noticed that many of the conflicts are not conflicts since the code of both methods and the protocols are the same. Does anybody experienced the same? Here are some examples and I'm puzzled. https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/417//artifact/valid… https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator/418//artifact/valid… Stef

May 17, 2016

Re: [Pharo-dev] UnifiedFFI Interrupted system call error on OSX

by stepharo

Le 17/5/16 Ã 21:33, Jan van de Sandt a Ã©crit : > Hi, > > I'm helping with the port of LibGit [1] from Pharo 4 to Pharo 5 [2]. BIG THANKS!!!! > This project provides Smalltalk bindings for the libgit2 library. Very > useful for better Git support in Pharo. The port means using the new > UnifiedFFI instead of NativeBoost. > > The project is still in the alpha stage but a lot of the libgit2 > features are already accessible. Some libgit2 calls access the > network. For example to clone a repository or to push a commit. The > calls that use https work on Linux and on Windows but on OSX we always > get the following error in Pharo 5: > > LGit_GIT_ERROR: Failed to connect to github.com <http://github.com>: > Interrupted system call. > > In Pharo4/NB this error does not occur. Could this be an issue in UFFI > or perhaps in the VM ? > > To reproduce the problem in Pharo 5 (after loading [2]): > > > | repo | > repo := LGitRepository on: 'my-test-repo' asFileReference. > repo cloneHttps: 'https://github.com/theseion/LibGit.git' > > > Jan. > > [1] https://github.com/theseion/LibGit > [2] https://github.com/jvdsandt/LibGit

May 17, 2016

Re: [Pharo-dev] more robust tests

by stepharo

thanks. I would like to have the system in a state where we can release the next day :) Le 17/5/16 Ã 21:43, Andrei Chis a Ã©crit : > We'll have a look. > > Cheers, > Andrei > > On Sun, May 15, 2016 at 3:06 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Hi > > While integrating some changes in P6.0 I got such tests failing. > Only failing on mac. > > Could you check? > > Stef > > > Regression > > GT.EventRecorder.Tests.Core.GTEventRecorderTest.testAddCollector3 > (from GT-EventRecorder-Tests) > > Failing for the past 1 build (Since Unstable#7 ) > Took 0.96 sec. > add description > Error Message > > Assertion failed > Stacktrace > > GTEventRecorderTest(TestAsserter)>>assert: > GTEventRecorderTest(TestAsserter)>>deny: > GTEventRecorderTest>>assertReceiverSemaphore > GTEventRecorderTest>>waitForDelivery > GTEventRecorderTest>>testAddCollector3 > GTEventRecorderTest(TestCase)>>performTest > > > Stef > > >

May 17, 2016

Re: [Pharo-dev] more robust tests

by Andrei Chis

We'll have a look. Cheers, Andrei On Sun, May 15, 2016 at 3:06 PM, stepharo <stepharo(a)free.fr> wrote: > Hi > > While integrating some changes in P6.0 I got such tests failing. Only > failing on mac. > > Could you check? > > Stef > > > Regression > > GT.EventRecorder.Tests.Core.GTEventRecorderTest.testAddCollector3 (from > GT-EventRecorder-Tests) > > Failing for the past 1 build (Since Unstable#7 ) > Took 0.96 sec. > add description > Error Message > > Assertion failed > Stacktrace > > GTEventRecorderTest(TestAsserter)>>assert: > GTEventRecorderTest(TestAsserter)>>deny: > GTEventRecorderTest>>assertReceiverSemaphore > GTEventRecorderTest>>waitForDelivery > GTEventRecorderTest>>testAddCollector3 > GTEventRecorderTest(TestCase)>>performTest > > > Stef > > >

May 17, 2016

UnifiedFFI Interrupted system call error on OSX

by Jan van de Sandt

Hi, I'm helping with the port of LibGit [1] from Pharo 4 to Pharo 5 [2]. This project provides Smalltalk bindings for the libgit2 library. Very useful for better Git support in Pharo. The port means using the new UnifiedFFI instead of NativeBoost. The project is still in the alpha stage but a lot of the libgit2 features are already accessible. Some libgit2 calls access the network. For example to clone a repository or to push a commit. The calls that use https work on Linux and on Windows but on OSX we always get the following error in Pharo 5: LGit_GIT_ERROR: Failed to connect to github.com: Interrupted system call. In Pharo4/NB this error does not occur. Could this be an issue in UFFI or perhaps in the VM ? To reproduce the problem in Pharo 5 (after loading [2]): | repo | repo := LGitRepository on: 'my-test-repo' asFileReference. repo cloneHttps: 'https://github.com/theseion/LibGit.git' Jan. [1] https://github.com/theseion/LibGit [2] https://github.com/jvdsandt/LibGit

May 17, 2016

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

by Alistair Grant

On Tue, May 17, 2016 at 06:16:07PM +0200, Esteban Lorenzano wrote: > there was a problem with the repositorio (I forget to make it public). > now you should be able to commit (of course, you still need an smalltalkhub user :P) > > Esteban Thanks! I've successfully uploaded the slice now. There are two versions, the first when Max uploaded it as part of looking in to the problem, and the second the one I just uploaded. They should be the same, of course. :-) Cheers, Alistair > > > On 17 May 2016, at 17:54, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > > On Tue, May 17, 2016 at 09:11:07AM +0200, Max Leske wrote: > >> On 17 May 2016, at 09:09, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> On 17 May 2016, at 06:48, Max Leske <maxleske(a)gmail.com> wrote: > >> No, itâs publicly writeable. You may have found a bug. Can you link to > >> the .mcz youâre trying to upload? Then we can give it a try. > >> > >> > >> Don't you have to be part of team Pharo ? > >> > >> > >> Hmâ¦ then âpublicâ is certainly a misleading label... > > > > Who should I contact to be added to the team? > > > > Thanks, > > Alistair > > > > > >

May 17, 2016

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

by Esteban Lorenzano

there was a problem with the repositorio (I forget to make it public). now you should be able to commit (of course, you still need an smalltalkhub user :P) Esteban > On 17 May 2016, at 17:54, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > On Tue, May 17, 2016 at 09:11:07AM +0200, Max Leske wrote: >> On 17 May 2016, at 09:09, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> On 17 May 2016, at 06:48, Max Leske <maxleske(a)gmail.com> wrote: >> No, itâs publicly writeable. You may have found a bug. Can you link to >> the .mcz youâre trying to upload? Then we can give it a try. >> >> >> Don't you have to be part of team Pharo ? >> >> >> Hmâ¦ then âpublicâ is certainly a misleading label... > > Who should I contact to be added to the team? > > Thanks, > Alistair > >

May 17, 2016

Re: [Pharo-dev] Internal Server error attempting to upload SLICE

by Alistair Grant

On Tue, May 17, 2016 at 09:11:07AM +0200, Max Leske wrote: > On 17 May 2016, at 09:09, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > On 17 May 2016, at 06:48, Max Leske <maxleske(a)gmail.com> wrote: > No, itâs publicly writeable. You may have found a bug. Can you link to > the .mcz youâre trying to upload? Then we can give it a try. > > > Don't you have to be part of team Pharo ? > > > Hmâ¦ then âpublicâ is certainly a misleading label... Who should I contact to be added to the team? Thanks, Alistair

May 17, 2016