Makes me want to go zap a long standing ocassional test fail I got. It seems that sometimes a netty hashwheeltimer is executing a timeout you add immediately,

Makes me want to go zap a long standing ocassional test fail I got. It seems that sometimes a netty hashwheeltimer is executing a timeout you add immediately, instead of after 2 seconds. And its the simplest code, and the 2 seconds we are trying to set are literals, so it ready surprises me. Find it hard to imagine a bug in netty and it always affects the same test, despite all our requests setting an aggressive 2 second timeout...