'test that connection close does not mean disconnect' fails

[EugenDueck]

I'm 'make test'ing a fresh socket.io checkout from HEAD, node 0.8.4, redis 2.4.15.

There are only 2 tests that fail:

• 'test listening with no arguments listens on 80' - No surprise here, I guess, because that port is used by another application, so I commented out that one

• 'test that connection close does not mean disconnect' fails with the following error:

  uncaught undefined: AssertionError: expected true to be false at Object.false (socket.io/node_modules/should/lib/should.js:270:10) at Object.module.exports.test that connection close does not mean disconnect as _onTimeout at Timer.list.ontimeout (timers.js:101:19)

  uncaught undefined: Error: 'test that connection close does not mean disconnect' timed out at Object._onTimeout (socket.io/node_modules/expresso/bin/expresso:943:23) at Timer.list.ontimeout (timers.js:101:19)

Is that a problem on my end or is that test broken?

[EugenDueck]

I could reproduce this on another machine, versions of socket.io, node and redis are the same, as is the os (debian testing, fairly up-to-date)