test: allow ENOENT in test-worker-init-failure

PR-URL: #34769 Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Denys Otrishko <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Ricky Zhou <[email protected]>
nodejs · Sep 22, 2020 · 5352cde · 5352cde
1 parent 238d01f
commit 5352cde
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/test/parallel/test-worker-init-failure.js b/test/parallel/test-worker-init-failure.js
@@ -30,14 +30,14 @@ if (process.argv[2] === 'child') {
     });
 
     // We want to test that if there is an error in a constrained running
-    // environment, it will be one of `ENFILE`, `EMFILE`, or
+    // environment, it will be one of `ENFILE`, `EMFILE`, 'ENOENT', or
     // `ERR_WORKER_INIT_FAILED`.
-    const allowableCodes = ['ERR_WORKER_INIT_FAILED', 'EMFILE', 'ENFILE'];
+    const expected = ['ERR_WORKER_INIT_FAILED', 'EMFILE', 'ENFILE', 'ENOENT'];
 
     // `common.mustCall*` cannot be used here as in some environments
     // (i.e. single cpu) `ulimit` may not lead to such an error.
     worker.on('error', (e) => {
-      assert.ok(allowableCodes.includes(e.code), `${e.code} not expected`);
+      assert.ok(expected.includes(e.code), `${e.code} not expected`);
     });
   }