Hi, I seems that I solved the bug in Moose, the Moose 6.0 job is now yellow with 4 tests failing. Actually, in some methods the é was corrupted in √© and Pharo was not able to load them. I don’t know was happened in the 50257 Pharo version, but now it is working! Cheers, Vincent *De :* Vincent BLONDEAU [mailto:vincent.blondeau@polytech-lille.net] *Envoyé :* mardi 25 août 2015 23:26 *À :* 'Moose-related development' *Objet :* RE: [Moose-dev] help with debugging the red build Work in progress! See https://pharo.fogbugz.com/f/cases/16359/ZnInvalidUTF8-is-not-an-valid-excep… and https://pharo.fogbugz.com/f/cases/16360/Case-16283-integration-makes-Moose-…. More help can be helpful, especially for the second case. Cheers, Vincent *De :* moose-dev-bounces(a)iam.unibe.ch [ mailto:moose-dev-bounces@iam.unibe.ch <moose-dev-bounces(a)iam.unibe.ch>] *De la part de* Tudor Girba *Envoyé :* mardi 25 août 2015 23:05 *À :* moose-dev *Objet :* [Moose-dev] help with debugging the red build Hi, The Moose build is red due to a strange error: ... Starting atomic load[31m==== Startup Error: SubclassResponsibility: UTF8InvalidText had the subclass responsibility to implement #defaultAction [0mUTF8InvalidText(Object)>>subclassResponsibility UTF8InvalidText(Exception)>>defaultAction UndefinedObject>>handleSignal: Context>>handleSignal: Context>>handleSignal: ... See here: https://ci.inria.fr/moose/job/moose-6.0/308/console Could anyone investigate this? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev