node/test/parallel/test-process-execve.js
Abdirahim Musse 963b24e9a6
process: disable building execve on IBM i
The `execve` syscall does exist on IBM i but
it has caveats that make it not usable in Node.js context.

These changes disable building with `execve` like Windows does.

PR-URL: https://github.com/nodejs/node/pull/57883
Reviewed-By: Michael Dawson <midawson@redhat.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Paolo Insogna <paolo@cowtech.it>
2025-04-18 11:07:51 +00:00

28 lines
905 B
JavaScript

'use strict';
const { isWindows, isIBMi, skip } = require('../common');
const { deepStrictEqual, fail, strictEqual } = require('assert');
const { isMainThread } = require('worker_threads');
if (!isMainThread) {
skip('process.execve is not available in Workers');
} else if (isWindows || isIBMi) {
skip('process.execve is not available in Windows or IBM i');
}
if (process.argv[2] === 'replaced') {
deepStrictEqual(process.argv, [process.execPath, __filename, 'replaced']);
strictEqual(process.env.CWD, process.cwd());
strictEqual(process.env.EXECVE_A, 'FIRST');
strictEqual(process.env.EXECVE_B, 'SECOND');
} else {
process.execve(
process.execPath,
[process.execPath, __filename, 'replaced'],
{ ...process.env, EXECVE_A: 'FIRST', EXECVE_B: 'SECOND', CWD: process.cwd() }
);
// If process.execve succeed, this should never be executed.
fail('process.execve failed');
}