Seaside 3.0.5+ and swazoo

Lukas,

I was wondering how come your Jenkins server was able to ship a clean version of swazoo and seaside 3.0.5+, since nearly every platform that I run the Seaside tests on, I get a bunch of errors and failures in the swazoo tests ...

So, I downloaded the swazoo artifact and the same set of tests fail ... so I guess the tests aren't run when you build the swazoo images? This is a bit distrubing to me...According to the giant graph all tests are green...

I complained about the failing swazoo tests in 3.0.5 when I first ran into the problems, but noone seems to care ... I don't think that this is a good thing...

Perhaps Swazoo should be made optional like Zinc is?

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

Hi Dale,

I've never used Swazoo, but it basically seems to work. I recently
suggested to remove it from the builds, but people said I should leave
it alone.

The test on my Jenkins are only run on the Seaside packages. For Zinc
I have a separate build that tests it, but for Kom and Swazoo I am not
aware of any tests.

I do not understand what you mean by "made optional"?

Lukas

On 9 September 2011 20: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

In the Seaside30 configurqation swazoo is loaded by default ... you have to go out of your way to not have swazoo loaded ...

Because of the stability issues for Zinc the zinc adaptor is not loaded by default in the 3.0.6 configuration and we could do the same thing with swazoo ...

I agree that swazoo appears to work fine, but if a regression occurs, noone will know because there is already a set of failing tests ... I would have hoped that the tests were run for the packages that are provided by the seaside ci server ... that is my expectation at least ... if the tests are green on the ci server why should i think that I need to run the tests ... again.

Failing tests in a ci server provides motivation for the maintainers to fix the problems, otherwise the problems are just masked and in the end the users are the ones who have deal with a faulty product ...

I don't like the fact that when one loads the default Seaside configuration and runs tests that the tests are red not green... I will hold off on releasing 3.0.6 until I hear a definitive answer.

Dale

----- Original Message -----
| From: "Lukas Renggli" <[hidden email]>
| To: "Seaside - developer list" <[hidden email]>
| Sent: Friday, September 9, 2011 11:52:49 AM
| Subject: Re: [Seaside-dev] Seaside 3.0.5+ and swazoo
|
| Hi Dale,
|
| I've never used Swazoo, but it basically seems to work. I recently
| suggested to remove it from the builds, but people said I should
| leave
| it alone.
|
| The test on my Jenkins are only run on the Seaside packages. For Zinc
| I have a separate build that tests it, but for Kom and Swazoo I am
| not
| aware of any tests.
|
| I do not understand what you mean by "made optional"?
|
| Lukas
|
| On 9 September 2011 20:48, Dale Henrichs <[hidden email]> wrote:
| > Lukas,
| >
| > I was wondering how come your Jenkins server was able to ship a
| > clean version of swazoo and seaside 3.0.5+, since nearly every
| > platform that I run the Seaside tests on, I get a bunch of errors
| > and failures in the swazoo tests ...
| >
| > So, I downloaded the swazoo artifact and the same set of tests fail
| > ... so I guess the tests aren't run when you build the swazoo
| > images? This is a bit distrubing to me...According to the giant
| > graph all tests are green...
| >
| > I complained about the failing swazoo tests in 3.0.5 when I first
| > ran into the problems, but noone seems to care ... I don't think
| > that this is a good thing...
| >
| > Perhaps Swazoo should be made optional like Zinc is?
| >
| > 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

On 9 September 2011 22:17, Dale Henrichs <[hidden email]> wrote:
> In the Seaside30 configurqation swazoo is loaded by default ... you have to go out of your way to not have swazoo loaded ...

This is strange that Swazoo is loaded by default, because we never
advertised to use it. It was even hosted in a different repository
because its license sucks.

> Because of the stability issues for Zinc the zinc adaptor is not loaded by default in the 3.0.6 configuration and we could do the same thing with swazoo ...

I always thought that Kom was the default. Zinc seems to be stable
again with the latest changes.

> Failing tests in a ci server provides motivation for the maintainers to fix the problems, otherwise the problems are just masked and in the end the users are the ones who have deal with a faulty product ...

I don't think that actually somebody is actually maintaining Swazoo,
at least I don't know that anybody touched it in the past couple of
years.

Lukas

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

On GemStone Swazoo was the only alternative to using FastCGI, so it has seen a fair amount of use over the years, but Zinc has been partially ported to GemStone and is picking up more users. There are some outstanding issues with Zinc on GemStone, but more cosmetic issues (I think) than real problems and I expect to address those problems relatively soon.

It is relatively easy to control what gets loaded by default in Metacello and that's all we're talking about...if someone wants to use Swazoo it is easy to load...

Dale

----- Original Message -----
| From: "Lukas Renggli" <[hidden email]>
| To: "Seaside - developer list" <[hidden email]>
| Sent: Friday, September 9, 2011 1:49:03 PM
| Subject: Re: [Seaside-dev] Seaside 3.0.5+ and swazoo
|
| On 9 September 2011 22:17, Dale Henrichs <[hidden email]> wrote:
| > In the Seaside30 configurqation swazoo is loaded by default ... you
| > have to go out of your way to not have swazoo loaded ...
|
| This is strange that Swazoo is loaded by default, because we never
| advertised to use it. It was even hosted in a different repository
| because its license sucks.
|
| > Because of the stability issues for Zinc the zinc adaptor is not
| > loaded by default in the 3.0.6 configuration and we could do the
| > same thing with swazoo ...
|
| I always thought that Kom was the default. Zinc seems to be stable
| again with the latest changes.
|
| > Failing tests in a ci server provides motivation for the
| > maintainers to fix the problems, otherwise the problems are just
| > masked and in the end the users are the ones who have deal with a
| > faulty product ...
|
| I don't think that actually somebody is actually maintaining Swazoo,
| at least I don't know that anybody touched it in the past couple of
| years.
|
| Lukas
|
| --
| 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