Smalltalk › Pharo › Pharo Smalltalk Developers

DefaultCommandLineHandler error

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Sean P. DeNigris

DefaultCommandLineHandler error

Administrator

I don't know if this is a bug (seems like it) or an artifact of Jenkins' build process, but...

If you download https://ci.lille.inria.fr/pharo/view/Pharo%202.0/job/Pharo-2.0/151/artifact/Pharo-2.0.zip , when you launch the image, there is "PostMortem: PrimitiveFailed: primitive #primClose: in MultiByteFileStream failed" signaled from the DefaultCommandLineHandler. It seems maybe the argument list has not been reset? It's still trying to evaluate /builds/jenkins/workspace/Pharo-2.0/Pharo-2.0/Pharo-2.0.st

Sean

Cheers,
Sean

Camillo Bruni-3

Re: DefaultCommandLineHandler error

grml that's some stupid bug I accidentally produced by rewriting the command line handler.
it seems like it does not properly finish execution and drags along some old code...

that's why the image starts up considerably slower the first time :P
see http://code.google.com/p/pharo/issues/detail?id=5907

On 2012-06-14, at 19:58, Sean P. DeNigris wrote:

> I don't know if this is a bug (seems like it) or an artifact of Jenkins'
> build process, but...
>
> If you download
> https://ci.lille.inria.fr/pharo/view/Pharo%202.0/job/Pharo-2.0/151/artifact/Pharo-2.0.zip
> , when you launch the image, there is "PostMortem: PrimitiveFailed:
> primitive #primClose: in MultiByteFileStream failed" signaled from the
> DefaultCommandLineHandler. It seems maybe the argument list has not been
> reset? It's still trying to evaluate
> /builds/jenkins/workspace/Pharo-2.0/Pharo-2.0/Pharo-2.0.st
>
> Sean
>
> --
> View this message in context: http://forum.world.st/DefaultCommandLineHandler-error-tp4634837.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>

Sean P. DeNigris

Re: DefaultCommandLineHandler error

Administrator

Camillo Bruni-3 wrote

that's why the image starts up considerably slower the first time :P

Okay, I updated the issue with that info...

Cheers,
Sean