jenkins Metacello build

It appears that the build failed, so I will need some initial help in figuring out how to debug the build ...

Here's the console output:
---------------------------------
Started by user Lukas Renggli
Deleting old artifacts from #1
[workspace] $ /bin/sh -xe /tmp/hudson3093928540986347263.sh
+ build.sh -i pharo -s seaside3-metacello -o seaside3-metacello
build.sh: Execution aborted (/usr/local/bin/cog)
 
  *** Warning: Warning: This package depends on the following classes:
    ParseTreeEnvironment
  You must resolve these dependencies before you will be able to load these definitions:
    ParseTreeEnvironment>>matcher
 
 
  *** Warning: Warning: This package depends on the following classes:
    SmalllintContext
  You must resolve these dependencies before you will be able to load these definitions:
    SmalllintContext>>isRenderingMethod
 
/srv/jenkins/builder/build.sh: line 170:  8613 Killed                  exec "$PHARO_VM" $PHARO_PARAM "$OUTPUT_IMAGE" "$OUTPUT_SCRIPT"
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
Finished: FAILURE
---------------------------------------------

An image and changes file was produced by the build, so I downloaded those artifacts and tried to build using the configuration load and I immediately got a deprecation warning ... so you must be doing something more in your load script than just running the config?

While we're here Do those classes ring a bell for you?

Finally, what are you using to trigger a new build?

Dale


_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

On Wednesday, 19 October 2011, Dale Henrichs <[hidden email]> wrote:
> It appears that the build failed, so I will need some initial help in figuring out how to debug the build ...
>
> Here's the console output:
> ---------------------------------
> Started by user Lukas Renggli
> Deleting old artifacts from #1
> [workspace] $ /bin/sh -xe /tmp/hudson3093928540986347263.sh
> + build.sh -i pharo -s seaside3-metacello -o seaside3-metacello
> build.sh: Execution aborted (/usr/local/bin/cog)
>
>  *** Warning: Warning: This package depends on the following classes:
>    ParseTreeEnvironment
>  You must resolve these dependencies before you will be able to load these definitions:
>    ParseTreeEnvironment>>matcher
>
>
>  *** Warning: Warning: This package depends on the following classes:
>    SmalllintContext
>  You must resolve these dependencies before you will be able to load these definitions:
>    SmalllintContext>>isRenderingMethod
>
> /srv/jenkins/builder/build.sh: line 170:  8613 Killed                  exec "$PHARO_VM" $PHARO_PARAM "$OUTPUT_IMAGE" "$OUTPUT_SCRIPT"
> Build step 'Execute shell' marked build as failure
> Archiving artifacts
> Recording test results
> Finished: FAILURE
> ---------------------------------------------
>
> An image and changes file was produced by the build, so I downloaded those artifacts and tried to build using the configuration load and I immediately got a deprecation warning ... so you must be doing something more in your load script than just running the config?

No, just the code I posted in the other mail. The build artefact must be just the starting image copied intothe workspace.

> While we're here Do those classes ring a bell for you?

Yes, too old version of RB. I renamed some classe a few months back.

> Finally, what are you using to trigger a new build?

Manual, at the moment.

Lukas

>
> Dale
>
>
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>

--
Lukas Renggli
www.lukas-renggli.ch

_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Okay ... the Seaside build is not using the latest Grease configuration and I'm, chasing a GemStone issue in parallel (GemStone 3.0.1 release for Seaside is coming up and I'm pushing the code freeze date as it is:) ... so I'll be checking in a new configuration in a half hour or so ... I'll send mail ... and then you can build whenever you get around to it ...

Dale

----- Original Message -----
| From: "Lukas Renggli" <[hidden email]>
| To: "Seaside - developer list" <[hidden email]>
| Sent: Tuesday, October 18, 2011 3:32:25 PM
| Subject: Re: [Seaside-dev] jenkins Metacello build
|
|
|
|
| On Wednesday, 19 October 2011, Dale Henrichs < [hidden email] >
| wrote:
| > It appears that the build failed, so I will need some initial help
| > in figuring out how to debug the build ...
| >
| > Here's the console output:
| > ---------------------------------
| > Started by user Lukas Renggli
| > Deleting old artifacts from #1
| > [workspace] $ /bin/sh -xe /tmp/hudson3093928540986347263.sh
| > + build.sh -i pharo -s seaside3-metacello -o seaside3-metacello
| > build.sh: Execution aborted (/usr/local/bin/cog)
| >
| > *** Warning: Warning: This package depends on the following
| > classes:
| > ParseTreeEnvironment
| > You must resolve these dependencies before you will be able to load
| > these definitions:
| > ParseTreeEnvironment>>matcher
| >
| >
| > *** Warning: Warning: This package depends on the following
| > classes:
| > SmalllintContext
| > You must resolve these dependencies before you will be able to load
| > these definitions:
| > SmalllintContext>>isRenderingMethod
| >
| > /srv/jenkins/builder/build.sh: line 170: 8613 Killed exec
| > "$PHARO_VM" $PHARO_PARAM "$OUTPUT_IMAGE" "$OUTPUT_SCRIPT"
| > Build step 'Execute shell' marked build as failure
| > Archiving artifacts
| > Recording test results
| > Finished: FAILURE
| > ---------------------------------------------
| >
| > An image and changes file was produced by the build, so I
| > downloaded those artifacts and tried to build using the
| > configuration load and I immediately got a deprecation warning ...
| > so you must be doing something more in your load script than just
| > running the config?
|
| No, just the code I posted in the other mail. The build artefact must
| be just the starting image copied intothe workspace.
|
| > While we're here Do those classes ring a bell for you?
|
| Yes, too old version of RB. I renamed some classe a few months back.
|
| > Finally, what are you using to trigger a new build?
|
| Manual, at the moment.
|
| Lukas
|
| >
| > Dale
| >
| >
| > _______________________________________________
| > seaside-dev mailing list
| > [hidden email]
| > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
| >
|
| --
| Lukas Renggli
| www.lukas-renggli.ch
|
| _______________________________________________
| seaside-dev mailing list
| [hidden email]
| http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
|
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

I've got a development version 3.0.6.2 that loads into the Jenkins image with the deprecation warning only ... of course the swazoo tests fail so we still won't get a clean build as the configs stand today, but then I've been complaining about swazoo for awhile now ...

As it happens I ported Swazoo to GemStone and cleaned up all of the test failures so I suppose I could do the same for Pharo, or we can remove Swazoo from the default load ... or you can arrange to load everything but Swazoo for the metacello tests ...

I want to do a little more testing of both the grease and seaside configs before I release 3.0.6.2 so perhaps later this evening so that at least folks will be able to load Seaside into Pharo 1.3...

Dale

----- Original Message -----
| From: "Dale Henrichs" <[hidden email]>
| To: "Seaside - developer list" <[hidden email]>
| Sent: Tuesday, October 18, 2011 3:47:00 PM
| Subject: Re: [Seaside-dev] jenkins Metacello build
|
| Okay ... the Seaside build is not using the latest Grease
| configuration and I'm, chasing a GemStone issue in parallel
| (GemStone 3.0.1 release for Seaside is coming up and I'm pushing the
| code freeze date as it is:) ... so I'll be checking in a new
| configuration in a half hour or so ... I'll send mail ... and then
| you can build whenever you get around to it ...
|
| Dale
|
| ----- Original Message -----
| | From: "Lukas Renggli" <[hidden email]>
| | To: "Seaside - developer list"
| | <[hidden email]>
| | Sent: Tuesday, October 18, 2011 3:32:25 PM
| | Subject: Re: [Seaside-dev] jenkins Metacello build
| |
| |
| |
| |
| | On Wednesday, 19 October 2011, Dale Henrichs < [hidden email]
| | >
| | wrote:
| | > It appears that the build failed, so I will need some initial
| | > help
| | > in figuring out how to debug the build ...
| | >
| | > Here's the console output:
| | > ---------------------------------
| | > Started by user Lukas Renggli
| | > Deleting old artifacts from #1
| | > [workspace] $ /bin/sh -xe /tmp/hudson3093928540986347263.sh
| | > + build.sh -i pharo -s seaside3-metacello -o seaside3-metacello
| | > build.sh: Execution aborted (/usr/local/bin/cog)
| | >
| | > *** Warning: Warning: This package depends on the following
| | > classes:
| | > ParseTreeEnvironment
| | > You must resolve these dependencies before you will be able to
| | > load
| | > these definitions:
| | > ParseTreeEnvironment>>matcher
| | >
| | >
| | > *** Warning: Warning: This package depends on the following
| | > classes:
| | > SmalllintContext
| | > You must resolve these dependencies before you will be able to
| | > load
| | > these definitions:
| | > SmalllintContext>>isRenderingMethod
| | >
| | > /srv/jenkins/builder/build.sh: line 170: 8613 Killed exec
| | > "$PHARO_VM" $PHARO_PARAM "$OUTPUT_IMAGE" "$OUTPUT_SCRIPT"
| | > Build step 'Execute shell' marked build as failure
| | > Archiving artifacts
| | > Recording test results
| | > Finished: FAILURE
| | > ---------------------------------------------
| | >
| | > An image and changes file was produced by the build, so I
| | > downloaded those artifacts and tried to build using the
| | > configuration load and I immediately got a deprecation warning
| | > ...
| | > so you must be doing something more in your load script than just
| | > running the config?
| |
| | No, just the code I posted in the other mail. The build artefact
| | must
| | be just the starting image copied intothe workspace.
| |
| | > While we're here Do those classes ring a bell for you?
| |
| | Yes, too old version of RB. I renamed some classe a few months
| | back.
| |
| | > Finally, what are you using to trigger a new build?
| |
| | Manual, at the moment.
| |
| | Lukas
| |
| | >
| | > Dale
| | >
| | >
| | > _______________________________________________
| | > seaside-dev mailing list
| | > [hidden email]
| | > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
| | >
| |
| | --
| | Lukas Renggli
| | www.lukas-renggli.ch
| |
| | _______________________________________________
| | seaside-dev mailing list
| | [hidden email]
| | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
| |
| _______________________________________________
| seaside-dev mailing list
| [hidden email]
| http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
|
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Lukas,

Go ahead and make another run ... should get swazoo test errors this time around ...

I released Grease 1.0.6.2 and Seaside 3.0.6.2: tested and loaded on:

  PharoCore 1.0, 1.1.2, 1.2.2
  Squeak 4.2
  GemStone 1.0-beta.8.6

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:)

Dale

----- Original Message -----
| From: "Dale Henrichs" <[hidden email]>
| To: "Seaside - developer list" <[hidden email]>
| Sent: Tuesday, October 18, 2011 4:49:03 PM
| Subject: Re: [Seaside-dev] jenkins Metacello build
|
| I've got a development version 3.0.6.2 that loads into the Jenkins
| image with the deprecation warning only ... of course the swazoo
| tests fail so we still won't get a clean build as the configs stand
| today, but then I've been complaining about swazoo for awhile now
| ...
|
| As it happens I ported Swazoo to GemStone and cleaned up all of the
| test failures so I suppose I could do the same for Pharo, or we can
| remove Swazoo from the default load ... or you can arrange to load
| everything but Swazoo for the metacello tests ...
|
| I want to do a little more testing of both the grease and seaside
| configs before I release 3.0.6.2 so perhaps later this evening so
| that at least folks will be able to load Seaside into Pharo 1.3...
|
| Dale
|
| ----- Original Message -----
| | From: "Dale Henrichs" <[hidden email]>
| | To: "Seaside - developer list"
| | <[hidden email]>
| | Sent: Tuesday, October 18, 2011 3:47:00 PM
| | Subject: Re: [Seaside-dev] jenkins Metacello build
| |
| | Okay ... the Seaside build is not using the latest Grease
| | configuration and I'm, chasing a GemStone issue in parallel
| | (GemStone 3.0.1 release for Seaside is coming up and I'm pushing
| | the
| | code freeze date as it is:) ... so I'll be checking in a new
| | configuration in a half hour or so ... I'll send mail ... and then
| | you can build whenever you get around to it ...
| |
| | Dale
| |
| | ----- Original Message -----
| | | From: "Lukas Renggli" <[hidden email]>
| | | To: "Seaside - developer list"
| | | <[hidden email]>
| | | Sent: Tuesday, October 18, 2011 3:32:25 PM
| | | Subject: Re: [Seaside-dev] jenkins Metacello build
| | |
| | |
| | |
| | |
| | | On Wednesday, 19 October 2011, Dale Henrichs <
| | | [hidden email]
| | | >
| | | wrote:
| | | > It appears that the build failed, so I will need some initial
| | | > help
| | | > in figuring out how to debug the build ...
| | | >
| | | > Here's the console output:
| | | > ---------------------------------
| | | > Started by user Lukas Renggli
| | | > Deleting old artifacts from #1
| | | > [workspace] $ /bin/sh -xe /tmp/hudson3093928540986347263.sh
| | | > + build.sh -i pharo -s seaside3-metacello -o seaside3-metacello
| | | > build.sh: Execution aborted (/usr/local/bin/cog)
| | | >
| | | > *** Warning: Warning: This package depends on the following
| | | > classes:
| | | > ParseTreeEnvironment
| | | > You must resolve these dependencies before you will be able to
| | | > load
| | | > these definitions:
| | | > ParseTreeEnvironment>>matcher
| | | >
| | | >
| | | > *** Warning: Warning: This package depends on the following
| | | > classes:
| | | > SmalllintContext
| | | > You must resolve these dependencies before you will be able to
| | | > load
| | | > these definitions:
| | | > SmalllintContext>>isRenderingMethod
| | | >
| | | > /srv/jenkins/builder/build.sh: line 170: 8613 Killed exec
| | | > "$PHARO_VM" $PHARO_PARAM "$OUTPUT_IMAGE" "$OUTPUT_SCRIPT"
| | | > Build step 'Execute shell' marked build as failure
| | | > Archiving artifacts
| | | > Recording test results
| | | > Finished: FAILURE
| | | > ---------------------------------------------
| | | >
| | | > An image and changes file was produced by the build, so I
| | | > downloaded those artifacts and tried to build using the
| | | > configuration load and I immediately got a deprecation warning
| | | > ...
| | | > so you must be doing something more in your load script than
| | | > just
| | | > running the config?
| | |
| | | No, just the code I posted in the other mail. The build artefact
| | | must
| | | be just the starting image copied intothe workspace.
| | |
| | | > While we're here Do those classes ring a bell for you?
| | |
| | | Yes, too old version of RB. I renamed some classe a few months
| | | back.
| | |
| | | > Finally, what are you using to trigger a new build?
| | |
| | | Manual, at the moment.
| | |
| | | Lukas
| | |
| | | >
| | | > Dale
| | | >
| | | >
| | | > _______________________________________________
| | | > seaside-dev mailing list
| | | > [hidden email]
| | | > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
| | | >
| | |
| | | --
| | | Lukas Renggli
| | | www.lukas-renggli.ch
| | |
| | | _______________________________________________
| | | seaside-dev mailing list
| | | [hidden email]
| | | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
| | |
| | _______________________________________________
| | seaside-dev mailing list
| | [hidden email]
| | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
| |
| _______________________________________________
| seaside-dev mailing list
| [hidden email]
| http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
|
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

I just started it.

On 19 October 2011 06:52, Dale Henrichs <[hidden email]> wrote:


--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

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.

Lukas

On Wednesday, 19 October 2011, Lukas Renggli <[hidden email]> wrote:
> I just started it.
>
> On 19 October 2011 06:52, Dale Henrichs <[hidden email]> wrote:
>> Lukas,
>>
>> Go ahead and make another run ... should get swazoo test errors this time around ...
>>
>> I released Grease 1.0.6.2 and Seaside 3.0.6.2: tested and loaded on:
>>
>>  PharoCore 1.0, 1.1.2, 1.2.2
>>  Squeak 4.2
>>  GemStone 1.0-beta.8.6
>>
>> 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:)
>>
>> Dale
>>
>> ----- Original Message -----
>> | From: "Dale Henrichs" <[hidden email]>
>> | To: "Seaside - developer list" <[hidden email]>
>> | Sent: Tuesday, October 18, 2011 4:49:03 PM
>> | Subject: Re: [Seaside-dev] jenkins Metacello build
>> |
>> | I've got a development version 3.0.6.2 that loads into the Jenkins
>> | image with the deprecation warning only ... of course the swazoo
>> | tests fail so we still won't get a clean build as the configs stand
>> | today, but then I've been complaining about swazoo for awhile now
>> | ...
>> |
>> | As it happens I ported Swazoo to GemStone and cleaned up all of the
>> | test failures so I suppose I could do the same for Pharo, or we can
>> | remove Swazoo from the default load ... or you can arrange to load
>> | everything but Swazoo for the metacello tests ...
>> |
>> | I want to do a little more testing of both the grease and seaside
>> | configs before I release 3.0.6.2 so perhaps later this evening so
>> | that at least folks will be able to load Seaside into Pharo 1.3...
>> |
>> | Dale
>> |
>> | ----- Original Message -----
>> | | From: "Dale Henrichs" <[hidden email]>
>> | | To: "Seaside - developer list"
>> | | <[hidden email]>
>> | | Sent: Tuesday, October 18, 2011 3:47:00 PM
>> | | Subject: Re: [Seaside-dev] jenkins Metacello build
>> | |
>> | | Okay ... the Seaside build is not using the latest Grease
>> | | configuration and I'm, chasing a GemStone issue in parallel
>> | | (GemStone 3.0.1 release for Seaside is coming up and I'm pushing
>> | | the
>> | | code freeze date as it is:) ... so I'll be checking in a new
>> | | configuration in a half hour or so ... I'll send mail ... and then
>> | | you can build whenever you get around to it ...
>> | |
>> | | Dale
>> | |
>> | | ----- Original Message -----
>> | | | From: "Lukas Renggli" <[hidden email]>
>> | | | To: "Seaside - developer list"
>> | | | <[hidden email]>
>> | | | Sent: Tuesday, October 18, 2011 3:32:25 PM
>> | | | Subject: Re: [Seaside-dev] jenkins Metacello build
>> | | |
>> | | |
>> | | |
>> | | |
>> | | | On Wednesday, 19 October 2011, Dale Henrichs <
>> | | | [hidden email]
>> | | | >
>> | | | wrote:
>> | | | > It appears that the build failed, so I will need some initial
>> | | | > help
>> | | | > in figuring out how to debug the build ...
>> | | | >
>> | | | > Here's the console output:
>> | | | > ---------------------------------
>> | | | > Started by user Lukas Renggli
>> | | | > Deleting old artifacts from #1
>> | | | > [workspace] $ /bin/sh -xe /tmp/hudson3093928540986347263.sh
>> | | | > + build.sh -i pharo -s seaside3-metacello -o seaside3-metacello
>> | | | > build.sh: Execution aborted (/usr/local/bin/cog)
>> | | | >
>> | | | > *** Warning: Warning: This package depends on the following
>> | | | > classes:
>> | | | > ParseTreeEnvironment
>> | | | > You must resolve these dependencies before you will be able to
>> | | | > load
> --
> Lukas Renggli
> www.lukas-renggli.ch
>

--
Lukas Renggli
www.lukas-renggli.ch

_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

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) ...

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

--
Lukas Renggli
www.lukas-renggli.ch

_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Are there different tests run by Jenkins other than the SUnit tests? I swear I ran all of the SUNIT tests for seaside in all of the those platforms (except Pharo 1.3) and the only errors/failures that showed up were Swazoo failures ...

I'll reload on Pharo1.3 later today (got a GemStone release to push:) and see what I can see...

Dale

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

The good news: This has nothing to do with Metacello.

The bad news: This is a very weird bug surfacing here.

It disappears when loading OB-Refactory and it comes back when
unloading OB-Refactory. However running the code that causes the
problem does not execute any code in OB-Refactory :-/

Lukas


On 19 October 2011 17:48, Dale Henrichs <[hidden email]> wrote:


--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

I could not figure out what is wrong. Now I do not run Lint anymore
and the Metacello build is green.

Lukas

On 19 October 2011 20:59, Lukas Renggli <[hidden email]> wrote:


--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Hmmm sounds like a rogue extension method ....

Dale

----- Original Message -----
| From: "Lukas Renggli" <[hidden email]>
| To: "Seaside - developer list" <[hidden email]>
| Sent: Wednesday, October 19, 2011 11:59:14 AM
| Subject: Re: [Seaside-dev] jenkins Metacello build
|
| The good news: This has nothing to do with Metacello.
|
| The bad news: This is a very weird bug surfacing here.
|
| It disappears when loading OB-Refactory and it comes back when
| unloading OB-Refactory. However running the code that causes the
| problem does not execute any code in OB-Refactory :-/
|
| Lukas
|
|
| On 19 October 2011 17:48, Dale Henrichs <[hidden email]> wrote:
| > Are there different tests run by Jenkins other than the SUnit
| > tests? I swear I ran all of the SUNIT tests for seaside in all of
| > the those platforms (except Pharo 1.3) and the only
| > errors/failures that showed up were Swazoo failures ...
| >
| > I'll reload on Pharo1.3 later today (got a GemStone release to
| > push:) and see what I can see...
| >
| > Dale
| >
| > ----- Original Message -----
| > | From: "Lukas Renggli" <[hidden email]>
| > | To: "Seaside - developer list"
| > | <[hidden email]>
| > | Sent: Tuesday, October 18, 2011 11:03:52 PM
| > | Subject: Re: [Seaside-dev] jenkins Metacello build
| > |
| > |
| > | 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) ...
| > |
| > | On Wednesday, 19 October 2011, Lukas Renggli < [hidden email]
| > | >
| > | wrote:
| > | > 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.
| > | >
| > | > Lukas
| > | >
| > | > On Wednesday, 19 October 2011, Lukas Renggli <
| > | > [hidden email] >
| > | > wrote:
| > | >> I just started it.
| > | >>
| > | >> On 19 October 2011 06:52, Dale Henrichs < [hidden email]
| > | >> >
| > | >> wrote:
| > | >>> Lukas,
| > | >>>
| > | >>> Go ahead and make another run ... should get swazoo test
| > | >>> errors
| > | >>> this time around ...
| > | >>>
| > | >>> I released Grease 1.0.6.2 and Seaside 3.0.6.2 : tested and
| > | >>> loaded
| > | >>> on:
| > | >>>
| > | >>> PharoCore 1.0, 1.1.2, 1.2.2
| > | >>> Squeak 4.2
| > | >>> GemStone 1.0-beta.8.6
| > | >>>
| > | >>> 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:)
| > | >>>
| > | >>> Dale
| > | >>>
| > | >>> ----- Original Message -----
| > | >>> | From: "Dale Henrichs" < [hidden email] >
| > | >>> | To: "Seaside - developer list" <
| > | >>> | [hidden email] >
| > | >>> | Sent: Tuesday, October 18, 2011 4:49:03 PM
| > | >>> | Subject: Re: [Seaside-dev] jenkins Metacello build
| > | >>> |
| > | >>> | I've got a development version 3.0.6.2 that loads into the
| > | >>> | Jenkins
| > | >>> | image with the deprecation warning only ... of course the
| > | >>> | swazoo
| > | >>> | tests fail so we still won't get a clean build as the
| > | >>> | configs
| > | >>> | stand
| > | >>> | today, but then I've been complaining about swazoo for
| > | >>> | awhile
| > | >>> | now
| > | >>> | ...
| > | >>> |
| > | >>> | As it happens I ported Swazoo to GemStone and cleaned up
| > | >>> | all of
| > | >>> | the
| > | >>> | test failures so I suppose I could do the same for Pharo,
| > | >>> | or we
| > | >>> | can
| > | >>> | remove Swazoo from the default load ... or you can arrange
| > | >>> | to
| > | >>> | load
| > | >>> | everything but Swazoo for the metacello tests ...
| > | >>> |
| > | >>> | I want to do a little more testing of both the grease and
| > | >>> | seaside
| > | >>> | configs before I release 3.0.6.2 so perhaps later this
| > | >>> | evening
| > | >>> | so
| > | >>> | that at least folks will be able to load Seaside into Pharo
| > | >>> | 1.3...
| > | >>> |
| > | >>> | Dale
| > | >>> |
| > | >>> | ----- Original Message -----
| > | >>> | | From: "Dale Henrichs" < [hidden email] >
| > | >>> | | To: "Seaside - developer list"
| > | >>> | | < [hidden email] >
| > | >>> | | Sent: Tuesday, October 18, 2011 3:47:00 PM
| > | >>> | | Subject: Re: [Seaside-dev] jenkins Metacello build
| > | >>> | |
| > | >>> | | Okay ... the Seaside build is not using the latest Grease
| > | >>> | | configuration and I'm, chasing a GemStone issue in
| > | >>> | | parallel
| > | >>> | | (GemStone 3.0.1 release for Seaside is coming up and I'm
| > | >>> | | pushing
| > | >>> | | the
| > | >>> | | code freeze date as it is:) ... so I'll be checking in a
| > | >>> | | new
| > | >>> | | configuration in a half hour or so ... I'll send mail ...
| > | >>> | | and
| > | >>> | | then
| > | >>> | | you can build whenever you get around to it ...
| > | >>> | |
| > | >>> | | Dale
| > | >>> | |
| > | >>> | | ----- Original Message -----
| > | >>> | | | From: "Lukas Renggli" < [hidden email] >
| > | >>> | | | To: "Seaside - developer list"
| > | >>> | | | < [hidden email] >
| > | >>> | | | Sent: Tuesday, October 18, 2011 3:32:25 PM
| > | >>> | | | Subject: Re: [Seaside-dev] jenkins Metacello build
| > | >>> | | |
| > | >>> | | |
| > | >>> | | |
| > | >>> | | |
| > | >>> | | | On Wednesday, 19 October 2011, Dale Henrichs <
| > | >>> | | | [hidden email]
| > | >>> | | | >
| > | >>> | | | wrote:
| > | >>> | | | > It appears that the build failed, so I will need some
| > | >>> | | | > initial
| > | >>> | | | > help
| > | >>> | | | > in figuring out how to debug the build ...
| > | >>> | | | >
| > | >>> | | | > Here's the console output:
| > | >>> | | | > ---------------------------------
| > | >>> | | | > Started by user Lukas Renggli
| > | >>> | | | > Deleting old artifacts from #1
| > | >>> | | | > [workspace] $ /bin/sh -xe /tmp> --
| > | >> Lukas Renggli
| > | >> www.lukas-renggli.ch
| > | >>
| > | >
| > | > --
| > | > Lukas Renggli
| > | > www.lukas-renggli.ch
| > | >
| > |
| > | --
| > | Lukas Renggli
| > | www.lukas-renggli.ch
| > |
| > | _______________________________________________
| > | seaside-dev mailing list
| > | [hidden email]
| > | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
| > |
| > _______________________________________________
| > seaside-dev mailing list
| > [hidden email]
| > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
| >
|
|
|
| --
| Lukas Renggli
| www.lukas-renggli.ch
| _______________________________________________
| seaside-dev mailing list
| [hidden email]
| http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
|
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Excellent!

----- Original Message -----
| From: "Lukas Renggli" <[hidden email]>
| To: "Seaside - developer list" <[hidden email]>
| Sent: Wednesday, October 19, 2011 12:34:11 PM
| Subject: Re: [Seaside-dev] jenkins Metacello build
|
| I could not figure out what is wrong. Now I do not run Lint anymore
| and the Metacello build is green.
|
| Lukas
|
| On 19 October 2011 20:59, Lukas Renggli <[hidden email]> wrote:
| > The good news: This has nothing to do with Metacello.
| >
| > The bad news: This is a very weird bug surfacing here.
| >
| > It disappears when loading OB-Refactory and it comes back when
| > unloading OB-Refactory. However running the code that causes the
| > problem does not execute any code in OB-Refactory :-/
| >
| > Lukas
| >
| >
| > On 19 October 2011 17:48, Dale Henrichs <[hidden email]>
| > wrote:
| >> Are there different tests run by Jenkins other than the SUnit
| >> tests? I swear I ran all of the SUNIT tests for seaside in all of
| >> the those platforms (except Pharo 1.3) and the only
| >> errors/failures that showed up were Swazoo failures ...
| >>
| >> I'll reload on Pharo1.3 later today (got a GemStone release to
| >> push:) and see what I can see...
| >>
| >> Dale
| >>
| >> ----- Original Message -----
| >> | From: "Lukas Renggli" <[hidden email]>
| >> | To: "Seaside - developer list"
| >> | <[hidden email]>
| >> | Sent: Tuesday, October 18, 2011 11:03:52 PM
| >> | Subject: Re: [Seaside-dev] jenkins Metacello build
| >> |
| >> |
| >> | 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) ...
| >> |
| >> | On Wednesday, 19 October 2011, Lukas Renggli < [hidden email]
| >> | >
| >> | wrote:
| >> | > 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.
| >> | >
| >> | > Lukas
| >> | >
| >> | > On Wednesday, 19 October 2011, Lukas Renggli <
| >> | > [hidden email] >
| >> | > wrote:
| >> | >> I just started it.
| >> | >>
| >> | >> On 19 October 2011 06:52, Dale Henrichs < [hidden email]
| >> | >> >
| >> | >> wrote:
| >> | >>> Lukas,
| >> | >>>
| >> | >>> Go ahead and make another run ... should get swazoo test
| >> | >>> errors
| >> | >>> this time around ...
| >> | >>>
| >> | >>> I released Grease 1.0.6.2 and Seaside 3.0.6.2 : tested and
| >> | >>> loaded
| >> | >>> on:
| >> | >>>
| >> | >>> PharoCore 1.0, 1.1.2, 1.2.2
| >> | >>> Squeak 4.2
| >> | >>> GemStone 1.0-beta.8.6
| >> | >>>
| >> | >>> 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:)
| >> | >>>
| >> | >>> Dale
| >> | >>>
| >> | >>> ----- Original Message -----
| >> | >>> | From: "Dale Henrichs" < [hidden email] >
| >> | >>> | To: "Seaside - developer list" <
| >> | >>> | [hidden email] >
| >> | >>> | Sent: Tuesday, October 18, 2011 4:49:03 PM
| >> | >>> | Subject: Re: [Seaside-dev] jenkins Metacello build
| >> | >>> |
| >> | >>> | I've got a development version 3.0.6.2 that loads into the
| >> | >>> | Jenkins
| >> | >>> | image with the deprecation warning only ... of course the
| >> | >>> | swazoo
| >> | >>> | tests fail so we still won't get a clean build as the
| >> | >>> | configs
| >> | >>> | stand
| >> | >>> | today, but then I've been complaining about swazoo for
| >> | >>> | awhile
| >> | >>> | now
| >> | >>> | ...
| >> | >>> |
| >> | >>> | As it happens I ported Swazoo to GemStone and cleaned up
| >> | >>> | all of
| >> | >>> | the
| >> | >>> | test failures so I suppose I could do the same for Pharo,
| >> | >>> | or we
| >> | >>> | can
| >> | >>> | remove Swazoo from the default load ... or you can arrange
| >> | >>> | to
| >> | >>> | load
| >> | >>> | everything but Swazoo for the metacello tests ...
| >> | >>> |
| >> | >>> | I want to do a little more testing of both the grease and
| >> | >>> | seaside
| >> | >>> | configs before I release 3.0.6.2 so perhaps later this
| >> | >>> | evening
| >> | >>> | so
| >> | >>> | that at least folks will be able to load Seaside into
| >> | >>> | Pharo
| >> | >>> | 1.3...
| >> | >>> |
| >> | >>> | Dale
| >> | >>> |
| >> | >>> | ----- Original Message -----
| >> | >>> | | From: "Dale Henrichs" < [hidden email] >
| >> | >>> | | To: "Seaside - developer list"
| >> | >>> | | < [hidden email] >
| >> | >>> | | Sent: Tuesday, October 18, 2011 3:47:00 PM
| >> | >>> | | Subject: Re: [Seaside-dev] jenkins Metacello build
| >> | >>> | |
| >> | >>> | | Okay ... the Seaside build is not using the latest
| >> | >>> | | Grease
| >> | >>> | | configuration and I'm, chasing a GemStone issue in
| >> | >>> | | parallel
| >> | >>> | | (GemStone 3.0.1 release for Seaside is coming up and I'm
| >> | >>> | | pushing
| >> | >>> | | the
| >> | >>> | | code freeze date as it is:) ... so I'll be checking in a
| >> | >>> | | new
| >> | >>> | | configuration in a half hour or so ... I'll send mail
| >> | >>> | | ... and
| >> | >>> | | then
| >> | >>> | | you can build whenever you get around to it ...
| >> | >>> | |
| >> | >>> | | Dale
| >> | >>> | |
| >> | >>> | | ----- Original Message -----
| >> | >>> | | | From: "Lukas Renggli" < [hidden email] >
| >> | >>> | | | To: "Seaside - developer list"
| >> | >>> | | | < [hidden email] >
| >> | >>> | | | Sent: Tuesday, October 18, 2011 3:32:25 PM
| >> | >>> | | | Subject: Re: [Seaside-dev] jenkins Metacello build
| >> | >>> | | |
| >> | >>> | | |
| >> | >>> | | |
| >> | >>> | | |
| >> | >>> | | | On Wednesday, 19 October 2011, Dale Henrichs <
| >> | >>> | | | [hidden email]
| >> | >>> | | | >
| >> | >>> | | | wrote:
| >> | >>> | | | > It appears that the build failed, so I will need
| >> | >>> | | | > some
| >> | >>> | | | > initial
| >> | >>> | | | > help
| >> | >>> | | | > in figuring out how to debug the build ...
| >> | >>> | | | >
| >> | >>> | | | > Here's the console output:
| >> | >>> | | | > ---------------------------------
| >> | >>> | | | > Started by user Lukas Renggli
| >> | >>> | | | > Deleting old artifacts from #1
| >> | >>> | | | > [workspace] $ /bin/sh -xe /tmp> --
| >> | >> Lukas Renggli
| >> | >> www.lukas-renggli.ch
| >> | >>
| >> | >
| >> | > --
| >> | > Lukas Renggli
| >> | > www.lukas-renggli.ch
| >> | >
| >> |
| >> | --
| >> | Lukas Renggli
| >> | www.lukas-renggli.ch
| >> |
| >> | _______________________________________________
| >> | seaside-dev mailing list
| >> | [hidden email]
| >> | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
| >> |
| >> _______________________________________________
| >> seaside-dev mailing list
| >> [hidden email]
| >> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
| >>
| >
| >
| >
| > --
| > Lukas Renggli
| > www.lukas-renggli.ch
| >
|
|
|
| --
| Lukas Renggli
| www.lukas-renggli.ch
| _______________________________________________
| seaside-dev mailing list
| [hidden email]
| http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
|
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev