Multiple persistent child-process-related test failures on Windows when running as a Service #19
Description
This sucks because I want to run the Jenkins client as a service but when I do I get 4 persistent failures:
=== release test-child-process-double-pipe === Path: simple/test-child-process-double-pipe grep stdin write 18 echo exit grep stdin write 7 Command: c:\workspace\iojs+v0.12+multi\nodes\node-forward-rackspace-iad-win2012r2-msvs2013\Release\node.exe c:\workspace\iojs+v0.12+multi\nodes\node-forward-rackspace-iad-win2012r2-msvs2013\test\simple\test-child-process-double-pipe.js --- TIMEOUT --- === release test-child-process-exit-code === Path: simple/test-child-process-exit-code Command: c:\workspace\iojs+v0.12+multi\nodes\node-forward-rackspace-iad-win2012r2-msvs2013\Release\node.exe c:\workspace\iojs+v0.12+multi\nodes\node-forward-rackspace-iad-win2012r2-msvs2013\test\simple\test-child-process-exit-code.js --- TIMEOUT --- === release test-child-process-spawnsync === Path: simple/test-child-process-spawnsync sleep started sleep exited [ 50, 509779200 ] assert.js:100 throw new assert.AssertionError({ ^ AssertionError: sleep should not take longer or less than 1 second at Object.<anonymous> (c:\workspace\iojs+v0.12+multi\nodes\node-forward-rackspace-iad-win2012r2-msvs2013\test\simple\test-child-process-spawnsync.js:44:8) at Module._compile (module.js:462:26) at Object.Module._extensions..js (module.js:480:10) at Module.load (module.js:357:32) at Function.Module._load (module.js:312:12) at Function.Module.runMain (module.js:503:10) at startup (node.js:135:16) at node.js:866:3 Command: c:\workspace\iojs+v0.12+multi\nodes\node-forward-rackspace-iad-win2012r2-msvs2013\Release\node.exe c:\workspace\iojs+v0.12+multi\nodes\node-forward-rackspace-iad-win2012r2-msvs2013\test\simple\test-child-process-spawnsync.js === release test-child-process-spawnsync-input === Path: simple/test-child-process-spawnsync-input Command: c:\workspace\iojs+v0.12+multi\nodes\node-forward-rackspace-iad-win2012r2-msvs2013\Release\node.exe c:\workspace\iojs+v0.12+multi\nodes\node-forward-rackspace-iad-win2012r2-msvs2013\test\simple\test-child-process-spawnsync-input.js --- TIMEOUT --- Compare Jenkins running as a service to running manually from cmd.
I'm using nssm with fairly standard options, running Jenkins from a 1-line .bat file and redirecting stdout and stderr to files.
Anybody have any clues about this? The only service-related problems I'm aware of are obvious ones like permissions problems. The test-child-process-spawnsync failure is particularly interesting. The sleep 1 appears to be taking 50 seconds (look at builds 47 and 48 and you'll see the same number!)--what's the significance of 50 seconds? A longer-than-expected execution might explain all of these errors but it's still not acceptable since running Node from a service on Windows is fairly common for production deployments.