963b24e9a6
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>
20 lines
631 B
JavaScript
20 lines
631 B
JavaScript
// Flags: --permission --allow-fs-read=* --allow-child-process
|
|
|
|
'use strict';
|
|
|
|
const { skip, isWindows, isIBMi } = require('../common');
|
|
const { deepStrictEqual } = 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']);
|
|
} else {
|
|
process.execve(process.execPath, [process.execPath, __filename, 'replaced'], process.env);
|
|
}
|