Hi Jason,

I think you are talking about another Test-Failure we have:

io.undertow.websockets.protocol.version07.WebSocket07ServerTest.testPing

http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/Undertow/io.undertow$undertow-websockets/85/testReport/junit/io.undertow.websockets.protocol.version07/WebSocket07ServerTest/testPing/

This is the one that is a cause of a race in Netty. I opened a pull-req to disable it until a new Netty version is released, which will most likely happen mid. next week.

https://github.com/undertow-io/undertow/pull/25


---
Norman Maurer
nmaurer@redhat.com



Am 10.01.2013 um 16:47 schrieb Jason Greene <jason.greene@redhat.com>:

As an update. The test was an interop test using netty as a client for an older web sockets protocol (07). It turns out there is a race condition in betty which breaks the test.

On Jan 10, 2013, at 8:21 AM, Norman Maurer <nmaurer@redhat.com> wrote:

Hey,

I just talked with Stuart about this one as it sometimes pass and sometimes fails here. He said he will most likely disable the Test for now as he suspect the Test is not correct.

So I guess just ignore it for now.

---
Norman Maurer
nmaurer@redhat.com



Am 10.01.2013 um 14:39 schrieb jean-frederic clere <jfclere@gmail.com>:

Hi,

I have the following error:
+++
Results :

Failed tests:   testWriteTimeout(io.undertow.test.WriteTimeoutTestCase):
Write did not time out

Tests run: 66, Failures: 1, Errors: 0, Skipped: 3
+++

Any hints?

Cheers

Jean-Frederic
_______________________________________________
undertow-dev mailing list
undertow-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/undertow-dev


_______________________________________________
undertow-dev mailing list
undertow-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/undertow-dev