2011/9/28 Bill Barker <[email protected]>:
> To whom it may engage...
>
> This is an automated request, but not an unsolicited one. For
> more information please visit http://gump.apache.org/nagged.html,
> and/or contact the folk at [email protected].
>
> Project tomcat-tc7.0.x-test has an issue affecting its community integration.
> This issue affects 1 projects,
> and has been outstanding for 8 runs.
> The current state of this project is 'Failed', with reason 'Build Failed'.
> For reference only, the following projects are affected by this:
> - tomcat-tc7.0.x-test : Tomcat 7.x, a web server implementing Java
> Servlet 3.0,
> ...
>
>
> Full details are available at:
>
> http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-test/index.html
Test org.apache.catalina.tribes.group.TestGroupChannelMemberArrival FAILED
================
TEST-org.apache.catalina.tribes.group.TestGroupChannelMemberArrival.BIO.txt
Testcase: testMemberArrival took 4.38 sec
FAILED
Checking member arrival length expected:<9> but was:<11>
junit.framework.AssertionFailedError: Checking member arrival length
expected:<9> but was:<11>
at
org.apache.catalina.tribes.group.TestGroupChannelMemberArrival.testMemberArrival(TestGroupChannelMemberArrival.java:77)
================
The same failure as was observed by Gump in trunk yesterday.
Again BIO fails, but NIO runs OK.
> Checking member arrival length expected:<9> but was:<11>
In failed trunk test it was
> Checking member arrival length expected:<9> but was:<19>
So, it received more data than were expected?
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
