test: make sure http pipelining does not emit a warning

PR-URL: #37964 Refs: #37937 Reviewed-By: Robert Nagy <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
nodejs · Mar 31, 2021 · 31fe3b2 · 31fe3b2
1 parent 2fa7d33
commit 31fe3b2
Showing 1 changed file with 3 additions and 1 deletion.
diff --git a/test/parallel/test-http-many-ended-pipelines.js b/test/parallel/test-http-many-ended-pipelines.js
@@ -20,7 +20,7 @@
 // USE OR OTHER DEALINGS IN THE SOFTWARE.
 
 'use strict';
-require('../common');
+const common = require('../common');
 
 // No warnings should happen!
 const trace = console.trace;
@@ -59,3 +59,5 @@ server.listen(0, function() {
   client.end();
   client.pipe(process.stdout);
 });
+
+process.on('warning', common.mustNotCall());