strange errors in jenkins jobs

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

strange errors in jenkins jobs

Tudor Girba-2
Hi,

Since yesterday, all Moose-related jobs are failing. These are built on top of Pharo 5.0 stable, downloaded like this:
wget --quiet -O - http://get.pharo.org/50+vm | bash

We did not change anything in the projects that fail, and locally on Mac, I can load any of the code without problems. The jobs are running Linux.

So, I am wondering if anything else has changed in Pharo 5.0.

In particular, the error is quite strange. It looks like this:
Error: MessageNotUnderstood: receiver of "finish" is nil
UndefinedObject(Object)>>error:
[ :err :rcvr |
| errCtx errMorph |
errCtx := thisContext.
[ errCtx := errCtx sender.
"Search the sender chain to find the morph causing the problem"
[ errCtx notNil and: [ errCtx receiver isMorph not ] ]
        whileTrue: [ errCtx := errCtx sender ].
"If we're at the root of the context chain then we have a fatal drawing problem"
errCtx ifNil: [ ^ self handleFatalDrawingError: err ].
errMorph := errCtx receiver.
...

See more at: https://ci.inria.fr/moose/job/fame/1266/console

Any idea of what might be wrong?


Cheers,
Doru


--
www.tudorgirba.com
www.feenk.com

"We cannot reach the flow of things unless we let go."




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.list.inf.unibe.ch/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-dev] strange errors in jenkins jobs

Nicolai Hess-3-2


2016-08-07 22:36 GMT+02:00 Tudor Girba <[hidden email]>:
Hi,

Since yesterday, all Moose-related jobs are failing. These are built on top of Pharo 5.0 stable, downloaded like this:
wget --quiet -O - http://get.pharo.org/50+vm | bash

We did not change anything in the projects that fail, and locally on Mac, I can load any of the code without problems. The jobs are running Linux.

So, I am wondering if anything else has changed in Pharo 5.0.

In particular, the error is quite strange. It looks like this:
 [31mError: MessageNotUnderstood: receiver of "finish" is nil
 [0mUndefinedObject(Object)>>error:
[ :err :rcvr |
| errCtx errMorph |
errCtx := thisContext.
[ errCtx := errCtx sender.
"Search the sender chain to find the morph causing the problem"
[ errCtx notNil and: [ errCtx receiver isMorph not ] ]
        whileTrue: [ errCtx := errCtx sender ].
"If we're at the root of the context chain then we have a fatal drawing problem"
errCtx ifNil: [ ^ self handleFatalDrawingError: err ].
errMorph := errCtx receiver.
...

See more at: https://ci.inria.fr/moose/job/fame/1266/console

Any idea of what might be wrong?


Cheers,
Doru


--
www.tudorgirba.com
www.feenk.com

"We cannot reach the flow of things unless we let go."







_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.list.inf.unibe.ch/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-dev] strange errors in jenkins jobs

Tudor Girba-2

> On Aug 7, 2016, at 11:10 PM, Nicolai Hess <[hidden email]> wrote:
>
>
>
> 2016-08-07 22:36 GMT+02:00 Tudor Girba <[hidden email]>:
> Hi,
>
> Since yesterday, all Moose-related jobs are failing. These are built on top of Pharo 5.0 stable, downloaded like this:
> wget --quiet -O - http://get.pharo.org/50+vm | bash
>
> We did not change anything in the projects that fail, and locally on Mac, I can load any of the code without problems. The jobs are running Linux.
>
> So, I am wondering if anything else has changed in Pharo 5.0.
>
> In particular, the error is quite strange. It looks like this:
>  [31mError: MessageNotUnderstood: receiver of "finish" is nil
>  [0mUndefinedObject(Object)>>error:
> [ :err :rcvr |
> | errCtx errMorph |
> errCtx := thisContext.
> [ errCtx := errCtx sender.
> "Search the sender chain to find the morph causing the problem"
> [ errCtx notNil and: [ errCtx receiver isMorph not ] ]
>         whileTrue: [ errCtx := errCtx sender ].
> "If we're at the root of the context chain then we have a fatal drawing problem"
> errCtx ifNil: [ ^ self handleFatalDrawingError: err ].
> errMorph := errCtx receiver.
> ...
>
> I think this is the same reported here:
> http://forum.world.st/newly-introduced-problem-in-Pharo5-0-running-headless-vm-Ubuntu-14-04-tp4908532.html
> 18706 Build of Pharo5 is broken
>

Hmm, indeed it looks quite the same, but in our case, the problem appeared only today while the report of Dale is older. Yesterday, our jobs worked well. What could be at play to explain that?

Doru


>
> See more at: https://ci.inria.fr/moose/job/fame/1266/console
>
> Any idea of what might be wrong?
>
>
> Cheers,
> Doru
>
>
> --
> www.tudorgirba.com
> www.feenk.com
>
> "We cannot reach the flow of things unless we let go."
>
>
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.list.inf.unibe.ch/listinfo/moose-dev

--
www.tudorgirba.com
www.feenk.com

"Value is always contextual."




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.list.inf.unibe.ch/listinfo/moose-dev