Skip to content
ci

test: port tests from node-http-proxy #510

Sign in to view logs

test: port tests from node-http-proxy

test: port tests from node-http-proxy #510

Triggered via pull request September 24, 2025 18:30
@pi0pi0
synchronize #88
test/upstream
Status Failure
Total duration 33s
Artifacts –

ci.yml

on: pull_request
ci
29s
ci
Fit to window
Zoom out
Zoom in

Annotations

5 errors
ci
Process completed with exit code 1.
test/https-proxy.test.ts > lib/http-proxy.js > HTTPS #createProxyServer > HTTP to HTTPS > should proxy the request en send back the response: test/https-proxy.test.ts#L76
Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ test/https-proxy.test.ts:76:7
test/http-proxy.test.ts > http-proxy > #createProxyServer using the web-incoming passes > should proxy sse: test/http-proxy.test.ts#L66
Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ test/http-proxy.test.ts:66:5
Unhandled error: src/server.ts#L68
Error: listen EADDRINUSE: address already in use :::1027 ❯ Server.setupListenHandle [as _listen2] node:net:1940:16 ❯ listenInCluster node:net:1997:12 ❯ Server.listen node:net:2102:7 ❯ ProxyServer.listen src/server.ts:68:18 ❯ test/https-proxy.test.ts:107:12 ❯ node_modules/.pnpm/@vitest[email protected]/node_modules/@vitest/runner/dist/chunk-hooks.js:155:11 ❯ node_modules/.pnpm/@vitest[email protected]/node_modules/@vitest/runner/dist/chunk-hooks.js:752:26 ❯ node_modules/.pnpm/@vitest[email protected]/node_modules/@vitest/runner/dist/chunk-hooks.js:1897:20 ❯ runWithTimeout node_modules/.pnpm/@vitest[email protected]/node_modules/@vitest/runner/dist/chunk-hooks.js:1863:10 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { code: 'EADDRINUSE', errno: -98, syscall: 'listen', address: '::', port: 1027 } This error originated in "test/https-proxy.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should proxy the request en send back the response". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.
Unhandled error: test/https-proxy.test.ts#L99
Error: listen EADDRINUSE: address already in use :::1026 ❯ Server.setupListenHandle [as _listen2] node:net:1940:16 ❯ listenInCluster node:net:1997:12 ❯ Server.listen node:net:2102:7 ❯ test/https-proxy.test.ts:99:16 ❯ node_modules/.pnpm/@vitest[email protected]/node_modules/@vitest/runner/dist/chunk-hooks.js:155:11 ❯ node_modules/.pnpm/@vitest[email protected]/node_modules/@vitest/runner/dist/chunk-hooks.js:752:26 ❯ node_modules/.pnpm/@vitest[email protected]/node_modules/@vitest/runner/dist/chunk-hooks.js:1897:20 ❯ runWithTimeout node_modules/.pnpm/@vitest[email protected]/node_modules/@vitest/runner/dist/chunk-hooks.js:1863:10 ❯ runTest node_modules/.pnpm/@vitest[email protected]/node_modules/@vitest/runner/dist/chunk-hooks.js:1574:12 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { code: 'EADDRINUSE', errno: -98, syscall: 'listen', address: '::', port: 1026 } This error originated in "test/https-proxy.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should proxy the request en send back the response". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.