Skip to content
Browse files

test: set umask for tests

#25213 proposes setting umask in the
Python test runner to avoid spurious test failures when running from a
shell with a restrictive umask. This is a good idea, but will only fix
the issue for tests run with the Python runner. Set it in
`common/index.js` as well so that it fixes it even when tests are run
directly with a `node` binary, bypassing the Python test runner.

PR-URL: #25229
Reviewed-By: Colin Ihrig <>
Reviewed-By: Luigi Pinca <>
Reviewed-By: James M Snell <>
  • Loading branch information
Trott committed Jan 10, 2019
1 parent 8c0290e commit a53518d027c7ab72e66100fa32a1d5a9898ca6d0
Showing with 8 additions and 0 deletions.
  1. +8 −0 test/common/index.js
@@ -34,6 +34,14 @@ const {
} = process.binding('config');

// Some tests assume a umask of 0o022 so set that up front. Tests that need a
// different umask will set it themselves.
// process.umask() is not available in workers so we need to check for its
// existence.
if (process.umask)

const noop = () => {};

const hasCrypto = Boolean(process.versions.openssl);

0 comments on commit a53518d

Please sign in to comment.