DNS resolution failed in CI
The runtime could not translate a configured host name into an address in the CI environment.
RECOGNIZABLE ERROR
getaddrinfo ENOTFOUND service-nameRANKED DIAGNOSIS
What usually causes it
- 01
The service alias is missing
The test expects a container or CI service name that was not declared.
DIAGNOSE
List the services and inspect the resolved environment variable without printing credentials.
FIX
Declare the service with the expected alias or update the base host.
- 02
A production-only hostname leaked into tests
Environment precedence may select an unreachable host.
DIAGNOSE
Trace which env file or secret sets the host in this job.
FIX
Use an explicit test configuration and validate it before the suite starts.
- 03
DNS was temporarily unavailable
Runner or network instability can cause a transient lookup failure.
DIAGNOSE
Compare failures across unrelated hosts and runner instances.
FIX
Retry only the readiness probe with a short bound, then surface the runner as unhealthy.
Prevent the repeat
- →Validate hosts before tests.
- →Use stable CI service aliases.
- →Do not silently fall back to production endpoints.
Primary references
Run this against your evidence
The browser triage workflow uses the same stable pattern slug and does not upload your paste.