mirror of
https://github.com/nodejs/node.git
synced 2024-12-01 16:10:02 +01:00
eed8b0525c
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>
33 lines
956 B
JavaScript
33 lines
956 B
JavaScript
'use strict';
|
|
const common = require('../common');
|
|
|
|
// TODO(mhdawson) Currently the test-tick-processor functionality in V8
|
|
// depends on addresses being smaller than a full 64 bits. AIX supports
|
|
// the full 64 bits and the result is that it does not process the
|
|
// addresses correctly and runs out of memory
|
|
// Disabling until we get a fix upstreamed into V8
|
|
if (common.isAix) {
|
|
common.skip('AIX address range too big for scripts.');
|
|
return;
|
|
}
|
|
|
|
if (!common.enoughTestCpu) {
|
|
common.skip('test is CPU-intensive');
|
|
return;
|
|
}
|
|
|
|
const base = require('./tick-processor-base.js');
|
|
|
|
// Unknown checked for to prevent flakiness, if pattern is not found,
|
|
// then a large number of unknown ticks should be present
|
|
base.runTest({
|
|
pattern: /LazyCompile.*\[eval]:1|.*% UNKNOWN/,
|
|
code: `function f() {
|
|
for (var i = 0; i < 1000000; i++) {
|
|
i++;
|
|
}
|
|
setImmediate(function() { f(); });
|
|
};
|
|
f();`
|
|
});
|