Actually everything loads fine, the error happen when running lint on the code. So there must be something disfunc in RB (the same tests work in the other images) ...<br><br>On Wednesday, 19 October 2011, Lukas Renggli <<a href="mailto:renggli@gmail.com">renggli@gmail.com</a>> wrote:<br>
> Still broken because of inconsistent versions of RB. Please make sure that the latest versions from squeaksource/rb of the packages AST-* and Refactoring-* are used.<br>><br>> Lukas<br>><br>> On Wednesday, 19 October 2011, Lukas Renggli <<a href="mailto:renggli@gmail.com">renggli@gmail.com</a>> wrote:<br>
>> I just started it.<br>>><br>>> On 19 October 2011 06:52, Dale Henrichs <<a href="mailto:dhenrich@vmware.com">dhenrich@vmware.com</a>> wrote:<br>>>> Lukas,<br>>>><br>>>> Go ahead and make another run ... should get swazoo test errors this time around ...<br>
>>><br>>>> I released Grease 1.0.6.2 and Seaside <a href="http://3.0.6.2">3.0.6.2</a>: tested and loaded on:<br>>>><br>>>> PharoCore 1.0, 1.1.2, 1.2.2<br>>>> Squeak 4.2<br>>>> GemStone 1.0-beta.8.6<br>
>>><br>>>> Deal with Swazoo tests at a later date at least folks should be able to load Seaside again in Pharo 1.3, but then we'll find that out when you run jenkins as I've run out of time:)<br>
>>><br>>>> Dale<br>>>><br>>>> ----- Original Message -----<br>>>> | From: "Dale Henrichs" <<a href="mailto:dhenrich@vmware.com">dhenrich@vmware.com</a>><br>>>> | To: "Seaside - developer list" <<a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a>><br>
>>> | Sent: Tuesday, October 18, 2011 4:49:03 PM<br>>>> | Subject: Re: [Seaside-dev] jenkins Metacello build<br>>>> |<br>>>> | I've got a development version 3.0.6.2 that loads into the Jenkins<br>
>>> | image with the deprecation warning only ... of course the swazoo<br>>>> | tests fail so we still won't get a clean build as the configs stand<br>>>> | today, but then I've been complaining about swazoo for awhile now<br>
>>> | ...<br>>>> |<br>>>> | As it happens I ported Swazoo to GemStone and cleaned up all of the<br>>>> | test failures so I suppose I could do the same for Pharo, or we can<br>>>> | remove Swazoo from the default load ... or you can arrange to load<br>
>>> | everything but Swazoo for the metacello tests ...<br>>>> |<br>>>> | I want to do a little more testing of both the grease and seaside<br>>>> | configs before I release 3.0.6.2 so perhaps later this evening so<br>
>>> | that at least folks will be able to load Seaside into Pharo 1.3...<br>>>> |<br>>>> | Dale<br>>>> |<br>>>> | ----- Original Message -----<br>>>> | | From: "Dale Henrichs" <<a href="mailto:dhenrich@vmware.com">dhenrich@vmware.com</a>><br>
>>> | | To: "Seaside - developer list"<br>>>> | | <<a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a>><br>>>> | | Sent: Tuesday, October 18, 2011 3:47:00 PM<br>
>>> | | Subject: Re: [Seaside-dev] jenkins Metacello build<br>>>> | |<br>>>> | | Okay ... the Seaside build is not using the latest Grease<br>>>> | | configuration and I'm, chasing a GemStone issue in parallel<br>
>>> | | (GemStone 3.0.1 release for Seaside is coming up and I'm pushing<br>>>> | | the<br>>>> | | code freeze date as it is:) ... so I'll be checking in a new<br>>>> | | configuration in a half hour or so ... I'll send mail ... and then<br>
>>> | | you can build whenever you get around to it ...<br>>>> | |<br>>>> | | Dale<br>>>> | |<br>>>> | | ----- Original Message -----<br>>>> | | | From: "Lukas Renggli" <<a href="mailto:renggli@gmail.com">renggli@gmail.com</a>><br>
>>> | | | To: "Seaside - developer list"<br>>>> | | | <<a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a>><br>>>> | | | Sent: Tuesday, October 18, 2011 3:32:25 PM<br>
>>> | | | Subject: Re: [Seaside-dev] jenkins Metacello build<br>>>> | | |<br>>>> | | |<br>>>> | | |<br>>>> | | |<br>>>> | | | On Wednesday, 19 October 2011, Dale Henrichs <<br>
>>> | | | <a href="mailto:dhenrich@vmware.com">dhenrich@vmware.com</a><br>>>> | | | ><br>>>> | | | wrote:<br>>>> | | | > It appears that the build failed, so I will need some initial<br>
>>> | | | > help<br>>>> | | | > in figuring out how to debug the build ...<br>>>> | | | ><br>>>> | | | > Here's the console output:<br>>>> | | | > ---------------------------------<br>
>>> | | | > Started by user Lukas Renggli<br>>>> | | | > Deleting old artifacts from #1<br>>>> | | | > [workspace] $ /bin/sh -xe /tmp> --<br>>> Lukas Renggli<br>>> <a href="http://www.lukas-renggli.ch">www.lukas-renggli.ch</a><br>
>><br>><br>> --<br>> Lukas Renggli<br>> <a href="http://www.lukas-renggli.ch">www.lukas-renggli.ch</a><br>><br><br>-- <br>Lukas Renggli<br><a href="http://www.lukas-renggli.ch">www.lukas-renggli.ch</a><br>