test: fix common.mustNotCall() usage in HTTP test

The argument to `common.mustNotCall()` is a message, not a function. PR-URL: #24750 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Anto Aravinth <anto.aravinth.cse@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
nodejs · Dec 5, 2018 · 63b06b55d75ce5f983dbfbe3b0b310201c700e3e · 63b06b5
1 parent 3d1853b
commit 63b06b55d75ce5f983dbfbe3b0b310201c700e3e
Showing with 1 addition and 1 deletion.

+1 −1 test/sequential/test-http-max-http-headers.js
diff --git a/test/sequential/test-http-max-http-headers.js b/test/sequential/test-http-max-http-headers.js
@@ -94,7 +94,7 @@ function test1() {
 
   server.listen(0, common.mustCall(() => {
     const port = server.address().port;
-    const client = http.get({ port: port }, common.mustNotCall(() => {}));
+    const client = http.get({ port: port }, common.mustNotCall());
 
     client.on('error', common.mustCall((err) => {
       assert.strictEqual(err.code, 'HPE_HEADER_OVERFLOW');