test: fix allocUnsafe uninitialized buffer check

Fixes parallel/test-buffer-bindingobj-no-zerofill to properly check that buffers created with `Buffer.allocUnsafe()` are not zero-filled. The test introduced in nodejs#11706 passes even if the buffer has been zero-filled and fails if none of the buffer values are zero. Signed-off-by: Karl Cheng <[email protected]> Refs: nodejs#11706
Qantas94Heavy · Apr 9, 2017 · 5700fc8 · 5700fc8
1 parent 2d3d4cc
commit 5700fc8
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/test/parallel/test-buffer-bindingobj-no-zerofill.js b/test/parallel/test-buffer-bindingobj-no-zerofill.js
@@ -44,7 +44,7 @@ const monkeyPatchedBuffer = require('../../lib/buffer');
 // possible that a segment of memory is already zeroed out, so try again and
 // again until we succeed or we time out.
 let uninitialized = buffer.Buffer.allocUnsafe(1024);
-while (uninitialized.some((val) => val !== 0))
+while (uninitialized.every((val) => val === 0))
   uninitialized = buffer.Buffer.allocUnsafe(1024);
 
 // On monkeypatched buffer, zeroFill property is undefined. allocUnsafe() should