Thanks for the answers!
On Tue, Sep 13, 2016 at 2:46 PM, Marcus Denker
wrote:
>
> > On 13 Sep 2016, at 18:54, Vitor Medina Cruz
> wrote:
> >
> > I understand. I thought it did more stuff, like remove necessary
> development tools or executing
> On 13 Sep 2016, at 18:54, Vitor Medina Cruz wrote:
>
> I understand. I thought it did more stuff, like remove necessary development
> tools or executing processes,
It does call #cleanUpForRelease, but this we call at *every* update on the CI,
too. This calls the
I understand. I thought it did more stuff, like remove necessary
development tools or executing processes, I don't know, but considering its
implementation it should affect only the image size, right?
Thanks,
Vitor
On Tue, Sep 13, 2016 at 8:30 AM, Marcus Denker
wrote:
>
> On 13 Sep 2016, at 13:15, Vitor Medina Cruz wrote:
>
> Humm, why not? When I load the configuration it loads several other packages,
> wouldn't that need a cleanup too? When I first see that I could cleanup an
> image my first thought was to put it in a production
Humm, why not? When I load the configuration it loads several other
packages, wouldn't that need a cleanup too? When I first see that I could
cleanup an image my first thought was to put it in a production state with
my code, then I would cleanup to leave it as lean as possible. Isn't that
Hi,
I think it is not really realistic to expect this to work *after* loading code
of others.
Why not
-> do image clean
-> *then* load the packages you need?
Marcus
> On 13 Sep 2016, at 03:19, Vitor Medina Cruz wrote:
>
> Ok, I did some extra
Ok, I did some extra tests and I think I figured what is happening: the
code I load on the image subject to clean has a startUp method that starts
a Teapot server on port 8080. I tried various scenarios:
1- Load a fresh image from get.pharo.org and execute clean --> Ok
2- Load a fresh image from
Ok may be this is just an endless loop :)
Le 12/9/16 à 10:22, Marcus Denker a écrit :
Hello,
Yes, this is a bug that we really need to fix.
(sadly no information to add other thant that).
On 09 Sep 2016, at 15:16, Vitor Medina Cruz >
Hello,
Yes, this is a bug that we really need to fix.
(sadly no information to add other thant that).
> On 09 Sep 2016, at 15:16, Vitor Medina Cruz wrote:
>
> Hello,
>
> Isn't cleanup the headless image working right now? I know it has some
> problems, but I tried to:
>
Hello, when I remember correctly when I tested cleaning last time, the problem
was in the method ImageCleaner>>cleanUpForRelease (called form
cleanUpForProduction).
Try to comment "self cleanUpMethods." in ImageCleaner>>cleanUpForRelease -
"cleanUpMethods" method never finish.
Have you tried
Hello,
Isn't cleanup the headless image working right now? I know it has some
problems, but I tried to:
curl get.pharo.org | bash
./pharo Pharo.image clean --production
It runs for hours and don't complete. Last time I leave it for about 5
hours before I cancelled.
Regards,
Vitor
11 matches
Mail list logo