On Wed, Apr 25, 2018 at 8:15 PM, Piotr Kliczewski <pkliczew@redhat.com> wrote:
śr., 25 kwi 2018, 19:07 użytkownik Martin Perina <mperina@redhat.com> napisał:
Ravi/Piotr, so what's the connection between non-blocking threads, jsonrpc-java connection closing and failing this network test? Does it mean that non-blocking threads change just revealed the jsonrpc-java issue which we haven't noticed before? And did the test really works with code prior to non-blocking threads changes and we are missing something else?
I think that the test found something not related to non-blocking threads. This behavior was in the code since the beginning.
ipv6 migration test is quite old too commit dea714ba85d5c0b77859f504bb80840275277e68 Author: Ondřej Svoboda <osvoboda@redhat.com> Date: Tue Mar 14 11:21:53 2017 +0100 Re-enable IPv6 migration. and vdsm_recovery test is not so young: commit 315cc100bc9bc0d81c01728a3576a10bfa576ac4 Author: Milan Zamazal <mzamazal@redhat.com> Date: Fri Sep 23 10:08:47 2016 +0200 vdsm_recovery test