test: move common.PORT debug tests to sequential

They tend to hang if they happen to run in parallel with another test that uses common.PORT. PR-URL: #13592 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
nodejs · Jun 20, 2017 · 6025833 · 6025833
1 parent b5d2bc9
commit 6025833
Show file tree

Hide file tree

Showing 7 changed files with 0 additions and 0 deletions.
diff --git a/test/parallel/test-debug-brk-no-arg.js → test/sequential/test-debug-brk-no-arg.js b/test/parallel/test-debug-brk-no-arg.js → test/sequential/test-debug-brk-no-arg.js
diff --git a/test/parallel/test-debug-no-context.js → test/sequential/test-debug-no-context.js b/test/parallel/test-debug-no-context.js → test/sequential/test-debug-no-context.js
diff --git a/test/parallel/test-debug-port-cluster.js → test/sequential/test-debug-port-cluster.js b/test/parallel/test-debug-port-cluster.js → test/sequential/test-debug-port-cluster.js
diff --git a/.../parallel/test-debug-port-from-cmdline.js → ...equential/test-debug-port-from-cmdline.js b/.../parallel/test-debug-port-from-cmdline.js → ...equential/test-debug-port-from-cmdline.js
diff --git a/test/parallel/test-debug-port-numbers.js → test/sequential/test-debug-port-numbers.js b/test/parallel/test-debug-port-numbers.js → test/sequential/test-debug-port-numbers.js
diff --git a/test/parallel/test-debug-signal-cluster.js → test/sequential/test-debug-signal-cluster.js b/test/parallel/test-debug-signal-cluster.js → test/sequential/test-debug-signal-cluster.js
diff --git a/...parallel/test-debugger-util-regression.js → ...quential/test-debugger-util-regression.js b/...parallel/test-debugger-util-regression.js → ...quential/test-debugger-util-regression.js