On Wed, Oct 3, 2018 at 7:31 PM Juraj Kubelka via Pharo-dev <
pharo-dev@lists.pharo.org> wrote:
> Hi!
>
> I did the same measurement for Pharo 6.1. To summarize it I have those
> results:
>
> By executing:
>
> -=-=-=-
> EpMonitor current disable.
> [ Metacello new
> baseline: 'GToolkit';
>
On Tue, 2018-10-02 at 23:31 -0300, Juraj Kubelka via Pharo-dev wrote:
>
I can profile it to see if there is something wrong, or it's just that
a lot of source code from GT and dependencies is written to disk and
then the only thing can do is disable change recording (and maybe then
re-enabling
--- Begin Message ---
Hi!
I did the same measurement for Pharo 6.1. To summarize it I have those results:
By executing:
-=-=-=-
EpMonitor current disable.
[ Metacello new
baseline: 'GToolkit';
repository: 'github://feenkcom/gtoolkit/src';
load.
] timeToRun
-=-=-=-
Pharo 6.1 64bit
> On 3 Oct 2018, at 15:04, Esteban Lorenzano wrote:
>
>
>> On 3 Oct 2018, at 14:26, Sven Van Caekenberghe wrote:
>>
>> Metacello new
>> repository: 'github://svenvc/ztimestamp';
>> baseline: 'ZTimestamp';
>> load.
>
> This part is bad.
> You need:
>
> Metacello new
> repository:
> On 3 Oct 2018, at 14:26, Sven Van Caekenberghe wrote:
>
> Metacello new
> repository: 'github://svenvc/ztimestamp ';
> baseline: 'ZTimestamp';
> load.
This part is bad.
You need:
Metacello new
repository: 'github://svenvc/ztimestamp/repository';
baseline: 'ZTimestamp';
load.
(You
There is a new Pharo build available!
The status of the build #1294 was: FAILURE.
The Pull Request #1855 was integrated: "22515 Package
ManifestGraphicsDisplayObjects and related classes in Graphics-Display Objects"
Pull request url: https://github.com/pharo-project/pharo/pull/1855
Issue
Well, I tried but no luck:
Metacello new
baseline: 'Metacello';
repository: 'github://metacello/metacello:pharo-6.1_dev/repository';
onConflict: [ :ex | ex useIncoming ];
load.
Metacello new
repository: 'github://pharo-vcs/tonel';
baseline: 'Tonel';
load.
Metacello new
There is a new Pharo build available!
The status of the build #1293 was: SUCCESS.
The Pull Request #1848 was integrated:
"22163-Memory-Leak-GLMHintableActionButtonBrick"
Pull request url: https://github.com/pharo-project/pharo/pull/1848
Issue Url: https://pharo.fogbugz.com/f/cases/22163
> On 3 Oct 2018, at 14:12, Norbert Hartl wrote:
>
>
>
>> Am 03.10.2018 um 14:02 schrieb Sven Van Caekenberghe :
>>
>> So I am trying to load GitHub/Tonel/BaselineOf code in Pharo 6.0.
>>
>> I got a fresh 6.0 and I installed Tonel into it using
>>
>> Metacello new
>> repository:
Hi Sven,
You still need latest metacello.
This is the list of requirements to use metacello and tonel.
1. Latest metacello:
Metacello new
baseline: 'Metacello';
repository: 'github://metacello/metacello:pharo-6.1_dev/repository';
onConflict: [ :ex | ex useIncoming ];
load.
> Am 03.10.2018 um 14:02 schrieb Sven Van Caekenberghe :
>
> So I am trying to load GitHub/Tonel/BaselineOf code in Pharo 6.0.
>
> I got a fresh 6.0 and I installed Tonel into it using
>
> Metacello new
> repository: 'github://pharo-vcs/tonel';
> baseline: 'Tonel';
> load.
>
> Which
So I am trying to load GitHub/Tonel/BaselineOf code in Pharo 6.0.
I got a fresh 6.0 and I installed Tonel into it using
Metacello new
repository: 'github://pharo-vcs/tonel';
baseline: 'Tonel';
load.
Which went OK
Fetched -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master
There is a new Pharo build available!
The status of the build #1292 was: FAILURE.
The Pull Request #1852 was integrated:
"22094-Scrollbars-need-to-take-displayScaleFactor-into-account"
Pull request url: https://github.com/pharo-project/pharo/pull/1852
Issue Url:
There is a new Pharo build available!
The status of the build #1291 was: SUCCESS.
The Pull Request #1853 was integrated:
"22513-Update-ProfStef-and-fix-spelling-mistakes"
Pull request url: https://github.com/pharo-project/pharo/pull/1853
Issue Url:
Yes +1 on the thanks!
Also it's great to read your emails to learn new stuff :)
On Tue, Oct 2, 2018 at 8:30 PM Stephane Ducasse
wrote:
> Ben I would like to thank you!
> Simply.
>
> Stef
> On Tue, Oct 2, 2018 at 5:58 AM Ben Coman wrote:
> >
> > On Fri, 13 Apr 2018 at 13:56, Benoit St-Jean via
Ok, so the upgrade of the server contract did not help.
There is a CDN included, I will try to enable that next (but CDNs cache by
name, so we need to make sure we invalidate the cache…)
I will do a calculation what S3 would cost, too.
Marcus
> On 3 Oct 2018, at 00:59, Esteban
There is a new Pharo build available!
The status of the build #1290 was: SUCCESS.
The Pull Request #1851 was integrated:
"22511-TestValueWithinFix-is-failing-randomly"
Pull request url: https://github.com/pharo-project/pharo/pull/1851
Issue Url: https://pharo.fogbugz.com/f/cases/22511
Build
It would also prefer an SS3-based STHub, at least as an alternative to GitHub.
___
montyos.wordpress.com
> Sent: Saturday, September 29, 2018 at 6:43 AM
> From: "Stephane Ducasse"
> To: "Pharo Development List"
> Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/
>
>
18 matches
Mail list logo
