Commit 2341805
committed
test: remove tests that create very large buffers
With V8 11.9, the maximum ArrayBuffer length can be as high as 2**53,
which is a bit too large for current hardware.
PR-URL: #50115
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>1 parent 1528846 commit 2341805
2 files changed
Lines changed: 0 additions & 32 deletions
This file was deleted.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -30,14 +30,6 @@ for (const [key, value] of sb.entries()) { | |||
| 30 | 30 | ||
| 31 | 31 | // Should work with edge cases | |
| 32 | 32 | assert.strictEqual(SlowBuffer(0).length, 0); | |
| 33 | - try { | ||
| 34 | - assert.strictEqual( | ||
| 35 | - SlowBuffer(buffer.kMaxLength).length, buffer.kMaxLength); | ||
| 36 | - } catch (e) { | ||
| 37 | - // Don't match on message as it is from the JavaScript engine. V8 and | ||
| 38 | - // ChakraCore provide different messages. | ||
| 39 | - assert.strictEqual(e.name, 'RangeError'); | ||
| 40 | - } | ||
| 41 | 33 | ||
| 42 | 34 | // Should throw with invalid length type | |
| 43 | 35 | const bufferInvalidTypeMsg = { | |
0 commit comments