From 9cfa4fd7d6ce7e6fa3c0b7edcf60088adaf82bda Mon Sep 17 00:00:00 2001 From: Ryan Dahl Date: Sat, 7 Nov 2009 15:08:46 +0100 Subject: [PATCH] Output stderr from test-remote-module-loading.js There is a small problem with test-remote-module-loading.js. When it starts a child "node", the child uses the default require.paths instead unshifting the build lib/ --- test/mjsunit/test-remote-module-loading.js | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/test/mjsunit/test-remote-module-loading.js b/test/mjsunit/test-remote-module-loading.js index 7baecff..7c6b0f5 100644 --- a/test/mjsunit/test-remote-module-loading.js +++ b/test/mjsunit/test-remote-module-loading.js @@ -29,10 +29,10 @@ sys modulesLoaded++; server.close(); }) - .addErrback(function() { - assertUnreachable('node binary could not load module from url'); + .addErrback(function(code, stdout, stderr) { + assertUnreachable('node binary could not load module from url: ' + stderr); }); process.addListener('exit', function() { assertEquals(2, modulesLoaded); -}); \ No newline at end of file +}); -- 2.7.4