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 get.pharo.org only with the dependencies from my project (ConfigurationOfTwitterChallenge), one at a time, and execute clean --> Ok 3- Load a fresh image from get.pharo.org, apply ConfigurationOfTwitterChallenge and execute clean --> Fail 4- Load a fresh image from get.pharo.org, apply ConfigurationOfTwitterChallenge and execute eval "TwitterChallengeMain stopDefaultExecution. ImageCleaner cleanUpForProduction. Smalltalk snapshot: true andQuit: true." --> *Ok *(Assuming ImageCleaner cleanUpForProduction. Smalltalk snapshot: true andQuit: true. does the same as clean --production) It appears I cannot clean an Image with the server started. Question: is that an error or I really should not try to clean an image with a server on? If the former I open an issue on FogBuz and I will try on a not-headless vm to see if some error happen. Regards, Vitor On Mon, Sep 12, 2016 at 6:59 AM, stepharo <steph...@free.fr> wrote: > 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 <vitormc...@gmail.com> wrote: > > 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 > > > >
