mirror of
https://github.com/nodejs/node.git
synced 2025-04-30 07:19:19 +00:00
caee112e52
There is actually no reason to use `assert.doesNotThrow()` in the tests. If a test throws, just let the error bubble up right away instead of first catching it and then rethrowing it. PR-URL: https://github.com/nodejs/node/pull/18669 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
17 lines
418 B
JavaScript
17 lines
418 B
JavaScript
'use strict';
|
|
// https://github.com/nodejs/node/issues/6034
|
|
|
|
const common = require('../common');
|
|
const assert = require('assert');
|
|
const zlib = require('zlib');
|
|
|
|
const decompress = zlib.createGunzip(15);
|
|
|
|
decompress.on('error', common.mustCall((err) => {
|
|
assert.strictEqual(decompress._closed, true);
|
|
decompress.close();
|
|
}));
|
|
|
|
assert.strictEqual(decompress._closed, false);
|
|
decompress.write('something invalid');
|