no cheating :) 
AsmJit-Tests are uncovering some weird behaviour that has to be fixed� but we cannot stop the stream in the mean time. 

but yes� it has to be fixed soon :)

Esteban

On 06 Jan 2014, at 13:46, Nicolai Hess <nicolaihess@web.de> wrote:

That's cheating :)



2014/1/6 Esteban Lorenzano <estebanlm@gmail.com>
green again� cool :)

On 06 Jan 2014, at 10:54, GitHub <noreply@github.com> wrote:

>  Branch: refs/heads/3.0
>  Home:   https://github.com/pharo-project/pharo-core
>  Commit: 0327dcd90fc34d638a6286e0b14d64ecfa85a438
>      https://github.com/pharo-project/pharo-core/commit/0327dcd90fc34d638a6286e0b14d64ecfa85a438
>  Author: Jenkins Build Server <board@pharo-project.org>
>  Date:   2014-01-06 (Mon, 06 Jan 2014)
>
>  Changed paths:
>    A Komitter.package/extension/MCFileTreeRepository/instance/isRemote.st
>    A Komitter.package/extension/MCFileTreeRepository/instance/koRemote.st
>    A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script326.st
>    A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30673.st
>    M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st
>
>  Log Message:
>  -----------
>  30673
> removeMe
>
> http://files.pharo.org/image/30/30673.zip
>
>