mirror of
https://github.com/nodejs/node.git
synced 2026-11-09 15:11:11 -05:00
Currently when running configure with the --debug option in combination
with the tests (./configure --debug && make -j8 test) there are a few
addon tests that fail with error messages similar to this:
=== release test ===
Path: addons/load-long-path/test
fs.js:558
return binding.open(pathModule._makeLong(path), stringToFlags(flags),
mode);
^
Error: ENOENT: no such file or directory, open
'/nodejs/node/test/addons/load-long-path/build/Release/binding.node'
at Object.fs.openSync (fs.js:558:18)
at Object.fs.readFileSync (fs.js:468:33)
at Object.<anonymous>
(/nodejs/node/test/addons/load-long-path/test.js:28:19)
at Module._compile (module.js:560:32)
at Object.Module._extensions..js (module.js:569:10)
at Module.load (module.js:477:32)
at tryModuleLoad (module.js:436:12)
at Function.Module._load (module.js:428:3)
at Module.runMain (module.js:594:10)
at run (bootstrap_node.js:382:7)
Command: out/Release/node
/nodejs/node/test/addons/load-long-path/test.js
This commit allows for the tests to pass even if the configured build
type is of type debug.
PR-URL: https://github.com/nodejs/node/pull/8836
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Ilkka Myller <ilkka.myller@nodefield.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
36 lines
690 B
JavaScript
36 lines
690 B
JavaScript
'use strict';
|
|
// Flags: --expose-gc
|
|
|
|
const common = require('../../common');
|
|
const binding = require(`./build/${common.buildType}/binding`);
|
|
|
|
function check(size, alignment, offset) {
|
|
var buf = binding.alloc(size, alignment, offset);
|
|
var slice = buf.slice(size >>> 1);
|
|
|
|
buf = null;
|
|
binding.check(slice);
|
|
slice = null;
|
|
global.gc();
|
|
global.gc();
|
|
global.gc();
|
|
}
|
|
|
|
check(64, 1, 0);
|
|
|
|
// Buffers can have weird sizes.
|
|
check(97, 1, 0);
|
|
|
|
// Buffers can be unaligned
|
|
check(64, 8, 0);
|
|
check(64, 16, 0);
|
|
check(64, 8, 1);
|
|
check(64, 16, 1);
|
|
check(97, 8, 1);
|
|
check(97, 16, 1);
|
|
check(97, 8, 3);
|
|
check(97, 16, 3);
|
|
|
|
// Empty ArrayBuffer does not allocate data, worth checking
|
|
check(0, 1, 0);
|