Smalltalk › Frameworks & Tools › Seaside › Seaside Development

grease and seaside on Squeak

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

11 messages Options

Johan Brichau-2

grease and seaside on Squeak

Hi all,

Currently, both Grease-1.1.6 and Seaside-3.1 have failing tests on Squeak.
The github repository has automated Travis CI builds setup for Squeak [1,2], so we can easily monitor this:

[1] https://travis-ci.org/glassdb/Grease
[2] https://travis-ci.org/glassdb/Seaside31

It would be good if someone can fix them or tell me to mark some parts as non-loadable on Squeak (e.g. Slime in Squeak).
Otherwise, I will disable the automated builds as they are now always reporting a failure.

The github repo's master branch is a mirror of the smalltalkhub one:
https://github.com/glassdb/Seaside31

The Travis CI build for that is here:
https://travis-ci.org/glassdb/Seaside31

You just need to make sure you check the build for the master branch, e.g.: https://travis-ci.org/glassdb/Seaside31/builds/19433103

Similar for Grease, but here is only one branch for all platforms:
https://github.com/glassdb/Grease
https://travis-ci.org/glassdb/Grease

If you have fixes, you can immediately commit them to Smalltalkhub, or you can create a fork of the github repo and submit a pull request.
Either way, I will pick up the changes and make sure to sync the repositories.

Maybe someone can forward this to Squeak dev mailinglist too? (I am not a subscriber there).

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

Tobias Pape

Re: grease and seaside on Squeak

Hey Johan,

On 23.03.2014, at 10:59, Johan Brichau <[hidden email]> wrote:

> Hi all,
>
> Currently, both Grease-1.1.6 and Seaside-3.1 have failing tests on Squeak.
> The github repository has automated Travis CI builds setup for Squeak [1,2], so we can easily monitor this:
>
> [1] https://travis-ci.org/glassdb/Grease
> [2] https://travis-ci.org/glassdb/Seaside31
>

I am on it.
Sadly builder-ci needs a small patch to cope for the fact that
the released 4.4 image still hast a redirect bug...

> It would be good if someone can fix them or tell me to mark some parts as non-loadable on Squeak (e.g. Slime in Squeak).
> Otherwise, I will disable the automated builds as they are now always reporting a failure.

GREASE:
I have fixed the only one Test that failed for me in Squeak 4.4 and Squeak 4.5.
The fix is in Grease-Slime-topa.26.
SEASIDE:
Also here, only one test failed.
The fix is in Seaside-Core-topa.811.

>
> The github repo's master branch is a mirror of the smalltalkhub one:
> https://github.com/glassdb/Seaside31
>
> The Travis CI build for that is here:
> https://travis-ci.org/glassdb/Seaside31
>
> You just need to make sure you check the build for the master branch, e.g.: https://travis-ci.org/glassdb/Seaside31/builds/19433103
>
> Similar for Grease, but here is only one branch for all platforms:
> https://github.com/glassdb/Grease
> https://travis-ci.org/glassdb/Grease
>
> If you have fixes, you can immediately commit them to Smalltalkhub, or you can create a fork of the github repo and submit a pull request.
> Either way, I will pick up the changes and make sure to sync the repositories.

:) Ok Fixes are in the STHub repo

Should https://github.com/dalehenrich/builderCI/pull/59 be accepted, please
add Squeak-4.5 to the test matrix :)

Thanks for taking care!

Best
-Tobias

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

signature.asc (1K) Download Attachment

Stephan Eggermont-3

Re: grease and seaside on Squeak

In reply to this post by Johan Brichau-2

From Johan’s tweets, I have the impression he is currently otherwise engaged (moving office)

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

Johan Brichau-2

Re: grease and seaside on Squeak

In reply to this post by Tobias Pape

Hey Tobias,

Sorry that it took a while to pick up your fixes.

On 25 Mar 2014, at 14:09, Tobias Pape <[hidden email]> wrote:

Sadly builder-ci needs a small patch to cope for the fact that
the released 4.4 image still hast a redirect bug…

Is that the cause of the failures?

Because the Grease build on Travis shows the same failing tests.

It would be good if someone can fix them or tell me to mark some parts as non-loadable on Squeak (e.g. Slime in Squeak).
Otherwise, I will disable the automated builds as they are now always reporting a failure.

GREASE:
I have fixed the only one Test that failed for me in Squeak 4.4 and Squeak 4.5.
The fix is in Grease-Slime-topa.26.
SEASIDE:
Also here, only one test failed.
The fix is in Seaside-Core-topa.811.

thank you!

They are now in version 3.1.1 of Seaside and version 1.1.7 of Grease.

:) Ok Fixes are in the STHub repo

Should https://github.com/dalehenrich/builderCI/pull/59 be accepted, please
add Squeak-4.5 to the test matrix :)

I will pull Dale.

He should emerge from the trenches any moment now :-)

thanks a lot!

Johan

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

EstebanLM

Re: grease and seaside on Squeak

well… now mongotalk configuration fails:

Fetched -> Magritte-Pharo3-Model-StephanEggermont.1 --- http://smalltalkhub.com/mc/Magritte/Magritte3/main/ --- http://smalltalkhub.com/mc/Magritte/Magritte3/main/
Project: MongoTalk stable [1.5.6]
Project: Grease stable [1.1.7]
...RETRY-> Grease-Slime-topa.26
...RETRY-> Grease-Slime-topa.26
...FAILED-> Grease-Slime-topa.26Could not resolve: Grease-Slime [ Grease-Slime-topa.26] in /var/lib/jenkins/jobs/rpg/workspace/package-cache http://smalltalkhub.com/mc/Seaside/Grease11/main/
MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer:
MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: in Block: linearLoadPackageSpec: packageSpec gofer: gofer...
MetacelloPharo30Platform(MetacelloPlatform)>>do:displaying:
MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer:
MetacelloPackageSpec>>loadUsing:gofer:
MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: in Block: [ :pkg | pkg loadUsing: self gofer: gofer ]
OrderedCollection>>do:
MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories:
MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories: in Block: [ super linearLoadPackageSpecs: packageSpecs repos...etc...
BlockClosure>>ensure:
MetacelloLoaderPolicy>>pushLoadDirective:during:
MetacelloLoaderPolicy>>pushLinearLoadDirectivesDuring:for:
MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories:
MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>load
MetacelloMCVersionSpecLoader>>load
MetacelloMCVersion>>executeLoadFromArray:
MetacelloMCVersion>>fetchRequiredFromArray: in Block: [ :dict | ^ self executeLoadFromArray: anArray ]
MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [ ^ aBlock value: dict ]
BlockClosure>>on:do:
MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary:
MetacelloMCVersion>>fetchRequiredFromArray: in Block: [ ...
BlockClosure>>ensure:
MetacelloMCVersion>>fetchRequiredFromArray: in Block: [ ...
MetacelloPharo30Platform(MetacelloPlatform)>>do:displaying:
MetacelloMCVersion>>fetchRequiredFromArray:
MetacelloMCProjectSpec>>loadVersion: in Block: [ :dict | ...
MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [ ^ aBlock value: dict ]
BlockClosure>>on:do:
MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary:
MetacelloMCProjectSpec>>loadVersion:
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
Sending e-mails to: [hidden email]
Finished: FAILURE

honestly, we need to enhance the way we work with configurations… they are too weak.

(it is not a complain against anyone, just an observation that becomes obvious day by day :P)

On 05 Apr 2014, at 09:58, Johan Brichau <[hidden email]> wrote:

Hey Tobias,

Sorry that it took a while to pick up your fixes.

On 25 Mar 2014, at 14:09, Tobias Pape <[hidden email]> wrote:

Sadly builder-ci needs a small patch to cope for the fact that
the released 4.4 image still hast a redirect bug…

Is that the cause of the failures?
Because the Grease build on Travis shows the same failing tests.

It would be good if someone can fix them or tell me to mark some parts as non-loadable on Squeak (e.g. Slime in Squeak).
Otherwise, I will disable the automated builds as they are now always reporting a failure.

GREASE:
I have fixed the only one Test that failed for me in Squeak 4.4 and Squeak 4.5.
The fix is in Grease-Slime-topa.26.
SEASIDE:
Also here, only one test failed.
The fix is in Seaside-Core-topa.811.

thank you!
They are now in version 3.1.1 of Seaside and version 1.1.7 of Grease.

:) Ok Fixes are in the STHub repo

Should https://github.com/dalehenrich/builderCI/pull/59 be accepted, please
add Squeak-4.5 to the test matrix :)

I will pull Dale.
He should emerge from the trenches any moment now :-)

thanks a lot!

Johan
_______________________________________________
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

Johan Brichau-2

Re: grease and seaside on Squeak

I don’t think it has anything to do with the configuration itself.

I have the same load problem on Travis CI for Grease and not on the Jenkins CI

I’m also puzzled… but looking into it

On 05 Apr 2014, at 15:07, Esteban Lorenzano <[hidden email]> wrote:

well… now mongotalk configuration fails:
Fetched -> Magritte-Pharo3-Model-StephanEggermont.1 --- http://smalltalkhub.com/mc/Magritte/Magritte3/main/ --- http://smalltalkhub.com/mc/Magritte/Magritte3/main/
Project: MongoTalk stable [1.5.6]
Project: Grease stable [1.1.7]
...RETRY-> Grease-Slime-topa.26
...RETRY-> Grease-Slime-topa.26
...FAILED-> Grease-Slime-topa.26Could not resolve: Grease-Slime [ Grease-Slime-topa.26] in /var/lib/jenkins/jobs/rpg/workspace/package-cache http://smalltalkhub.com/mc/Seaside/Grease11/main/
MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer:
MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: in Block: linearLoadPackageSpec: packageSpec gofer: gofer...
MetacelloPharo30Platform(MetacelloPlatform)>>do:displaying:
MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer:
MetacelloPackageSpec>>loadUsing:gofer:
MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: in Block: [ :pkg | pkg loadUsing: self gofer: gofer ]
OrderedCollection>>do:
MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories:
MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories: in Block: [ super linearLoadPackageSpecs: packageSpecs repos...etc...
BlockClosure>>ensure:
MetacelloLoaderPolicy>>pushLoadDirective:during:
MetacelloLoaderPolicy>>pushLinearLoadDirectivesDuring:for:
MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories:
MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>load
MetacelloMCVersionSpecLoader>>load
MetacelloMCVersion>>executeLoadFromArray:
MetacelloMCVersion>>fetchRequiredFromArray: in Block: [ :dict | ^ self executeLoadFromArray: anArray ]
MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [ ^ aBlock value: dict ]
BlockClosure>>on:do:
MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary:
MetacelloMCVersion>>fetchRequiredFromArray: in Block: [ ...
BlockClosure>>ensure:
MetacelloMCVersion>>fetchRequiredFromArray: in Block: [ ...
MetacelloPharo30Platform(MetacelloPlatform)>>do:displaying:
MetacelloMCVersion>>fetchRequiredFromArray:
MetacelloMCProjectSpec>>loadVersion: in Block: [ :dict | ...
MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [ ^ aBlock value: dict ]
BlockClosure>>on:do:
MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary:
MetacelloMCProjectSpec>>loadVersion:
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
Sending e-mails to: [hidden email]
Finished: FAILURE
honestly, we need to enhance the way we work with configurations… they are too weak.
(it is not a complain against anyone, just an observation that becomes obvious day by day :P)

On 05 Apr 2014, at 09:58, Johan Brichau <[hidden email]> wrote:

Hey Tobias,

Sorry that it took a while to pick up your fixes.

On 25 Mar 2014, at 14:09, Tobias Pape <[hidden email]> wrote:

Sadly builder-ci needs a small patch to cope for the fact that
the released 4.4 image still hast a redirect bug…

Is that the cause of the failures?
Because the Grease build on Travis shows the same failing tests.

It would be good if someone can fix them or tell me to mark some parts as non-loadable on Squeak (e.g. Slime in Squeak).
Otherwise, I will disable the automated builds as they are now always reporting a failure.

GREASE:
I have fixed the only one Test that failed for me in Squeak 4.4 and Squeak 4.5.
The fix is in Grease-Slime-topa.26.
SEASIDE:
Also here, only one test failed.
The fix is in Seaside-Core-topa.811.

thank you!
They are now in version 3.1.1 of Seaside and version 1.1.7 of Grease.

:) Ok Fixes are in the STHub repo

Should https://github.com/dalehenrich/builderCI/pull/59 be accepted, please
add Squeak-4.5 to the test matrix :)

I will pull Dale.
He should emerge from the trenches any moment now :-)

thanks a lot!

Johan
_______________________________________________
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

Johan Brichau-2

Re: grease and seaside on Squeak

Ok… it’s the configuration and it was my fault: a leading space in the package name.

<repeat 10x> I should refrain from changing the version methods by hand </repeat 10x>

And I also fixed the Jenkins build that was not loading the Slime part (hence no failure).

Johan

On 05 Apr 2014, at 15:10, Johan Brichau <[hidden email]> wrote:

I don’t think it has anything to do with the configuration itself.

I have the same load problem on Travis CI for Grease and not on the Jenkins CI

I’m also puzzled… but looking into it
On 05 Apr 2014, at 15:07, Esteban Lorenzano <[hidden email]> wrote:
well… now mongotalk configuration fails:
Fetched -> Magritte-Pharo3-Model-StephanEggermont.1 --- http://smalltalkhub.com/mc/Magritte/Magritte3/main/ --- http://smalltalkhub.com/mc/Magritte/Magritte3/main/
Project: MongoTalk stable [1.5.6]
Project: Grease stable [1.1.7]
...RETRY-> Grease-Slime-topa.26
...RETRY-> Grease-Slime-topa.26
...FAILED-> Grease-Slime-topa.26Could not resolve: Grease-Slime [ Grease-Slime-topa.26] in /var/lib/jenkins/jobs/rpg/workspace/package-cache http://smalltalkhub.com/mc/Seaside/Grease11/main/
MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer:
MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: in Block: linearLoadPackageSpec: packageSpec gofer: gofer...
MetacelloPharo30Platform(MetacelloPlatform)>>do:displaying:
MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer:
MetacelloPackageSpec>>loadUsing:gofer:
MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: in Block: [ :pkg | pkg loadUsing: self gofer: gofer ]
OrderedCollection>>do:
MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories:
MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories: in Block: [ super linearLoadPackageSpecs: packageSpecs repos...etc...
BlockClosure>>ensure:
MetacelloLoaderPolicy>>pushLoadDirective:during:
MetacelloLoaderPolicy>>pushLinearLoadDirectivesDuring:for:
MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories:
MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>load
MetacelloMCVersionSpecLoader>>load
MetacelloMCVersion>>executeLoadFromArray:
MetacelloMCVersion>>fetchRequiredFromArray: in Block: [ :dict | ^ self executeLoadFromArray: anArray ]
MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [ ^ aBlock value: dict ]
BlockClosure>>on:do:
MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary:
MetacelloMCVersion>>fetchRequiredFromArray: in Block: [ ...
BlockClosure>>ensure:
MetacelloMCVersion>>fetchRequiredFromArray: in Block: [ ...
MetacelloPharo30Platform(MetacelloPlatform)>>do:displaying:
MetacelloMCVersion>>fetchRequiredFromArray:
MetacelloMCProjectSpec>>loadVersion: in Block: [ :dict | ...
MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [ ^ aBlock value: dict ]
BlockClosure>>on:do:
MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary:
MetacelloMCProjectSpec>>loadVersion:
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
Sending e-mails to: [hidden email]
Finished: FAILURE
honestly, we need to enhance the way we work with configurations… they are too weak.
(it is not a complain against anyone, just an observation that becomes obvious day by day :P)

On 05 Apr 2014, at 09:58, Johan Brichau <[hidden email]> wrote:

Hey Tobias,

Sorry that it took a while to pick up your fixes.

On 25 Mar 2014, at 14:09, Tobias Pape <[hidden email]> wrote:

Sadly builder-ci needs a small patch to cope for the fact that
the released 4.4 image still hast a redirect bug…

Is that the cause of the failures?
Because the Grease build on Travis shows the same failing tests.

It would be good if someone can fix them or tell me to mark some parts as non-loadable on Squeak (e.g. Slime in Squeak).
Otherwise, I will disable the automated builds as they are now always reporting a failure.

GREASE:
I have fixed the only one Test that failed for me in Squeak 4.4 and Squeak 4.5.
The fix is in Grease-Slime-topa.26.
SEASIDE:
Also here, only one test failed.
The fix is in Seaside-Core-topa.811.

thank you!
They are now in version 3.1.1 of Seaside and version 1.1.7 of Grease.

:) Ok Fixes are in the STHub repo

Should https://github.com/dalehenrich/builderCI/pull/59 be accepted, please
add Squeak-4.5 to the test matrix :)

I will pull Dale.
He should emerge from the trenches any moment now :-)

thanks a lot!

Johan
_______________________________________________
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

Tobias Pape

Re: grease and seaside on Squeak

In reply to this post by Johan Brichau-2

On 05.04.2014, at 14:58, Johan Brichau <[hidden email]> wrote:

Hey Tobias,

Sorry that it took a while to pick up your fixes.

On 25 Mar 2014, at 14:09, Tobias Pape <[hidden email]> wrote:

Sadly builder-ci needs a small patch to cope for the fact that
the released 4.4 image still hast a redirect bug…

Is that the cause of the failures?
Because the Grease build on Travis shows the same failing tests.

I am really unsure there.
I tested locally and got (save the ones below) none of the travis failures.

It would be good if someone can fix them or tell me to mark some parts as non-loadable on Squeak (e.g. Slime in Squeak).
Otherwise, I will disable the automated builds as they are now always reporting a failure.

GREASE:
I have fixed the only one Test that failed for me in Squeak 4.4 and Squeak 4.5.
The fix is in Grease-Slime-topa.26.
SEASIDE:
Also here, only one test failed.
The fix is in Seaside-Core-topa.811.

thank you!
They are now in version 3.1.1 of Seaside and version 1.1.7 of Grease.

:) Ok Fixes are in the STHub repo

Should https://github.com/dalehenrich/builderCI/pull/59 be accepted, please
add Squeak-4.5 to the test matrix :)

I will pull Dale.
He should emerge from the trenches any moment now :-)

:D

Best
-Tobias

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

signature.asc (1K) Download Attachment

Johan Brichau-2

Re: grease and seaside on Squeak

On 05 Apr 2014, at 15:18, Tobias Pape <[hidden email]> wrote:

I am really unsure there.
I tested locally and got (save the ones below) none of the travis failures.

Hm… they might be related to the fact that the tests are running in a headless image.

I got the same issues with Pharo before… I will see if I can check that.

Johan

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

EstebanLM

Re: grease and seaside on Squeak

any update?

The package is not being found probably because repository/commit error?

A problem that maybe you do not have in local because of your package-cache has it.

Esteban

On 05 Apr 2014, at 10:21, Johan Brichau <[hidden email]> wrote:

On 05 Apr 2014, at 15:18, Tobias Pape <[hidden email]> wrote:

I am really unsure there.
I tested locally and got (save the ones below) none of the travis failures.

Hm… they might be related to the fact that the tests are running in a headless image.
I got the same issues with Pharo before… I will see if I can check that.

Johan
_______________________________________________
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

Johan Brichau-2

Re: grease and seaside on Squeak

I fixed this 5 minutes after responding.

It is fixed. Did you try to build?

Johan (sent from my mobile)

On 06 Apr 2014, at 16:43, Esteban Lorenzano <[hidden email]> wrote:

any update?
The package is not being found probably because repository/commit error?
A problem that maybe you do not have in local because of your package-cache has it.

Esteban

On 05 Apr 2014, at 10:21, Johan Brichau <[hidden email]> wrote:

On 05 Apr 2014, at 15:18, Tobias Pape <[hidden email]> wrote:

I am really unsure there.
I tested locally and got (save the ones below) none of the travis failures.

Hm… they might be related to the fact that the tests are running in a headless image.
I got the same issues with Pharo before… I will see if I can check that.

Johan
_______________________________________________
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