Repository: nodejs/node
Pull request: test: ignore EPIPE errors in https proxy invalid URL test

There can be a race from eagerly shutting down the servers and severing two pipes at the same time but for the purpose of this test, we only care about whether the requests are initiated from the client as expected, not how the upstream/proxy servers behave. Ignore EPIPE errors from them.

Refs: https://github.com/nodejs/node/issues/59741

<!--
Before submitting a pull request, please read:

- the CONTRIBUTING guide at https://github.com/nodejs/node/blob/HEAD/CONTRIBUTING.md
- the commit message formatting guidelines at
  https://github.com/nodejs/node/blob/HEAD/doc/contributing/pull-requests.md#commit-message-guidelines

For code changes:
1. Include tests for any bug fixes or new features.
2. Update documentation if relevant.
3. Ensure that `make -j4 test` (UNIX), or `vcbuild test` (Windows) passes.

If you believe this PR should be highlighted in the Node.js CHANGELOG
please add the `notable-change` label.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.
-->


Changed files:
filename: test/client-proxy/test-https-proxy-request-invalid-char-in-url.mjs
patch: @@ -82,7 +82,19 @@ for (const testCase of testCases) {
           proxy.close();
           server.close();
           assert.deepStrictEqual(requests, expectedUrls);
-          assert.deepStrictEqual(new Set(logs), expectedProxyLogs);
+          const logSet = new Set(logs);
+          for (const log of logSet) {
+            if (log.source === 'proxy connect' && log.error?.code === 'EPIPE') {
+              // There can be a race from eagerly shutting down the servers and severing
+              // two pipes at the same time but for the purpose of this test, we only
+              // care about whether the requests are initiated from the client as expected,
+              // not how the upstream/proxy servers behave. Ignore EPIPE errors from them..
+              // Refs: https://github.com/nodejs/node/issues/59741
+              console.log('Ignoring EPIPE error from proxy connect', log.error);
+              logSet.delete(log);
+            }
+          }
+          assert.deepStrictEqual(logSet, expectedProxyLogs);
         }));
       }
     }));