|
All checks were successful
CI / verification (pull_request) Successful in 28s
test-curl.sh booted its servers on 3099 and 3098, hardcoded, and ci.test.js runs it whole on every `npm test`: two runs side by side got in each other's way, at least one of them failing every time. - TEST_CURL_PORT and TEST_CURL_NOINGEST_PORT choose the ports, 3099 and 3098 staying the defaults. Names of their own rather than PORT, which a dev shell often exports already. - BASE_URL and NOINGEST_URL are derived from the ports and no longer read from the environment: overridden alone, they sent every curl away from the servers the script had started. - A value outside 1-65535 and two identical ports are refused up front, with the variable named. - ci.test.js gives every case free ports of its own (freePorts() keeps its probes open together so they are distinct), and no case listens on 3099 or 3098 any more. New cases: two passes at once, the four refusals, source pins on the defaults and on the derived URLs, and a first-try connection check that pins the `wait` of the trap, which the fixed ports used to pin by accident. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| agent.test.js | ||
| auth.test.js | ||
| ci.test.js | ||
| findings.test.js | ||
| health.test.js | ||
| hosts.test.js | ||
| state.test.js | ||
| writes.test.js | ||