mirror of
https://github.com/nodejs/node.git
synced 2026-11-09 15:11:11 -05:00
Rich Trott
d196c5d2af
The `test-tick-processor-*` tests are now passing everywhere except for the single-processor 700MHz Raspberry Pi 1 devices. The tests are CPU-intensive. Skip the tests if there is only one CPU and it runs at a speed not more than 700 MHz. PR-URL: https://github.com/nodejs/node/pull/8652 Reviewed-By: Matthew Loring <mattloring@google.com>
34 lines
1016 B
JavaScript
34 lines
1016 B
JavaScript
'use strict';
|
|
const common = require('../common');
|
|
const path = require('path');
|
|
|
|
// 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(path.join(common.fixturesDir, '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();`
|
|
});
|