Re: [Pharo-dev] keyboard events in the windows VM

2015-11-12 Thread Nicolai Hess
2015-11-12 16:43 GMT+01:00 EuanM : > I'm happy to test on Windows 7, and on Raspbian Linux > > (Although Raspbian Linux runs Pharo UI events slo-o-owly, so I am not > the best person to do the Linux testing) > Thank you EuanM, I 'll provide a vm with these changes. All changes are only for the wi

Re: [Pharo-dev] Using a newer vm with PharoLauncher, platform differences

2015-11-12 Thread Dimitris Chloupis
nice , I did not know that. Where is that setting located ? On Fri, Nov 13, 2015 at 3:09 AM Stephan Eggermont wrote: > On 12/11/15 23:46, Dimitris Chloupis wrote: > > I could be wrong but since pharolauncher on macos is a mac app then you > > will need to change the vm inside the pharo.app folde

Re: [Pharo-dev] Using a newer vm with PharoLauncher, platform differences

2015-11-12 Thread Stephan Eggermont
On 12/11/15 23:46, Dimitris Chloupis wrote: I could be wrong but since pharolauncher on macos is a mac app then you will need to change the vm inside the pharo.app folder, in pharo.app/Contents/MacOS PharoLauncher has a setting to use a different vm to start its images than the one it uses itse

Re: [Pharo-dev] Using a newer vm with PharoLauncher, platform differences

2015-11-12 Thread Dimitris Chloupis
I could be wrong but since pharolauncher on macos is a mac app then you will need to change the vm inside the pharo.app folder, in pharo.app/Contents/MacOS On Thu, Nov 12, 2015 at 5:13 PM Stephan Eggermont wrote: > I wanted to use a newer vm with PharoLauncher, > so I added a vms directory in >

Re: [Pharo-dev] Never ending BlockClosure>>benchFor:

2015-11-12 Thread Tudor Girba
+1 Doru > On Nov 12, 2015, at 10:21 PM, stepharo wrote: > > thanks max this is great to have your support. > > Le 12/11/15 21:21, Max Leske a écrit : >> I found a single test method I could use to narrow down the problem (be >> aware that this might not work for you. I have other (fresh) im

Re: [Pharo-dev] Never ending BlockClosure>>benchFor:

2015-11-12 Thread stepharo
thanks max this is great to have your support. Le 12/11/15 21:21, Max Leske a écrit : I found a single test method I could use to narrow down the problem (be aware that this might not work for you. I have other (fresh) images where the issue never occurs). The method I used is EpRedoAndUndoVis

[Pharo-dev] [pharo-project/pharo-core] 26e6b3: 50440

2015-11-12 Thread GitHub
Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 26e6b3ab5ea102c92db043ea8a4f10b6557c30bd https://github.com/pharo-project/pharo-core/commit/26e6b3ab5ea102c92db043ea8a4f10b6557c30bd Author: Jenkins Build Server Date: 2015-11-12 (Thu, 12 Nov 2015

[Pharo-dev] [pharo-project/pharo-core]

2015-11-12 Thread GitHub
Branch: refs/tags/50440 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] Never ending BlockClosure>>benchFor:

2015-11-12 Thread Max Leske
I found a single test method I could use to narrow down the problem (be aware that this might not work for you. I have other (fresh) images where the issue never occurs). The method I used is EpRedoAndUndoVisitorTest>>testClassModification. I was able to mitigate the hang by making a small modi

Re: [Pharo-dev] Never ending BlockClosure>>benchFor:

2015-11-12 Thread Martin Dias
Yes! with Max Leske we have been isolating the problem and we realized that a fresh image was enough: 1) curl get.pharo.org/50+vm | bash 2) ./pharo Pharo.image eval "CommandLineTestRunner runClasses: {GLMTreeMorphicTest. GLMWatcherMorphicTest. GLMPagerMorphTest} named: 'x'. CommandLineTestRunner

Re: [Pharo-dev] Never ending BlockClosure>>benchFor:

2015-11-12 Thread Sven Van Caekenberghe
Then it must be that waiting on the delay never ends, which is probably a problem all by itself. > On 12 Nov 2015, at 18:39, Marcus Denker wrote: > > The fun thing is that I now get the same problem when integrating the GT > Tools update. > > After doing the update for issue 16957, the test r

Re: [Pharo-dev] Never ending BlockClosure>>benchFor:

2015-11-12 Thread Marcus Denker
The fun thing is that I now get the same problem when integrating the GT Tools update. After doing the update for issue 16957, the test run hangs with starting testcase: BlockClosureTest>>testBenchFor ... > On 11 Nov 2015, at 22:42, Martin Dias wrote: > > Hello, > > I'm trying to understan

Re: [Pharo-dev] keyboard events in the windows VM

2015-11-12 Thread EuanM
I'm happy to test on Windows 7, and on Raspbian Linux (Although Raspbian Linux runs Pharo UI events slo-o-owly, so I am not the best person to do the Linux testing) On 12 November 2015 at 15:42, EuanM wrote: > I think anything that makes a consistent UI to Pharo for users on > different platform

Re: [Pharo-dev] keyboard events in the windows VM

2015-11-12 Thread EuanM
I think anything that makes a consistent UI to Pharo for users on different platforms is a good thing. However, I do not know what the downside-effects of this change are. The key thing is to capture all breaks caused by the changed, so they can be coded through or around. And ensure that the te

[Pharo-dev] Using a newer vm with PharoLauncher, platform differences

2015-11-12 Thread Stephan Eggermont
I wanted to use a newer vm with PharoLauncher, so I added a vms directory in /Users/stephan/Library/Application Support/Pharo/ and used curl get.pharo.org/vmLatest50 | bash to install it there. In PharoLauncher I then set the vm full path to either /Users/stephan/Library/Application Support/Pharo

[Pharo-dev] [pharo-project/pharo-core] 56b5ef: 50439

2015-11-12 Thread GitHub
Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 56b5ef44e07c2b445b71e979444fe8b2da4dc3b8 https://github.com/pharo-project/pharo-core/commit/56b5ef44e07c2b445b71e979444fe8b2da4dc3b8 Author: Jenkins Build Server Date: 2015-11-12 (Thu, 12 Nov 2015

[Pharo-dev] [pharo-project/pharo-core]

2015-11-12 Thread GitHub
Branch: refs/tags/50439 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] [Pharo-project] [Vm-dev] Cog issue? Re: StandardFileStream size limit?

2015-11-12 Thread Nicolai Hess
2015-11-12 14:10 GMT+01:00 Dimitris Chloupis : > latest vm has issues with OSProcess stdout the last time I checked on > Yosemite. I would not call it stable unless we talk only crashes here. > Ah, I didn't know this was a vm issue. Does this means it is working with the "official" stable vm ?

Re: [Pharo-dev] [Pharo-project] [Vm-dev] Cog issue? Re: StandardFileStream size limit?

2015-11-12 Thread Dimitris Chloupis
latest vm has issues with OSProcess stdout the last time I checked on Yosemite. I would not call it stable unless we talk only crashes here. On Thu, Nov 12, 2015 at 2:55 PM Nicolai Hess wrote: > 2015-11-12 6:14 GMT+01:00 Jimmie Houchin : > >> This still fails three and a half years later with a

Re: [Pharo-dev] [Pharo-project] [Vm-dev] Cog issue? Re: StandardFileStream size limit?

2015-11-12 Thread Nicolai Hess
2015-11-12 6:14 GMT+01:00 Jimmie Houchin : > This still fails three and a half years later with a default Pharo 4 vm > and image. > :( > > I spent a few hours trying to diagnose why Pharo was telling me that I > file I knew existed didn't exist. Very frustrating trying to debug this and > then to

Re: [Pharo-dev] Smalltalkhub returning 500 response for a public repository

2015-11-12 Thread Denis Kudriashov
Same for me now. I try commit to CAR/Ghost repository 2015-11-11 20:30 GMT+01:00 Euan Mee : > I've been trying unsuccessfully to write to the > SandstoneDb public repository at smalltalkhub.com > > http://smalltalkhub.com/#!/~gnaritas/SandstoneDb > shows the green tickmark and PUBLIC > > Writing

Re: [Pharo-dev] Does anybody know if Sport is available in Pharo?

2015-11-12 Thread Christophe Demarey
Le 12 nov. 2015 à 10:15, Frank Shearar a écrit : > On 12 November 2015 at 09:04, Christophe Demarey > wrote: >> >> Le 10 nov. 2015 à 21:39, Sven Van Caekenberghe a écrit : >> >>> << Sport is a Smalltalk portability layer. Sport presents a consistent >>> interface and implemented in a number o

Re: [Pharo-dev] Never ending BlockClosure>>benchFor:

2015-11-12 Thread Sven Van Caekenberghe
> On 12 Nov 2015, at 10:49, Sven Van Caekenberghe wrote: > > But how could Epicea have an impact on that part ? > > That is the question. > > Unless someone objects, I would not say that this should hold integration. > There will be much more work to do after integration when people start usi

Re: [Pharo-dev] Never ending BlockClosure>>benchFor:

2015-11-12 Thread Sven Van Caekenberghe
But how could Epicea have an impact on that part ? That is the question. Unless someone objects, I would not say that this should hold integration. There will be much more work to do after integration when people start using it ;-) > On 12 Nov 2015, at 10:40, Martin Dias wrote: > > Hi Sven,

Re: [Pharo-dev] Never ending BlockClosure>>benchFor:

2015-11-12 Thread Martin Dias
Hi Sven, El 12/11/2015 9:32, "Sven Van Caekenberghe" escribió: > Hi Martin, > > Here is the relevant issue for the last change in that method: > > > https://pharo.fogbugz.com/f/cases/14989/Improve-and-simplify-BlockClosure-benchmarking > > IIRC the timing change was done in Squeak too, not the Be

Re: [Pharo-dev] Does anybody know if Sport is available in Pharo?

2015-11-12 Thread Frank Shearar
On 12 November 2015 at 09:04, Christophe Demarey wrote: > > Le 10 nov. 2015 à 21:39, Sven Van Caekenberghe a écrit : > >> << Sport is a Smalltalk portability layer. Sport presents a consistent >> interface and implemented in a number of Smalltalk dialects. Smalltalk code >> written to the Sport

Re: [Pharo-dev] Does anybody know if Sport is available in Pharo?

2015-11-12 Thread Christophe Demarey
Le 10 nov. 2015 à 21:39, Sven Van Caekenberghe a écrit : > << Sport is a Smalltalk portability layer. Sport presents a consistent > interface and implemented in a number of Smalltalk dialects. Smalltalk code > written to the Sport interfaces can be run in any Smalltalk dialect without > altera

[Pharo-dev] [pharo-project/pharo-core]

2015-11-12 Thread GitHub
Branch: refs/tags/50438 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 224f0e: 50438

2015-11-12 Thread GitHub
Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 224f0e85618e9da1e6680661ef22490bfc47a786 https://github.com/pharo-project/pharo-core/commit/224f0e85618e9da1e6680661ef22490bfc47a786 Author: Jenkins Build Server Date: 2015-11-12 (Thu, 12 Nov 2015

Re: [Pharo-dev] Ubuntu fullscreen problems

2015-11-12 Thread Nicolai Hess
2015-11-09 21:41 GMT+01:00 J.F. Rick : > Works like a charm: both toggling modes and using the Unity pager to > switch workspaces. > Thank you for testing. Dave Lewis added another change to enable the old fullscreen method by a command line option. (some (older) windowmanager may not support th

Re: [Pharo-dev] Never ending BlockClosure>>benchFor:

2015-11-12 Thread Sven Van Caekenberghe
Hi Martin, Here is the relevant issue for the last change in that method: https://pharo.fogbugz.com/f/cases/14989/Improve-and-simplify-BlockClosure-benchmarking IIRC the timing change was done in Squeak too, not the BenchmarkResult object. Maybe the old code is more reliable, thing is, the CI m

[Pharo-dev] [pharo-project/pharo-core]

2015-11-12 Thread GitHub
Branch: refs/tags/50437 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 08dc03: 50437

2015-11-12 Thread GitHub
Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 08dc031662f61ded7ffdacbcd9d47c2204221b86 https://github.com/pharo-project/pharo-core/commit/08dc031662f61ded7ffdacbcd9d47c2204221b86 Author: Jenkins Build Server Date: 2015-11-12 (Thu, 12 Nov 2015