CI failure (socket.send)

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

CI failure (socket.send)

Darjus Loktevic
Hey Nick,

Looks like your socket.send change broke the regregression tests. It seems that something is leaking/isn't being cleaned up as expected if the address is still in use. Would appreciate you taking a look at this.

https://circleci.com/gh/jythontools/jython/tree/master

Cheers,
Darjus

------------------------------------------------------------------------------

_______________________________________________
Jython-dev mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jython-dev
Reply | Threaded
Open this post in threaded view
|

Re: CI failure (socket.send)

Jim Baker-2
Darjus,

Thanks for taking a look at this. I believe the problem has been surfaced by the upgrade to Netty 4.1, which is giving us more feedback on a resource leak in test_socket. It's not the send fix itself.

The solution to any Netty problem is to add another listener :), and joking aside, that should likely be the case here.

- Jim

On Fri, Aug 19, 2016 at 4:16 AM, Darjus Loktevic <[hidden email]> wrote:
Hey Nick,

Looks like your socket.send change broke the regregression tests. It seems that something is leaking/isn't being cleaned up as expected if the address is still in use. Would appreciate you taking a look at this.

https://circleci.com/gh/jythontools/jython/tree/master

Cheers,
Darjus

------------------------------------------------------------------------------

_______________________________________________
Jython-dev mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jython-dev



------------------------------------------------------------------------------

_______________________________________________
Jython-dev mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jython-dev