test: move tick-processor tests to own directory

The tick-processor tests are inherently non-deterministic. They
therefore have false negatives from time to time. They also
sometimes leave extra processes running.

Move them to their own directory until these issues are sorted. Note
that this means that the tests will not be run in CI. Like the inspector
tests and other tests, they will have to be run manually when they are
wanted.

PR-URL: https://github.com/nodejs/node/pull/9506
Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com>
Reviewed-By: Matthew Loring <mattloring@google.com>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>

1 files changed, 27 insertions, 0 deletions

diff --git a/test/tick-processor/test-tick-processor-cpp-core.js b/test/tick-processor/test-tick-processor-cpp-core.js
new file mode 100644
index 0000000000..72eb25e91c
--- /dev/null
+++ b/test/tick-processor/test-tick-processor-cpp-core.js
@@ -0,0 +1,27 @@
+'use strict';
+const common = require('../common');
+
+if (common.isWindows ||
+    common.isSunOS ||
+    common.isAix ||
+    common.isLinuxPPCBE ||
+    common.isFreeBSD) {
+  common.skip('C++ symbols are not mapped for this os.');
+  return;
+}
+
+if (!common.enoughTestCpu) {
+  common.skip('test is CPU-intensive');
+  return;
+}
+
+const base = require('./tick-processor-base.js');
+
+base.runTest({
+  pattern: /RunInDebugContext/,
+  code: `function f() {
+           require('vm').runInDebugContext('Debug');
+           setImmediate(function() { f(); });
+         };
+         f();`
+});