[Seaside-dev] Seaside 3.0.5+ and swazoo

[Lukas Renggli]

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 <dhenrich at vmware.com> 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
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>



-- 
Lukas Renggli
www.lukas-renggli.ch