test-cluster-disconnect.js AssertionError: 1 == 2 on busy arm host

[kapouer]

Hi,
anyone seen this ?

not ok 79 test-cluster-disconnect.js
#
#assert.js:89
#  throw new assert.AssertionError({
#  ^
#AssertionError: 1 == 2
#    at process.<anonymous> (/«PKGBUILDDIR»/test/parallel/test-cluster-disconnect.js:97:12)
#    at process.g (events.js:260:16)
#    at emitOne (events.js:82:20)
#    at process.emit (events.js:169:7)
  ---
  duration_ms: 2.423

from
https://buildd.debian.org/status/fetch.php?pkg=nodejs&arch=armel&ver=4.2.1~dfsg-1&stamp=1444780989

I wonder if it's a flaky test or a failure.

[Trott]

The test runs without issue on the "stress test" (run a test over and over again) job on the Node Jenkins server: https://ci.nodejs.org/job/node-stress-single-test/36/nodes=armv7-wheezy/console Of course, that's probably not a busy arm host...

The one that is flaky on the Node CI server is test-http-client-timeout-with-data.js:

not ok 50 test-http-client-timeout-with-data.js
# 
# assert.js:90
#   throw new assert.AssertionError({
#   ^
# AssertionError: 0 == 1
#     at process.<anonymous> (/home/iojs/build/workspace/node-test-binary-arm/RUN_SUBSET/addons/nodes/pi1-raspbian-wheezy/test/parallel/test-http-client-timeout-with-data.js:10:10)
#     at emitOne (events.js:83:20)
#     at process.emit (events.js:170:7)

[Trott]

@kapouer Still seeing this? Or was it a happened-once-and-never-came-up-again thing?

FWIW, something recently landed that might be relevant:

• 57a51a0

And some possibly relevant open PRs that might affect this behavior:

• cluster: fix race condition setting suicide prop #4349
• cluster: ignore queryServer msgs on disconnection #4465

[Trott]

Closing due to inactivity and lack of reproducibility (at least by me!). Please, by all means, absolutely re-open if this still requires investigation.