René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Multiple persistent child-process-related test failures on Windows when running as a Service","articleBody":"\u003cimg src=\"https://imgflip.com/readImage?iid=412211\" height=100>\n\nThis sucks because I want to run the Jenkins client as a service but when I do I get 4 persistent failures:\n\n```\n=== release test-child-process-double-pipe ===\nPath: simple/test-child-process-double-pipe\ngrep stdin write 18\necho exit\ngrep stdin write 7\nCommand: 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\n--- TIMEOUT ---\n```\n\n```\n=== release test-child-process-exit-code ===\nPath: simple/test-child-process-exit-code\nCommand: 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\n--- TIMEOUT ---\n```\n\n```\n=== release test-child-process-spawnsync ===\nPath: simple/test-child-process-spawnsync\nsleep started\nsleep exited [ 50, 509779200 ]\nassert.js:100\n  throw new assert.AssertionError({\n        ^\nAssertionError: sleep should not take longer or less than 1 second\n    at Object.\u003canonymous> (c:\\workspace\\iojs+v0.12+multi\\nodes\\node-forward-rackspace-iad-win2012r2-msvs2013\\test\\simple\\test-child-process-spawnsync.js:44:8)\n    at Module._compile (module.js:462:26)\n    at Object.Module._extensions..js (module.js:480:10)\n    at Module.load (module.js:357:32)\n    at Function.Module._load (module.js:312:12)\n    at Function.Module.runMain (module.js:503:10)\n    at startup (node.js:135:16)\n    at node.js:866:3\nCommand: 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\n```\n\n```\n=== release test-child-process-spawnsync-input ===\nPath: simple/test-child-process-spawnsync-input\nCommand: 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\n--- TIMEOUT ---\n```\n\nCompare Jenkins [running as a service](https://jenkins-node-forward.nodesource.com/job/iojs+v0.12+multi/nodes=node-forward-rackspace-iad-win2012r2-msvs2013/49/console) to [running manually from cmd](https://jenkins-node-forward.nodesource.com/job/iojs+v0.12+multi/nodes=node-forward-rackspace-iad-win2012r2-msvs2013/50/console).\n\nI'm using [nssm](http://nssm.cc/) with fairly standard options, running Jenkins from a 1-line .bat file and redirecting stdout and stderr to files.\n\nAnybody 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.\n","author":{"url":"https://github.com/rvagg","@type":"Person","name":"rvagg"},"datePublished":"2014-11-30T04:26:45Z","url":"https://github.com/nodejs/node/issues/19"}