test: root can connect to chmod'd pipes

diff --git a/test/simple/test-net-pipe-connect-errors.js b/test/simple/test-net-pipe-connect-errors.js
index 627698d947b89c2a06a9bc9001630f350097ecbc..8200a16cf0baa2e77b5a10a224acce1f87f860b6 100644 (file)
--- a/test/simple/test-net-pipe-connect-errors.js
+++ b/test/simple/test-net-pipe-connect-errors.js
@@ -53,8 +53,8 @@ noEntSocketClient.on('error', function(err) {
 });
 
 
-// On Windows a chmod has no effect on named pipes
-if (process.platform !== 'win32') {
+// On Windows or when running as root, a chmod has no effect on named pipes
+if (process.platform !== 'win32' && process.getuid() !== 0) {
   // Trying to connect to a socket one has no access to should result in EACCES
   var accessServer = net.createServer(function() {
     assert.ok(false);
@@ -79,7 +79,7 @@ if (process.platform !== 'win32') {
 process.on('exit', function() {
   assert.ok(notSocketErrorFired);
   assert.ok(noEntErrorFired);
-  if (process.platform !== 'win32') {
+  if (process.platform !== 'win32' && process.getuid() !== 0) {
     assert.ok(accessErrorFired);
   }
 });