From f5e46c9bf2f50d66a953fa133161fc829cecff06 Mon Sep 17 00:00:00 2001
From: Matt Mastracci <matthew@mastracci.com>
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.
---
 .../test-stream-pipeline-queued-end-in-destroy.js  | 46 ----------------------
 1 file changed, 46 deletions(-)
 delete mode 100644 cli/tests/node_compat/test/parallel/test-stream-pipeline-queued-end-in-destroy.js

(limited to 'cli/tests/node_compat/test/parallel/test-stream-pipeline-queued-end-in-destroy.js')

diff --git a/cli/tests/node_compat/test/parallel/test-stream-pipeline-queued-end-in-destroy.js b/cli/tests/node_compat/test/parallel/test-stream-pipeline-queued-end-in-destroy.js
deleted file mode 100644
index e785a0008..000000000
--- a/cli/tests/node_compat/test/parallel/test-stream-pipeline-queued-end-in-destroy.js
+++ /dev/null
@@ -1,46 +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 common = require('../common');
-const assert = require('assert');
-const { Readable, Duplex, pipeline } = require('stream');
-
-// Test that the callback for pipeline() is called even when the ._destroy()
-// method of the stream places an .end() request to itself that does not
-// get processed before the destruction of the stream (i.e. the 'close' event).
-// Refs: https://github.com/nodejs/node/issues/24456
-
-const readable = new Readable({
-  read: common.mustCall()
-});
-
-const duplex = new Duplex({
-  write(chunk, enc, cb) {
-    // Simulate messages queueing up.
-  },
-  read() {},
-  destroy(err, cb) {
-    // Call end() from inside the destroy() method, like HTTP/2 streams
-    // do at the time of writing.
-    this.end();
-    cb(err);
-  }
-});
-
-duplex.on('finished', common.mustNotCall());
-
-pipeline(readable, duplex, common.mustCall((err) => {
-  assert.strictEqual(err.code, 'ERR_STREAM_PREMATURE_CLOSE');
-}));
-
-// Write one chunk of data, and destroy the stream later.
-// That should trigger the pipeline destruction.
-readable.push('foo');
-setImmediate(() => {
-  readable.destroy();
-});
-- 
cgit v1.2.3