From f5e46c9bf2f50d66a953fa133161fc829cecff06 Mon Sep 17 00:00:00 2001 From: Matt Mastracci Date: Sat, 10 Feb 2024 13:22:13 -0700 Subject: 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. --- cli/tests/node_compat/test/common/child_process.js | 56 ---------------------- 1 file changed, 56 deletions(-) delete mode 100644 cli/tests/node_compat/test/common/child_process.js (limited to 'cli/tests/node_compat/test/common/child_process.js') diff --git a/cli/tests/node_compat/test/common/child_process.js b/cli/tests/node_compat/test/common/child_process.js deleted file mode 100644 index b860d7697..000000000 --- a/cli/tests/node_compat/test/common/child_process.js +++ /dev/null @@ -1,56 +0,0 @@ -// 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'; - -const assert = require('assert'); -const common = require('./'); - -// Workaround for Windows Server 2008R2 -// When CMD is used to launch a process and CMD is killed too quickly, the -// process can stay behind running in suspended state, never completing. -function cleanupStaleProcess(filename) { - if (!common.isWindows) { - return; - } - process.once('beforeExit', () => { - const basename = filename.replace(/.*[/\\]/g, ''); - try { - require('child_process') - .execFileSync(`${process.env.SystemRoot}\\System32\\wbem\\WMIC.exe`, [ - 'process', - 'where', - `commandline like '%${basename}%child'`, - 'delete', - '/nointeractive', - ]); - } catch { - // Ignore failures, there might not be any stale process to clean up. - } - }); -} - -// This should keep the child process running long enough to expire -// the timeout. -const kExpiringChildRunTime = common.platformTimeout(20 * 1000); -const kExpiringParentTimer = 1; -assert(kExpiringChildRunTime > kExpiringParentTimer); - -function logAfterTime(time) { - setTimeout(() => { - // The following console statements are part of the test. - console.log('child stdout'); - console.error('child stderr'); - }, time); -} - -module.exports = { - cleanupStaleProcess, - logAfterTime, - kExpiringChildRunTime, - kExpiringParentTimer, -}; -- cgit v1.2.3