Skip to content

Commit 6b2fea3

Browse files
Trottrichardlau
authored andcommitted
test: move inspector-cli tests to sequential
There's no reason to keep these tests separated from everything else. PR-URL: #39079 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
1 parent 6447cab commit 6b2fea3

27 files changed

+0
-14
lines changed

β€Žtest/README.md

-1
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,6 @@ For the tests to run on Windows, be sure to clone Node.js source code with the
2525
| `doctool` | Yes | Tests for the documentation generator. |
2626
| `es-module` | Yes | Test ESM module loading. |
2727
| `fixtures` | | Test fixtures used in various tests throughout the test suite. |
28-
| `inspector-cli` | Yes | Tests for `node inspect` |
2928
| `internet` | No | Tests that make real outbound network connections. Tests for networking related modules may also be present in other directories, but those tests do not make outbound connections. |
3029
| `js-native-api` | Yes | Tests for Node.js-agnostic [n-api](https://nodejs.org/api/n-api.html) functionality. |
3130
| `known_issues` | Yes | Tests reproducing known issues within the system. All tests inside of this directory are expected to fail. If a test doesn't fail on certain platforms, those should be skipped via `known_issues.status`. |

β€Žtest/inspector-cli/inspector-cli.status

-7
This file was deleted.

β€Žtest/inspector-cli/testcfg.py

-6
This file was deleted.

0 commit comments

Comments
Β (0)