(05:54:09) dmlloyd: when running with JDWP enabled on the client or server, I occasionally get bind exceptions due to address in use
(05:54:25) dmlloyd: which means that tests are running into each other without waiting for termination of the previous one
(05:54:35) dmlloyd: which may also be causing other issues
(05:56:04) ozizka: dmlloyd: Yes, lbarrerio observed similar problem too,
(05:56:47) ozizka: And that's arq's issue too - there's no way to get around this currently AFAIK. Or is there?
(05:57:05) ozizka: Perhaps "manually" wait in @AfterClass or such
(05:57:07) dmlloyd: yeah, it can wait for the child process to terminate
(05:57:07) ozizka: which is ugly
(05:57:14) dmlloyd: I mean arq should

(05:59:17) ozizka: dmlloyd: Do you have it somewhere on hudson?
(05:59:24) ozizka: dmlloyd: It never happened to me actually
(05:59:49) ozizka: Send me a log if you have one handy
(06:01:35) dmlloyd: ozizka: no, try running with this command though:

mvn -DallTests install -Djpda -Dsurefire.jpda.args=-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n \
                   -Dmaven.surefire.debug="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005"

(06:13:56) ozizka: dmlloyd: That's on linux?
(06:14:03) dmlloyd: yes