test-child-process-emfile.js fails on freebsd

[evanlucas]

I haven't had a chance to look into specifics, but just wanted to note it.

Here is the error:

not ok 878 test-child-process-emfile.js
#
#assert.js:89
#  throw new assert.AssertionError({
#  ^
#AssertionError: 0 undefined null
#    at emitTwo (events.js:87:13)
#    at ChildProcess.emit (events.js:172:7)
#    at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)

[evanlucas]

Here is a run where it failed. https://ci.nodejs.org/job/node-test-commit-other/823/nodes=freebsd101-64/console

[rvagg]

mm, I noticed this the other day, /cc @nodejs/platform-freebsd

[Trott]

#3335 isn't a fix but may at least help point someone in the right direction.

[jbergstroem]

Just saw it in the 32-bit environment with the updated error message:

not ok 898 test-child-process-emfile.js
#
#assert.js:89
#  throw new assert.AssertionError({
#  ^
#AssertionError: "exit" should not be emitted (the process never spawned!)
#    at ChildProcess.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd101-32/test/sequential/test-child-process-emfile.js:32:10)
#    at emitTwo (events.js:87:13)
#    at ChildProcess.emit (events.js:172:7)
#    at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)

[Trott]

On FreeBSD, I haven't noticed this test failing (or any tests, for that matter, hooray!). I suspect this was fixed by d89bc7b. Closing.

[kapouer]

For what it's worth, on debian/kfreebsd the test has not been failing either.

[jbergstroem]

(same on gentoo/freebsd)