chore: move cli/tests/ -> tests/ (#22369)

This looks like a massive PR, but it's only a move from cli/tests ->
tests, and updates of relative paths for files.

This is the first step towards aggregate all of the integration test
files under tests/, which will lead to a set of integration tests that
can run without the CLI binary being built.

While we could leave these tests under `cli`, it would require us to
keep a more complex directory structure for the various test runners. In
addition, we have a lot of complexity to ignore various test files in
the `cli` project itself (cargo publish exclusion rules, autotests =
false, etc).

And finally, the `tests/` folder will eventually house the `test_ffi`,
`test_napi` and other testing code, reducing the size of the root repo
directory.

For easier review, the extremely large and noisy "move" is in the first
commit (with no changes -- just a move), while the remainder of the
changes to actual files is in the second commit.

1 files changed, 65 insertions, 0 deletions

diff --git a/tests/node_compat/test/parallel/test-child-process-spawnsync-maxbuf.js b/tests/node_compat/test/parallel/test-child-process-spawnsync-maxbuf.js
new file mode 100644
index 000000000..62b71c729
--- /dev/null
+++ b/tests/node_compat/test/parallel/test-child-process-spawnsync-maxbuf.js
@@ -0,0 +1,65 @@
+// deno-fmt-ignore-file
+// deno-lint-ignore-file
+
+// Copyright Joyent and Node contributors. All rights reserved. MIT license.
+// Taken from Node 18.12.1
+// This file is automatically generated by `tools/node_compat/setup.ts`. Do not modify this file manually.
+
+'use strict';
+require('../common');
+
+// This test checks that the maxBuffer option for child_process.spawnSync()
+// works as expected.
+
+const assert = require('assert');
+const spawnSync = require('child_process').spawnSync;
+const { getSystemErrorName } = require('util');
+const msgOut = 'this is stdout';
+const msgOutBuf = Buffer.from(`${msgOut}\n`);
+
+const args = [
+  '-e',
+  `console.log("${msgOut}");`,
+];
+
+// Verify that an error is returned if maxBuffer is surpassed.
+{
+  const ret = spawnSync(process.execPath, args, { maxBuffer: 1 });
+
+  assert.ok(ret.error, 'maxBuffer should error');
+  assert.strictEqual(ret.error.code, 'ENOBUFS');
+  assert.strictEqual(getSystemErrorName(ret.error.errno), 'ENOBUFS');
+  // We can have buffers larger than maxBuffer because underneath we alloc 64k
+  // that matches our read sizes.
+  assert.deepStrictEqual(ret.stdout, msgOutBuf);
+}
+
+// Verify that a maxBuffer size of Infinity works.
+{
+  const ret = spawnSync(process.execPath, args, { maxBuffer: Infinity });
+
+  assert.ifError(ret.error);
+  assert.deepStrictEqual(ret.stdout, msgOutBuf);
+}
+
+// Default maxBuffer size is 1024 * 1024.
+{
+  const args = ['-e', "console.log('a'.repeat(1024 * 1024))"];
+  const ret = spawnSync(process.execPath, args);
+
+  assert.ok(ret.error, 'maxBuffer should error');
+  assert.strictEqual(ret.error.code, 'ENOBUFS');
+  assert.strictEqual(getSystemErrorName(ret.error.errno), 'ENOBUFS');
+}
+
+// Default maxBuffer size is 1024 * 1024.
+{
+  const args = ['-e', "console.log('a'.repeat(1024 * 1024 - 1))"];
+  const ret = spawnSync(process.execPath, args);
+
+  assert.ifError(ret.error);
+  assert.deepStrictEqual(
+    ret.stdout.toString().trim(),
+    'a'.repeat(1024 * 1024 - 1)
+  );
+}